GitLab VPS

GitLab VPS, self-hosted and preinstalled

GitLab CE comes installed and running, so you push your first repository the moment you log in. Your source code, pipelines and container images stay on a machine you own, with full root access, NVMe storage and a dedicated Vietnam IPv4. Billed monthly, and you never pay per seat.

View pricing Get help choosing a config

Unlimited users
No CI minutes
Container registry
Self-hosted

GitLab VPS plans

GitLab documents a baseline of 8 vCPU and 16 GB of memory for a single-node install, so we only open the tiers that actually run it well. Both plans sit on NVMe with a dedicated Vietnam IPv4, and GitLab CE is configured before you get the login.

GitLab CE and GitLab Runner, preinstalled
HTTPS with Let's Encrypt from first login
Unlimited users, no CI minute metering
Full root, edit gitlab.rb as you like

VPS VNx4

Small teams and private repositories.

790.000đ/mo

Order Now

6 vCPU
12GB RAM
80GB Storage
Unlimited Traffic
IPv4 rDNS, Full Root

Recommended

VPS VNx8

Matches the GitLab baseline of 8 vCPU and 16 GB.

1.190.000đ/mo

Order Now

8 vCPU
16GB RAM
100GB Storage
Unlimited Traffic
IPv4 rDNS, Full Root

Not sure which plan fits, or need something bigger?

See all plans and pricing

From commit to deploy, on runners you own

A merge request kicks off the same GitLab pipeline your team already knows. Build, test and deploy stages run on GitLab Runner registered against your own instance, so there are no metered minutes and no shared fleet.

Commit and open a merge request
Build and test on your own runner
Publish images to the container registry
Deploy from the same box, close to your users

A GitLab CI/CD pipeline: a feature branch opens a merge request into main, then build, test and deploy stages run on your own runner, each marked passed and ending in a passed pipeline — A merge request into main triggers build, test and deploy stages, each passing on a runner you control.

GitLab ready on login, full root behind it

SSH in and GitLab CE is already serving over HTTPS. Create your first group, push a repository and register a runner. You still hold full root, so you tune gitlab.rb, resize Puma workers, mount a bigger volume for the registry or restore a backup on your own schedule.

Preinstalled: GitLab CE, Omnibus package
Storage: NVMe SSD, never SATA or HDD
IPv4: 1 dedicated Vietnam address
Support: 24/7 ticket, from 790.000đ/mo

vnx-08 Running

GitLab CE: latest stable
Install method: Omnibus
Runners registered: 2
Configuration: 8 vCPU · 16 GB RAM
Storage: 100 GB NVMe SSD
Region: Vietnam

A Git platform you actually own

Hosted Git services bill per seat, meter your CI minutes and keep your code on someone else's disk. This is a dedicated machine with committed resources where the repositories, the pipelines and the registry all belong to you.

No seats, no CI minutes

GitLab CE is free and open source. Add as many users as your team needs and run pipelines until the CPU runs out. You pay for the server, not for headcount.

Source code stays in Vietnam

Repositories, artefacts and backups live on NVMe in our Vietnam datacenter, on a dedicated IPv4 you control. Nothing is replicated to a region you did not choose.

CI/CD close to your users

Register runners on the same box or on a second VPS. Clones, pulls and pipeline artefacts move over local network paths instead of crossing an ocean on every job.

Full control, no black box

Edit gitlab.rb, swap the bundled PostgreSQL for an external one, point object storage elsewhere, or upgrade on your own timetable. Nothing about the install is locked down.

What comes preinstalled

Every GitLab VPS ships with the Omnibus package and the services it depends on, already wired together. Prefer a clean slate or a different setup? Reinstall the OS anytime, free of charge.

GitLab CElatest stable, Omnibus

GitLab RunnerCI/CD, Docker executor

PostgreSQLbundled, tuned for GitLab

Rediscache, queues, sessions

Nginx + Let's EncryptHTTPS from first login

Built for real engineering teams

With root on the box and NVMe underneath it, the GitLab VPS carries the work a development team does every day:

Private repositories: Unlimited private projects and groups, with merge requests and code review built in
CI/CD pipelines: Build, test and deploy with runners you own, without metered pipeline minutes
Container registry: Push and pull your own images from the registry that ships with GitLab
Code that cannot leave: Projects under NDA or regulatory scope, kept on infrastructure you can point to
Issue and release tracking: Boards, milestones and releases alongside the code, in one place
Migration off hosted Git: Import from GitHub, Bitbucket or gitlab.com and keep history, issues and merge requests

Frequently asked questions

GitLab VPS at thueVPS

How much RAM does self-hosted GitLab really need?

GitLab's own documentation gives a baseline of 8 vCPU and 16 GB of memory for a single-node install, and notes that it can operate with at least 8 GB in constrained scenarios. That is why the smallest GitLab VPS we sell is 6 vCPU with 12 GB, and why VNx8 at 8 vCPU and 16 GB is the plan we recommend. A 4 GB machine will install GitLab and then struggle the first time a pipeline runs.

Which GitLab edition is preinstalled?

GitLab Community Edition, installed from the official Omnibus package. It is free and open source, with unlimited users and private repositories. If you later need Premium or Ultimate features, you can apply a licence to the same installation without rebuilding the server.

Is GitLab Runner included, and where does it run?

GitLab Runner is installed and registered against your instance with the Docker executor, so pipelines work out of the box. Because CI competes with GitLab itself for CPU and memory, teams running heavy pipelines usually move the runner onto a second VPS. That is a configuration change, not a reinstall.

Is HTTPS set up for me?

Yes. Nginx ships with the Omnibus package and we configure a Let's Encrypt certificate that renews automatically, so your instance is on HTTPS from the first login. Point your domain at the dedicated Vietnam IPv4 before provisioning and the certificate is issued for that hostname.

Can I migrate an existing GitHub or gitlab.com project across?

Yes. GitLab has built-in importers for GitHub, Bitbucket and other GitLab instances, and they bring repositories, issues, merge requests and comments with them. For a whole gitlab.com group, a project export and import preserves history without touching the command line.

How do backups work?

Omnibus provides gitlab-backup create, which archives repositories, the database, uploads and the registry into a single tarball. Schedule it with cron and copy the result off the server. The snapshots and backups available on your VPS cover the whole disk as a second layer. We recommend keeping off-server copies of anything important, on a regular schedule.

Should swap be enabled on the server?

GitLab advises disabling swap where possible, because swapping causes significant performance degradation under load. Both plans are sized so that GitLab has enough real memory and never needs to reach for it. If you keep swap for safety, treat it as a crash buffer rather than as extra RAM.

How do payment and billing cycles work?

Billing is monthly and PayPal is accepted. There is no long-term contract, so you renew or cancel whenever you want. GitLab CE itself costs nothing, so the only bill is the server.