A Git host for teams
Review in small steps. Keep every review. Self-hosted.
Fettlecode is a Git host you run on your own server: repositories, code review and editing in the browser, for your whole team. Push a stack of small commits and each becomes its own change, reviewed and merged in order. Reviews remember what you've seen, even after a rebase. Single sign-on, code owners and the merge queue are free, with nothing held back.
Fettlecode is in development and hasn't been released. It will be free for every organisation for now, and for personal use and teams of up to 10 for good, with a commercial licence for larger organisations later; the source code and Docker image aren't public yet.
Stacks with plain Git
Push your commits to refs/for/main. Each one becomes a change, stacked
on the one before. No extra tool to install.
Review that remembers
Every revision is kept. A clean rebase keeps your approvals and “reviewed” marks; you see only what the author changed.
Yours
Your server, plain Git repositories, and source code you can read. Single sign-on and the audit log aren't kept for a top tier.
See it in action
Half a minute of reviewing a stack.
Priya opens a change from her review list and sees only what Tom changed since she last looked. She marks the file reviewed, leaves a comment, approves it, and checks the merge queue.
Features
The Git host you know, with better review.
Everything here works today, in every copy. There are no feature tiers and no plans to unlock.
Stacked review
One change per commit, stacked in order. Approve each layer on its own, then submit the stack bottom up, all or nothing.
Since you last looked
Come back to a change and see only what its author changed since your last visit, with changes from the rebase taken out.
Discussions you settle
Comment on a line, a file or the whole change. Whoever is waiting for an answer is the one who resolves it, and the change waits too.
Rules, owners and a queue
Branch rules, completion rules and CODEOWNERS. “Merge when ready” queues
a change to merge as soon as its approvals and discussions allow.
Single sign-on, free
SAML, OpenID Connect, LDAP and SCIM provisioning, plus passkeys and two-step sign-in. Teams and five roles for each repository.
Comes with you from GitHub
Import repositories with their open pull requests, keep mirrors in step, and link pull requests both ways while you move.
Screenshots
More of the app.
Taken from the app as it is today, with a demo team. Light and dark themes follow your system, or each person's choice.
How review works
Two commands, once. Then just push.
-
In each clone, add the hook that gives every commit a
Change-Id, so a change keeps its identity through amends and rebases. - Push for review. Each commit becomes a change; commits on top of each other become a stack.
- Amend or rebase, then push again. Each change gets a new revision, and reviewers see only what's new.
Pushes to a protected branch that's review-only are refused with a message saying how to send them for review instead. More on review.
# Once, in each clone
curl -o .git/hooks/commit-msg https://code.example.com/tools/commit-msg
chmod +x .git/hooks/commit-msg
# Send your commits for review, as a stack
git push origin HEAD:refs/for/mainAt a glance
What comes in every copy.
Compare
What other Git hosts charge extra for.
A few of the things that sit in paid plans elsewhere.
| Feature | Fettlecode | Elsewhere |
|---|---|---|
| SAML single sign-on | Free, with OIDC, LDAP and SCIM too | GitHub: Enterprise, from US$21 a person a month. Gitea and Graphite: Enterprise. GitLab self-managed: in Free. |
| Approval rules and code owners | Free | GitHub: Team, for private repos. GitLab: Premium, US$29 a person a month. |
| Merge queue | Free | GitLab merge trains: Premium. Graphite: Team, US$40 a person a month. |
| Stacked review | Free, self-hosted, across forks | GitHub: public preview, not across forks. GitLab: a CLI experiment. Graphite: GitHub only. |
Checked on 23 October 2026 against each vendor's own pages. The full chart, with a source for every cell.
Self-hosting
Running in a few minutes, once it's out.
- Install Docker with Compose v2: Docker Desktop on Windows and macOS, or Docker Engine on Linux.
- Get Fettlecode and start it.
- Open it in a browser and create your account. The first person becomes the instance admin; sign-up is closed to everyone else unless you open it.
The settings, single sign-on and the GitHub connection are on the self-hosting page.
Not released yet. The Docker image and Compose file are part of the work for 1.0, and the source code isn't public. These are the steps we're planning.
# In the Fettlecode folder
docker compose up -dLicence
Free for you and your team.
Fettlecode will be free for personal use, and for organisations with up to 10 users, under the Fettle Community Licence. For now it's free for every organisation, whatever its size; later, larger ones will need a commercial licence, and get the same software: there are no feature tiers. Single sign-on, SCIM, the audit log, approval rules, code owners, the merge queue, stacked review and live editing are in every copy.
Free for you and small teams
- Personal use, and organisations with up to 10 users
- Every feature, with unlimited organisations and repositories
- Your code and data on your server, in plain Git repositories
Larger organisations
- Free for now, then a discounted commercial licence for organisations with more than 10 users
- The same software, with every feature
- Hosting and support planned for after 1.0; no prices yet
Status and roadmap
In development, and honest about it.
Fettlecode is being built in batches. The first three are done, and so is the GitHub baseline that came after them. It isn't ready for real work yet.
Working today
- Hosting and review: Git over HTTPS and SSH, stacks, revisions, approvals, discussions, code owners and the merge queue
- Accounts and access: organisations, teams, roles, branch rules, the audit log and every kind of single sign-on
- Tested against the real thing: integration tests drive the real Git client against a real server and database
Not yet
- A release: the source code and Docker image aren't public
- Live co-editing and CI, which are planned, not built
- Backups, upgrade guides, a security review and a screen-reader audit, which are the work for 1.0
| Batches 1 to 3 | Git hosting, stacked review, accounts and access, single sign-on, SSH, the browser editor, GitHub import and mirrors, notifications, discussions, code owners, blame and the merge queue | Done |
|---|---|---|
| 3b | The GitHub baseline: forks and templates, code search, releases and Download ZIP, and Git LFS | Done |
| Batch 4 | Edit together: live co-editing from inside a review, then one revision with everyone as co-authors | Next |
| Batches 5 and 6 | CI with results reused across rebases, secret scanning, signed commits; review history inside the repository, JSON export, more importers, AI you bring, an MCP server, review insights and Pages | Planned |
| 1.0 | A Docker image and Compose file, backups, docs, a security review, a performance budget and a screen-reader audit, then the first release | Planned |