Keep source and CI aligned
GitLab can cover both repository access and pipeline automation, which suits teams that already work that way.
Integration
GitLab integrations on Wodby
Use GitLab as the Git source for Wodby builds when the repository workflow already lives there and the runtime stack should remain reusable and separate.
GitCI
Let Wodby own the runtime
Use the provider for code and automation while Wodby manages services, integrations, environments, and stack upgrades.
Fit multiple app stacks
The same Git-plus-CI pattern works for frontend apps, APIs, CMS projects, and custom services.
Supported workflows
How GitLab fits into Wodby
Each supported integration kind maps GitLab into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.
Git
Git
Pull application source from GitLab into Wodby build workflows.
- A clean fit for app stacks such as Next.js, Node.js, Laravel, Drupal, and WordPress.
- Repository access is configured once at integration level instead of per app.
- Pairs naturally with CI and registry integrations when the release path spans several systems.
CI
CI
Use GitLab for build and release automation while Wodby manages the runtime stack.
- Lets the team keep build, test, and release logic in the CI system they already use.
- Works well with Wodby CLI and stack-aware deployment workflows.
- Separates pipeline automation from runtime stack management.
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to GitLab.
Stack fit
Stacks that commonly pair with GitLab
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
Next.js
Stack
Next.js application stack for frontend and full-stack projects that need a reusable deployment setup.
Next.js projects typically start from a Git-backed build and release flow.
View stackNode.js
Stack
Node.js application stack for APIs, workers, and custom services with a repeatable runtime setup.
Node.js APIs, workers, and services usually rely on a connected Git provider for source retrieval.
View stackLaravel
Stack
Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.
Laravel teams can keep repository management in the Git provider while Wodby handles the stack runtime.
View stackDrupal 11
Stack
Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.
Drupal delivery remains reviewable when the codebase stays in Git and the stack stays reusable.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.