Git hosting built for teams that ship with agents.

Repositories, reviews, issues and CI in one place. Your agents edit code on the server, with no clone and no sandbox. A write to a path you protect waits for your approval before it lands.

Create free account Move from GitHub Your workflows keep running
  1. Retry failed webhook deliveries with backoff, five tries at most.

  2. agent/retry-webhooks

    caisson on acme-pay/api

  3. "fetch\(.*hook" src/

    src/webhooks/deliver.ts:31: const res = await fetch(hook.url, {

    src/webhooks/replay.ts:12: await fetch(hook.url, init)

  4. rg -l "deliver\(" src | xargs wc -l | sort -rn | head -2

    exit 0 (38ms)

    412 total

    188 src/webhooks/deliver.ts

  5. src/webhooks/deliver.ts

    +22 −6

  6. bun test src/webhooks

    exit 1 (4812ms)

    (fail) gives up after five tries: expected 5 calls, got 6

  7. src/webhooks/deliver.ts

    +1 −1

    43 43 export async function deliver(hook: Hook, event: Event) {
    44 − for (let attempt = 0; attempt <= max; attempt++) {
    44 + for (let attempt = 0; attempt < max; attempt++) {
    45 45 const res = await fetch(hook.url, { method: "POST" });
  8. bun test src/webhooks

    exit 0 (4390ms) 37 pass

  9. the diff, as an adversary

    approve 0 findings

  10. Retry failed webhook deliveries

    pull request #419

  11. claude-code · token ci-bot

    named on every commit

  12. db/migrations/0042_webhook_attempts.sql

    held for approval: db/migrations/

  13. db/migrations/

    approved by a reviewer

  14. Retry failed webhook deliveries

    merged

  • No seat charge
  • Runs your GitHub Actions workflows
  • Works with Claude CodeCursorVS CodeChatGPT
  • 0 trackers

Everything between push and merge

One agent, start to finish

100 µs

To open a caisson, an agent’s own branch and unsaved edits kept on Sailfork. No sandbox starts, so nothing waits on a clone.

How caissons work

In a sandbox

2 h billed

In a caisson

No machine

  • Starting: clone and install
  • Editing files
  • Waiting on the model
  • Left running
One example task. Only the dark blue needs the files; the dashed line is the agent waiting with nothing running for it.
1 µs
Read a file
10 µs
Write a file
500 µs
Commit

You decide what agents can touch

Mark any path allow, ask or never. A write to an ask path waits until a person approves it. Every agent commit names the agent and the token it used, and any agent action can be undone for 24 hours.

Path policy for agent writes
PathRuleWhat happens
src/allow
db/migrations/ask
.github/never

Each clone is copied, not computed

Sailfork stores a repository as pack segments when you push, and a clone sends them as stored. Stock git builds a pack for every clone.

1.89 s vs 8.89 s

Linux kernel full clone, Sailfork against stock git 2.54 on the same machine. Server time, median of 5 runs on one Apple M4 Max.

1.56 s vs 2.36 s on GitHub

Full clone of f-droid/fdroidserver over the network from one Mac in San Francisco, 2026-11-05.
Every number and how we measured it

Still plain git, and tested to stay that way

A push is acknowledged only after it is stored and recorded.

  1. Push arrives
  2. Durable in storage
  3. Recorded
  4. Acknowledged
If git says a push went through, it is already stored and on the record.

git’s own test suite

pass

Run against git clients 2.26 to 2.54.

0 differences

4,533 randomized histories, each checked against stock git

0 lost

2,763 pushes through a database failover during a push storm

Bring everything from GitHub

Move one repository, your whole account or an organization. Pull requests, reviews and issues come with you, and their numbers carry on from GitHub’s. Keep the GitHub copy as a mirror while you decide.

Authorize GitHub

Pay for storage, not seats

Free for 5 GB. Pro is $12 a month for 50 GB. Every feature is in every plan, and every plan is free during early access.

See pricing

Where your code lives

And everything Sailfork keeps about you while it is there.

Los Angeles
Servers on Fly.io in Los Angeles, the database on Fly Managed Postgres, and repositories in Tigris object storage.
1 cookie
A session cookie, set only when you sign in
0 trackers
No advertising or tracking cookies
0 analytics
No analytics scripts on any page

FAQ

Loading Sailfork