Quickstart

Pay-per-use Git for agents · No seats

Let agents branch.Keep main pinned.

Private Git repositories for your agents and your product’s users. Create as many as you need, decide who may touch each one, and pay only for the bytes stored and sent. Never per seat.

Planned launch rates$0 per seat∞ repositoriesrepos$0.001per GiB-hour
Agent prompt

Documented steps only. No secrets in chat.
PR 1-17PR 1-18mainprotected━ agent/docs-refresh━ agent/fix-auth
mainprotected
At launchNo per-seat feesUnlimited repositoriesNo repository size tiersEmbed with the APIScoped, expiring keysPull requests. Protected main.

01 / PRICING

Pay for bytes,
not seats.

One rate card. No plans to outgrow.
Keep as many repositories as you need.

Planned launch rates. Public account setup and charging are not open yet.

Storage

$0.001

per GiB-hour

Physical Git data, measured hourly.
Keep it for an hour or a year.

Outbound transfer

$0.02

per GiB

Bytes sent out by Gitpin.
Inbound transfer is included.

Everything else

$0

no per-seat fees

  • Seats
  • Repositories
  • Scoped keys
  • API requests
A small, real example

1 GiB stored for 30 days = $0.72.
Transfer is extra. Delete the bytes and storage stops when removal is confirmed.

How billing works

USD, before tax · rate card gitpin-usd-v1 · $5 collection threshold, with twelve-month or account-closure settlement · 1 GiB per push · soft organisation storage quota applies.

02 / BUILT ON GITPIN

One Git API,
many products.

Git is a useful primitive.
Your users don’t need to know it’s there.

01 / KNOWLEDGE

Wikis and
knowledge bases.

A repository for every space. Every page has a history. An agent’s suggested edit is a pull request you can review, merge or leave alone.

50 MiB wiki ≈ 4¢ / month in storage.
Storage only. Transfer is extra.

acme / handbookprivate

How we ship

Small branches. Clear changes.
A main branch we can trust.

− Push directly to main.
+ Open a pull request for review.
Suggested by agent/docs-refreshready to review
02 / MEMORY

AI memory
with a history.

A memory repository for every agent or end user. Remember something, update it, learn from it. Roll back a bad write without losing the trail.

10,000 users × 5 MiB ≈ $35 / month in storage.
At the planned rate. Transfer is extra.

memory / user-1042main
Remember

Prefers concise answers

Update

Working on the October release

Learn

Uses Python and TypeScript

Revert

Restore the previous preference

03 / YOUR PRODUCT

Inside your app.
Out of your way.

History, suggestions and restore, backed by Gitpin behind your backend. Give your users the workflow. Let Gitpin keep the versions.

See how embedding works
dDraftspace Example app
Product notesHistory · Suggestions · Restore

A better way to remember.

Your document, your editor, your users.
Gitpin is the version history underneath.

1 suggested changeFrom the writing assistant
Saved just now 12 versions

03 / EMBED GITPIN

Put Git inside
your product.

Your app owns the experience.
Gitpin owns the Git.

01

A repository per customer, workspace or job.

Keep histories separate without buying another seat.

02

Your access rules, enforced per key.

Issue a key scoped to the repository and the work it needs.

03

One bill, based on bytes.

Storage and outbound transfer, across your product.

Your backend issues scoped keys

Example access map

Customer A
workspace-a

read · write

30 days
Customer B
workspace-b

read · write

30 days
Review job
workspace-a

read · merge

1 hour
Search indexer
workspace-a

read

15 minutes

Keys stay in trusted runtime configuration.

04 / THE WORKFLOW

Ordinary Git.
Deliberate authority.

Your agent gets a branch.
Main keeps its boundaries.

1

Clone the repository.

Use HTTPS with a scoped key in your credential helper. Keep the secret out of URLs and commands.

terminal
git clone https://gitpin.dev/git/<repository-id>.git
cd my-project
2

Give the work its own branch.

Agents work in separate branches. A write key can push there without overwriting main.

terminal
git switch -c agent/docs-refresh
# make a small, focused change
git add . && git commit -m 'Refresh the docs'
3

Push the change.

Normal Git over HTTPS. No new transport to learn.

terminal
git push origin agent/docs-refresh
4

Open a pull request.

Compare the change and its history before it reaches main.

REST API
POST /v1/organizations/{org}/repositories/{repo}/pulls
{
  "title": "Refresh the docs",
  "head": "agent/docs-refresh"
}
5

Merge with a key that may merge.

No mandatory human approval gate. You choose who has the authority; Git still checks for conflicts.

REST API
POST /v1/organizations/{org}/repositories/{repo}/pulls/{id}/merge
Read the Git guide

05 / SCOPED AUTHORITY

A key for the job.
A boundary around it.

Choose the repository, capabilities
and expiry. Narrow them as you delegate.

read

Clone, fetch and inspect history.

write

Push work to your branches.

merge

Merge a pull request into main.

replace

Replace history deliberately.

delegate

Issue a narrower child key.

publish

Append a change to protected main.

Parent key

Build agent

read · write · delegate

Repository: knowledge-base
Expires in 30 days

Narrower child key

Review helper

read

Same repository
Expires in 1 hour

A child can never gain authority its parent doesn’t have.

Understand scopes and delegation

06 / START WITH THE DOCS

Your next commit
starts here.

Read it yourself.
Or send your agent.

Agent quickstart

The current setup path, scoped keys and your first change.

The full picture

Concepts, Git, permissions, billing and recovery.

Agent prompt

Documented steps only. No secrets in chat.