Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Git server VPS

Canadian VPS hosting for a Git server

Host repositories on a server you control. Plan SSH or HTTPS access, storage growth and backups for repositories and service configuration.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

Runtime and processes

Check a self-hosted Git service on a VPS where repository data, SSH/HTTPS access, user accounts, hooks, upgrades, backups, and storage growth are the customer’s responsibility.

02

Data to protect

Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.

03

Network access

List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.

04

Deployment and maintenance

Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.

Field guide

Self-hosted Git: storage, access, and backups

A self-hosted Git service such as Gitea or GitLab stores three things that grow at different rates: repository data, the application database, and build or attachment artifacts. GitLab in particular carries a documented minimum memory footprint for its bundled services, so read the current requirements for your chosen software before sizing the server.

Access runs over SSH and HTTPS, and both need care: SSH keys per user, no password login for Git accounts, and TLS on the web interface. The failure people hit is disk pressure from repository growth and CI artifacts, discovered when pushes start failing, so monitor repository disk use and set artifact expiry.

01

Repository backup scope

Back up repositories, the application database, and configuration together. Repositories alone cannot rebuild user accounts, permissions, and issue history.

02

Hook and LFS load

Large binary assets belong in Git LFS or external storage. Plain Git clones copy every version of every large file, which slows clones and inflates the disk.

03

Upgrade path testing

Snapshot or back up before each upgrade and read the release notes for required intermediate versions. Skipping required upgrade stops is a common cause of failed migrations.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Canadian VPS hosting for a Git server: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move