Code should move as fast as the people and agents writing it.

Sailfork exists to take the waiting out of git: for you at a terminal, and for every agent that edits your code.

The wait we remove

Stock git counts objects and builds a pack before it sends anything, then does it again for the next clone. Sailfork builds the pack once, when you push.

An agent waits on the same work: a clone, a sandbox, a machine that starts before the first edit. We take that wait out too, so changing three lines costs three lines.

See the numbers and how we measured them

What we believe

Do the work once
A clone of the same commit is the same bytes every time. Sailfork builds the pack when you push and every clone after that is a copy.
Agents work in the repository
An agent changing three lines should not need a full clone and a sandbox. A caisson is an agent’s own branch and its unsaved edits, kept on Sailfork; the agent reads and writes through the API, so nothing is cloned and no machine starts.
Leaving should be easy
Plain git goes in and plain git comes out. Moving in keeps every commit hash, so moving out keeps them too.
Show how it was measured
Every speed claim on this site comes with the machine, the git version and the command behind it.

What we will not do

Lines we hold even when crossing them would be easier. Who builds Sailfork

  • A client you have to install

    Stock git over HTTPS and SSH is enough. The sailfork CLI and remote helper are optional.

  • Tracking

    One session cookie when you sign in. No analytics scripts, no advertising cookies.

  • Promises we cannot back

    No uptime guarantee during early access. Live status is at sailfork.com/status. With git, you already keep a full copy.

  • Hiding what is missing

    The roadmap lists what Sailfork still lacks next to GitHub, in the order we plan to build it.

How to hold us to it

Three pages we keep current, so you can check the work instead of taking our word.

Loading Sailfork