Build a Git product

Amendable hosts repositories. You ship the product.

BeanHub and MakerRepo are built on the same engine Amendable provides: layer-based Git storage, HTTPS remotes, the HTTP API, and webhooks. They are not lookalikes. They run this store.

• BeanHub is Git-backed accounting. Users keep Beancount books in a real Git repo. BeanHub owns the book UI, imports, forms, and inbox.
• MakerRepo is Git for manufacturing as code. Users push Python CAD (Build123D). MakerRepo owns the model viewer, artifact builds, and the maker workflow.

You do the same: accounts, billing, and a domain-specific UI on your side. Amendable is the Git store. How those objects are packed is in How Git is stored and How BeanHub works, part 2. Each push is an immutable layer, so auditable history survives a force-push that rewrites Git.

Other shapes look like that too: an internal portal with your review rules, an agent product that creates a repo per session, or Git embedded in a SaaS (one repo per customer).

Suggested backend steps

1. When a customer (or agent session) starts, POST /v1/repositories with a unique name.
2. Mint a SELECTED_REPO token with GIT_HTTP_READ / GIT_HTTP_WRITE for that repo only, or exchange OIDC from the runner.
3. Hand the clone URL plus credentials to the agent or to your UI.
4. Register an account webhook once. On push, run your pipeline (tests, builds, preview).
5. When the session ends, DELETE the repo if it was ephemeral.

Tip

Create the webhook at account setup, not per repository. It already fans out to every repo you own.

Clone URL

Git clone and push use:

https://amendable.io/r/<username>/<repo>.git

Your product UI can live on your own domain. Git still talks to amendable.io. Custom Git hostnames are coming later.

If you want to

You want to	Use
Create repos, clone, and push	Git over HTTPS
Read a file without cloning	Fetch files
Let an agent or CI talk to Git	Access tokens or OIDC
Run a job when a ref moves	Webhooks
Keep Git objects in a bucket you own	Bring your own S3
Keep an audit trail when Git history is rewritten	Auditable history

What you ship

• Accounts, billing, and permissions for your customers
• Review UI, diffs, comments, and the file views those customers see
• Build runners
• Domain-specific previews (Beancount books, STL, packages, notebooks)

The Amendable browse site at https://amendable.io/r/<username>/<repo> signs in as your Amendable account. Your customers do not get Amendable logins. They use your product.

Start on Pro. Metered overage covers larger stored history and clone traffic. Active repositories are unlimited for typical use. If you need SSO, committed volume, or custom limits, email support@amendable.io for Enterprise.

Amendable does not train models on your repositories. You own your Content.