Gitblit Hosting on MassiveGRID PaaS
Gitblit is an open-source, pure-Java Git server for hosting, viewing and managing repositories, designed for small workgroups that want a centralised Git service without the weight of GitLab. The MassiveGRID PaaS package deploys Gitblit on a Java server in one click, with HTTPS from the first minute.
Gitblit on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $19.68 a month for the Starter configuration, a Java application server (1 GiB), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with Gitblit pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Gitblit Package Facts
| Attribute | Value |
|---|---|
| Package | Gitblit |
| Type | Application (installs a complete environment) |
| Category | DevOps & Admin Tools |
| Software vendor / project | Gitblit project |
| Licence | Apache License 2.0 (open source) |
| Runtime / stack | Gitblit Java Git server on a Java application server |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $19.68/month for the Starter configuration (8 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Gitblit?
Gitblit provides repository hosting over HTTPS and SSH, a web interface to browse commits, branches and diffs, user and team management with per-repository permissions, federation between Gitblit instances, and a ticket system. It runs as a single Java application with no external database, which makes it simple to operate and cheap to host.
The package deploys Gitblit on a Java application server with persistent storage for repositories and configuration, and exposes the web interface over HTTPS. It suits teams that need a private Git server for a handful of projects and prefer minimal administration.
What the Gitblit Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.
- Java application server: A Java container running the Gitblit web application with JVM settings tied to the cloudlet allocation.
- Repository storage: Persistent disk for Git repositories, users and settings, with platform snapshots.
- HTTPS and SSH access: Web UI and Git-over-HTTPS on the platform subdomain, with SSH transport configurable.
- Initial administrator: Admin credentials delivered to your dashboard and email after installation.
What Gitblit Costs to Run
Three starting configurations for the Gitblit package, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterEvaluation and small workloads | Java application server (8 cloudlets, 1 GiB) | 8 | $19.68 |
| StandardA team in daily use | Java application server (16 cloudlets, 2 GiB) | 16 | $39.36 |
| ProductionBusy or business-critical use | Java application server (32 cloudlets, 4 GiB) | 32 | $78.72 |
Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.
Why Teams Choose Gitblit
Simple, self-contained
One Java application, no database, minimal configuration.
Access control
Users, teams and per-repository permissions, plus LDAP integration.
Repository browsing
Commit history, diffs, branches, tags and search in the web interface.
Federation and mirroring
Mirror repositories between Gitblit instances for backup or distribution.
How to Install Gitblit on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Gitblit package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every Gitblit node, wires them together and hands you the live URL and credentials.
Who Runs Gitblit on PaaS
Small development teams
Groups of two to twenty developers that need private repositories without GitLab's footprint.
Internal tooling and configuration repos
Ops teams storing infrastructure code and scripts on a server they control.
Backup mirrors
A federated Gitblit instance mirroring repositories from another server.
Why Run Gitblit on MassiveGRID PaaS
Built for uptime. Gitblit runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Gitblit environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 27001 and ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: For Developers.
Gitblit Questions
Gitblit Guides from the MassiveGRID Blog
Gitblit is covered in these comparison guides and roundups, alongside the packages it is usually deployed with. Browse the blog.
More from the Marketplace
Packages that are often deployed alongside Gitblit, or that solve the same problem a different way. Browse all 83 packages.
Deploy Gitblit Today
Start the free 14-day trial and have Gitblit running in minutes. No credit card required.