Apps / GitLab CE
Managed GitLab CE hosting.
One server, no app limits.
Full self-hosted Git plus CI/CD. Honest requirement: it wants 8 GB, and we will say so before you order.
What it is
GitLab CE is the whole DevOps platform self-hosted: Git, merge requests, issue boards, CI/CD with runners, and a container registry, in one (famously resource-hungry) Omnibus package.
Minimum RAM
8 GB
Fits on SC-8GB; SC-16GB is the comfortable pick with room to stack.
What we install
The playbook deploys GitLab CE via the official Omnibus package with external URL and HTTPS configured, mail through the managed gateway, backup jobs wired into our dual offsite backup path, and the sysctl and memory settings GitLab actually requires.
What managed covers
OS, package, and platform updates on GitLab's release cadence with a snapshot before each; daily snapshots and dual offsite backups of repositories and the database; monitoring tuned for GitLab's appetite; the managed firewall and deliverable email.
The app is $0. The managed server is the only bill, and everything above is part of it.
What does managed GitLab hosting include?
The full Omnibus GitLab kept updated, backed up, and monitored on a server sized for it, plus mail that delivers and a firewall that is watched. Everything gitlab.com charges per user for, at the flat price of one capable server.
How big a server does GitLab really need?
GitLab's own minimum is 8 GB of RAM, and it means it, which is why the catalog lists 8 GB and the order flow will not pretend otherwise. A small team on SC-8GB is comfortable; add runners or heavy CI and SC-16GB is the honest pick. We would rather size you right than sell you a slow GitLab.
Do CI runners work?
Yes. A runner on the same server suits light pipelines; busier teams put runners on a second small server so CI cannot starve the main instance, and both stay inside one managed relationship.
GitLab CE or Gitea?
GitLab when you want the integrated everything: boards, environments, registry, approvals. Gitea when you want Git plus CI in a tenth of the footprint. Both are in this catalog; the honest difference is 8 GB versus 1 GB, and we will say so.
Stack it
GitLab CE runs well with.
Same server, no extra bill. These are the companions our team installs next to GitLab CE most often.
Uptime Kuma
+1 GBThe self-hosted uptime monitor everyone loves. Watch your sites from your own server.
Frequently asked questions
Is 8 GB really the minimum?
Yes, per GitLab's own documentation, and our experience agrees. Below it, GitLab swaps and crawls. The order flow sizes for reality.
Do you handle GitLab upgrades?
Yes, on the maintained release line, snapshot first, respecting GitLab's required upgrade paths between versions. Skipped-version jumps are planned, not improvised.
Are backups GitLab-aware?
Yes: the playbook wires gitlab-backup into the schedule and ships the artifacts into the dual offsite path, alongside the full-server snapshots.
Sizing an app stack? The VPS sizing calculator recommends a plan from your apps and traffic, with the math shown.
Shared CPU servers
The right home for GitLab CE and most stacks: 3.0+ GHz vCPU, from $10/mo.
See Shared CPU →Dedicated CPU servers
For CPU-hungry stacks and busy databases: cores that are physically yours.
See Dedicated CPU →All plans and pricing
Every plan, both families, one honest price with everything included.
See pricing →Your server runs. You sleep.
Fully managed hosting from people who have been doing this since 2001.