This page summarises the differences between GitLab for Confluence (Data Center) and GitLab for Confluence (Cloud).
Connection
|
Capability |
Data Center |
Cloud |
|---|---|---|
|
Connect via GitLab Personal Access Token |
✅ |
✅ |
|
Global (admin-level) connection |
✅ |
✅ |
|
Per-user (personal) connection |
✅ |
❌ |
|
Multiple integrations support |
✅ |
❌ |
Supported macros
|
Macro / Content Type |
Data Center |
Cloud |
|---|---|---|
|
Project / Repository
|
✅ |
✅ |
|
Issue |
✅ |
✅ |
|
Merge Request |
✅ |
✅ |
|
Commit |
✅ |
✅ |
|
Release |
✅ |
✅ |
|
Epic |
✅ |
✅ |
|
Milestone |
✅ |
✅ |
|
Snippet |
✅ |
✅ |
|
File content |
✅ |
✅ |
|
Pipeline (single) |
❌ |
✅ |
|
Job (single) |
❌ |
✅ |
|
Gantt chart
|
✅ |
✅ |
|
GitLab Query (GLQL)
|
❌ |
✅ |
|
↳ Issues list |
✅ dedicated macro |
✅ via GLQL |
|
↳ Merge requests list |
✅ dedicated macro |
✅ via GLQL |
|
↳ Milestones list |
✅ dedicated macro |
✅ via GLQL |
|
↳ Projects list |
✅ dedicated macro |
✅ via GLQL |
|
↳ Groups list |
✅ dedicated macro |
✅ via GLQL |
|
Builds / Pipelines list
|
✅ |
❌ |
Global configuration settings
|
Setting |
Data Center |
Cloud |
|---|---|---|
|
Request timeout (duration (in seconds) before a macro call times out) |
✅ |
❌ |
|
Allowed spaces (restrict macros to specific Confluence spaces) |
✅ |
❌ |
|
Forbidden spaces (prevent macros from being used in specific Confluence spaces) |
✅ |
❌ |
|
Automatically convert GitLab links into macros |
✅ |
❌ Not configurable on Cloud, auto-conversion is always on |
|
Macro Default Settings (administrator-defined default values applied to GitLab macros) |
✅ |
❌ |
Hosting & deployment
|
Capability |
Data Center |
Cloud |
|---|---|---|
|
Works with http://gitlab.com (SaaS GitLab) |
✅ Yes |
✅ Yes |
|
Works with self-hosted, internet-reachable GitLab |
✅ Yes |
✅ Yes |
|
Works with self-hosted GitLab that is not reachable from the internet |
✅ Yes |
❌ |
Need help?
If you have questions about the differences above, please contact the Move Work Forward Support team. We'll be glad to help.
Updated: October, 2026