Enroute
Git servers still think in folders on one machine's disk, and Enroute is the Git server rebuilt like a modern database: your repositories live as immutable layers in object storage, served by compute nodes you can add or replace at will. Point any Git client at it and push; the push creates the repository, gets indexed and validated without locks, and commits once its entry is replicated across the ledger nodes' disks, which is how a single repository absorbs thousands of pushes per second. Clones and fetches always read one consistent snapshot, so readers never block writers, and background layer merging replaces the git repack jobs you used to schedule. The programmable part is hooks: your own code decides who can read or write, which branches a client may see, whether a ref update is allowed, and what happens after a push, from running CI to mirroring elsewhere. A rich gRPC API lets applications create, inspect, and manage repositories programmatically, so you can build your own code-hosting product on top instead of forking a monolith. Start as one node with a local directory, then separate compute from ledger nodes and replicate across three machines without pushing a repository again. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
walgit
walgit is a self-hosted Git server that keeps every repository inside one S3 or GCS bucket, so the machine serving your code is disposable while your history stays durable. Point the binary at a bucket, start it, and pushing to a new repository name creates that repository on the spot, with no admin console or provisioning step in between. Developers clone, fetch, and push over smart HTTP with Git LFS support for large files, and big clones are delivered as static bundle files so multi-gigabyte repositories never bottleneck the server process. The built-in web interface lets you browse file trees, read files, review commit history, and inspect diffs directly in the browser. Per-repository policy files control protected branches, fast-forward-only references, and bypass lists, so release branches stay guarded without a separate compliance tool. A JSON API and the dependency-free repos.js SDK let scripts, internal dashboards, and automation agents read repository data programmatically, with long operations streaming progress as server-sent events. Webhooks deliver exactly-once reference events to CI systems, chat tools, and deployment pipelines whenever branches or tags move. Background checkpoints and compaction keep storage tidy on their own, while token or OpenID Connect sign-in decides who may read and who may push. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Infrahub
For network and infrastructure teams, Infrahub is one validated source of truth for devices, IP space, circuits, and services, with Git-style branches for every change. You write the schema in YAML, and Infrahub builds the web interface and API endpoints from it, covering sites, devices, interfaces, VLANs, BGP sessions, or any concept your business needs. Built-in IPAM tracks IPv4 and IPv6 prefix trees, utilization, addresses, namespaces, and resource pools. Work on a branch, compare a per-object diff of added, removed, and updated records, resolve conflicts, and merge through a proposed change that bundles data, files, artifacts, schema, and check results. Python checks enforce your own design rules, such as two WAN circuits per site, before anything merges. Immutable history and an activity log answer who changed what, and when. Transformations in Jinja2 or Python render device configurations and other documents as stored artifacts, while Generators create objects from a site design. Git repositories supply schemas, queries, and templates. GraphQL, REST, a Python SDK, an Ansible collection, and a Nornir plugin feed existing automation, Infrahub Sync imports from NetBox or Nautobot, and an optional MCP server lets Claude and Cursor read the data. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Gerrit Code Review
Unlike pull-request forges, Gerrit reviews every Git change as a series of patchsets, and nothing merges until the required approvals are in. Developers upload with a plain git push to a refs/for ref, adding push options for topics, hashtags, work-in-progress, or private changes. Each change gets a page listing reviewers, CCs, an attention set that flags who must act next, and submit requirements driven by labels such as Code-Review and Verified, with a quick approve button for the last missing vote. Side-by-side diffs with syntax highlighting take inline comments written in Markdown, saved as drafts and published together. A Checks tab shows CI runs reported by plugins, and integrations reach Jenkins, GitHub Actions, Zuul, and webhooks. Access rights attach to groups and branch patterns, including regular expressions, and inherit from parent projects and All-Projects. Sign-in works with LDAP, OAuth, OpenID, or HTTP single sign-on, and SAML through a plugin. A query language filters changes by status, owner, reviewer, label, file path, and reviewer count. Projects pick a submit strategy: merge if necessary, fast forward only, rebase if necessary, rebase always, merge always, or cherry pick. A REST API, SSH commands, and a plugin system extend the server, and an optional Review Agent chat panel can summarize a change once an AI provider plugin is installed. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Review Board
Before a change lands in the main branch, Review Board gives your team a self-hosted code review server where reviewers read the diff, open issues on specific lines, and sign off with a Ship It. Post a review request from the web or with RBTools, either before you commit or after, and every update becomes a new revision that stays in the history. Interdiffs show exactly what changed between revisions, and moved-code detection keeps rearranged blocks from drowning out real edits. Comments can open issues that reviewers later mark fixed or dropped. Images and Markdown files can be reviewed alongside code, with split, onion-skin, color, and side-by-side diffs for pictures. A dashboard with customizable columns separates incoming from outgoing requests by review group. Connect Git, Mercurial, Subversion, or Perforce repositories, including ones hosted on GitHub or GitLab, and review them all on one server. Slack and Discord notifications, Jenkins builds, and Review Bot linters report back inside the review. Private repositories and hidden or invite-only review groups restrict who sees what, with sign-in through Active Directory, LDAP, or SAML 2.0. A REST API, WebHooks, and Python extensions cover custom workflows. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Dolt
Dolt is a SQL database that versions your tables the way Git versions files, so every row carries a history you can branch, diff, merge, and roll back. The command line mirrors Git command for command: dolt init, add, commit, checkout, log, and blame operate on tables instead of files, and merges happen cell by cell, with conflicting cells landing in dolt_conflicts tables you resolve by choosing ours or theirs. Run dolt sql-server and the same database answers on the MySQL wire protocol, so the mysql client, TablePlus, DataGrip, and your existing application drivers connect unchanged, while stored procedures like DOLT_CHECKOUT and DOLT_MERGE and system tables like dolt_diff and dolt_log put version control inside SQL itself. Teams push and pull databases through remotes on DoltHub, S3, GCS, or a filesystem, fork a database to test a risky migration, and cherry-pick the good commits back. AI agents get their own branches to write into, and a human reviews the row-level diff before anything merges to main. Data publishers ship corrections as commits subscribers can pull, and analysts query any historical snapshot with AS OF instead of restoring backups. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
Twigpine Node
Twigpine Node is a self-hosted git node that publishes repositories under cryptographic identities and replicates them across a peer-to-peer network. Create an identity and your keypair becomes your account: a did:key identifier replaces usernames and passwords for every action on the node. Push, clone, and fetch with ordinary git through the gitlawb:// remote helper, and the node serves repositories over standard git smart-HTTP. Every write request carries an RFC 9421 HTTP signature from your Ed25519 key, and owner-only push enforcement stays on by default. Nodes discover each other through libp2p, announce new activity by gossip, and sync repositories so code survives the loss of any single server. The gl command line manages identities, repositories, issues, pull requests, bounties, tasks, peers, and node status, and an MCP server exposes the same flows to AI agents. Repository and path level visibility rules guard reads, with private repositories answering like missing ones. Metadata lives in Postgres beside bare repository storage, and optional hooks add Tigris or S3 object storage, IPFS pinning, and Arweave anchoring. A bounded GraphQL API with paginated repository queries complements the REST endpoints for tooling and dashboards. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT and Apache-2.0 licensed.
GitBucket
One downloadable WAR file gives your team a complete GitHub-style home for its code, with no per-seat bill and no repositories living on someone else's terms. You create public or private repositories and reach them over HTTP, HTTPS, or SSH, with Git LFS handling large binary assets alongside ordinary commits. The repository viewer includes an online file editor, so quick fixes and documentation tweaks happen in the browser without a local clone. Every repository carries its own issue tracker, pull request workflow, and wiki, keeping discussion, review, and project documentation next to the code they describe. Activity timelines and email notifications keep collaborators aware of new issues, comments, and merges as they happen. Administrators manage users and groups directly, connect account management to LDAP, and protect the instance with fine-grained repository visibility. A plug-in system extends the platform, and official plug-ins add gists, emoji, static Pages hosting, and richer notifications, while community plug-ins widen the menu further. Tools that already speak the GitHub API can point at your GitBucket instead, because its web API deliberately mirrors GitHub's. Upgrades stay simple: stop the process, replace the WAR, and restart with the same data directory. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.
GitArena
GitArena gives your team its own place to host code, combining repository hosting, issue tracking, and code review in one lightweight service you run yourself. Push and pull over HTTP or SSH, browse code in the browser with syntax highlighting, blame, and raw views, and follow commit history with diffs branch by branch. Repositories can be forked, archived, tagged, and released with downloadable assets, and every project gets an issue tracker with labels, milestones, assignees, and a kanban board. Issues are stored natively in Git using the git-bug format, so they travel with the repository and remain readable offline with the git-bug CLI. Merge requests collect changes for review before they land, while organizations and teams control who can see and change each project. Search spans code, repositories, issues, and users from one box, profiles show contribution graphs and activity, and sign-in supports passwords, SSH keys, passkeys, and OAuth single sign-on. A REST API exposes the platform to your own tooling, and the whole service runs from a single Docker Compose stack or a compiled binary with a separate frontend build. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Forgejo
Governed by the non-profit Codeberg e.V. with over 150 contributors and quarterly major releases reaching v16.0 in July 2026, Forgejo delivers a complete code collaboration platform in a single Go binary that runs comfortably on 512 MB of RAM — providing full Git hosting with SSH and HTTPS, pull requests with inline code review, issue tracking with labels and milestones, kanban project boards, wikis, and an integrated package registry supporting Docker, npm, PyPI, Maven, NuGet, and Cargo. Forgejo Actions provides GitHub Actions-compatible CI/CD with reusable workflows, OpenID Connect for secure third-party access, ephemeral runners for autoscaling, and dynamic matrix support for complex build pipelines. The platform implements ActivityPub-based forge federation allowing issues, pull requests, and stars to work across independent instances — enabling a decentralized development ecosystem similar to how Mastodon federates social networks. Organizations and team permissions provide fine-grained access control, while LDAP, OAuth2, and OpenID authentication integrate with existing identity infrastructure. Code search indexes repositories for fast discovery, LFS handles large files efficiently, and mirror synchronization imports repositories from GitHub, GitLab, and other forges. Deploy via a single static binary, Docker container, or official Helm charts with SQLite for small instances or PostgreSQL and MySQL for production workloads. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3+ licensed.
Githome
Point the gh CLI at your private Githome server and it works identically to github.com, because every REST v3 and GraphQL v4 endpoint returns byte-for-byte compatible JSON shapes, headers, Link pagination, and ETag caching. A single compiled Go binary serves the REST API under /api/v3, GraphQL under /api/graphql, git smart-HTTP transport, and a server-rendered web UI implementing the GitHub Primer design system with full functionality when JavaScript is disabled. The web interface provides repository browsing with Markdown rendering and syntax highlighting, issue tracking, pull requests with unified diffs and inline code review threads, full-text search, user profiles, and a notifications inbox. Authentication supports personal access tokens with prefix-based identification, OAuth device and web flows, and scoped permissions on every response header with only token hashes stored. The pull request system implements the complete lifecycle including async mergeable state computation, squash, merge, and rebase strategies, commit statuses, check runs, and statusCheckRollup fields. Webhooks deliver events with X-Hub-Signature-256 verification, SSRF protection, and at-least-once retry semantics. Storage supports SQLite for single-node deployments or PostgreSQL for production configurations. Performance optimizations include batch loaders replacing N+1 queries, keyset pagination, FTS-backed search, and GraphQL dataloaders. Docker deployment pulls the official multi-arch container image from GitHub Container Registry. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.