GitLab stack services
This page shows the capabilities provided by the services in the GitLab stack and the connections, configs, settings, cron schedules, actions, volumes, backups, imports, and other customizations attached to them for this specific stack.
| Stack service | Base service | Versions | Role |
|---|---|---|---|
| GitLab Community Edition | 19 | Primary | |
| PostgreSQL | 17 | Required | |
| Valkey | 8.1 | Required | |
| OpenSMTPD | 7 | Required | |
| GitLab Runner | 19 | Disabled by default |
- Additional services can be added or removed.
- When one of the services in the stack updates, the stack can be upgraded to a new revision.
- Stack changes can then be rolled out to environments on your schedule.
Backups
Protect service data with repeatable backup workflows that stay attached to the stack.
Imports and migration
Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.
Configs
Keep service config files versioned with the stack instead of rebuilding them per environment.
Settings
Tune service behavior per environment while keeping one reusable stack baseline.
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Service links
See how services are wired together so dependencies stay consistent across environments.