Managed Gitness Hosting — production-ready from $11 a month
Open-source developer platform combining Git hosting, CI pipelines, and delivery. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Gitness, no lock-in.
Gitness on ManageStacks is an open-source developer platform with source control, continuous integration and continuous delivery, deployed to your own AWS, Azure or GCP region with flat per-app pricing from $11 a month ($25 on the Standard production plan). Engineering teams host repositories and pipelines in one place, as an alternative to GitHub and GitLab.
What does Gitness do, and why do teams deploy it?
Gitness is a developer platform from Harness that brings source code hosting and pipelines together. Teams create Git repositories, review code through pull requests, and define pipelines that build and test changes. It is written mainly in Go with a TypeScript web interface, and it is released under the Apache-2.0 licence. A single Go service keeps the footprint small, which makes it practical to run for a team that wants repositories and automation together in infrastructure they operate themselves.
- Git repository hosting with a web interface
- Pull requests with code review and comments
- Built-in CI pipelines defined as code
- Pipeline execution with logs shown in the interface
- Spaces to organise repositories and pipelines into groups
- Secrets storage for use in pipeline steps
Open-source developer platform combining Git hosting, CI pipelines, and delivery
Gitness as a self-hosted alternative to GitHub, GitLab and Bitbucket
Instead of paying per-seat fees to a SaaS vendor, teams self-host Gitness to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed Gitness hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting Gitness the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Gitness at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Gitness run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Gitness in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Gitness on ManageStacks
What is Gitness on ManageStacks?
Gitness is an open-source developer platform with Git hosting and CI/CD pipelines. ManageStacks deploys and operates it in your own AWS, Azure, or GCP account, so your source code, pipelines, and build logs stay on infrastructure that you control.
How does Gitness compare to GitHub?
GitHub is a proprietary hosted platform with a large ecosystem. Gitness is open-source and self-hosted, combining repositories, pull requests, and pipelines in one service you control. It is a good choice when keeping code and CI in your own account matters more than ecosystem size.
Does Gitness include CI/CD?
Yes. Gitness includes pipelines that you define as code, so builds and tests can run when changes are pushed. The pipeline results and logs appear next to your repositories, which keeps feedback close to the code it relates to.
Can I import existing repositories or keep my code?
Yes. You can bring existing Git repositories across, since Git history is portable, and your data is stored in your own cloud account. You keep full ownership of your code and can clone or export it at any time.
How are Gitness upgrades and backups handled?
ManageStacks handles upgrades and scheduled backups of the data in your account. You can schedule updates to suit your release cycle, and a backup can be restored if an upgrade needs to be reversed, protecting your repositories and pipeline history.
Other devtools tools on ManageStacks
WordPress
Open-source publishing platform for websites, blogs, and online applications
GitLab
Single DevOps platform for Git hosting, CI/CD pipelines, code review, and security scanning
Drupal
Open-source content management platform for structured, multi-author websites
Joomla
Open-source content management system for websites and online applications
Run Gitness without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $11/mo.