Build a Git product

Amendable hosts repositories. You ship the product. Typical shapes:

• Internal Git portal with your review rules
• AI coding product that creates a repo per session
• Vertical Git (CAD, packages, maker files) with your own viewer
• Git embedded in a SaaS, one repo per customer

Suggested backend loop

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, CAD export, 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.

What you should not rebuild

Problem	Use
Git storage	Amendable HTTPS remotes
Auth for agents	Access tokens or OIDC exchange
Notify CI	Webhooks + HMAC
Object location	Platform S3 or BYO
Human glance at files	https://amendable.io/r/... while you build a nicer UI

What you still own

• Accounts, billing, and permissions for your customers
• Review UI, diffs, comments
• Build runners
• Domain-specific previews (STL, packages, notebooks)

Platform plan is the catalog SKU aimed at ISVs (500 active repos, 200 GiB, 500 GiB transfer). Talk to support@amendable.io if you need SSO or committed volume.

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