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.
Git server VPS
Host repositories on a server you control. Plan SSH or HTTPS access, storage growth and backups for repositories and service configuration.
Hosting options
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
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.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
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
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.
Back up repositories, the application database, and configuration together. Repositories alone cannot rebuild user accounts, permissions, and issue history.
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.
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
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour 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.