A clone should be copied, not computed.

Every git host rebuilds the same pack for every clone. Sailfork builds it once, when you push.

Why Sailfork

Stock git spends 4.5 seconds counting objects and building a pack before it sends a byte of Linux, even with a bitmap, and then does it again for the next clone. Sailfork builds the pack once, when you push, so a clone starts in 0.14 ms.

A pack built from scratch The same history, cloned six times.

New

What it is building next

Caissons: online worktrees where agents edit the repository on Sailfork, each on its own branch, with no clone and no sandbox.

See how caissons work

  1. Open

    A caisson on a new branch

    open caisson

  2. Edit in place

    Read and write files on Sailfork

    edit invoice.ts

  3. Commit

    Saved to the branch

    commit "Round totals"

  4. Pull request

    Reviewed behind your branch rules

    #418 merged

The name

Sailfish

The fastest fish in the ocean

fork

Where every git project starts

Sailfork

Team

The people who build Sailfork and answer when you write.

Hover, click or tap for the photo.

Fenil Sonani

Founder. Builds and runs Sailfork.

San Francisco

AI and machine learning developer and entrepreneur. Founding AI engineer at GetMyHotels and former CTO of Archimedes IT. Reads every message sent through the contact page, and every deletion request.

Who runs it

One person, as an individual, and the one cloud region your code lives in.

Questions and deletion requests go to the same one person.

What it holds to

Plain git
No client to install and nothing proprietary in the protocol. What you push comes back out with stock git.
You own your code
You keep ownership of everything you push. Sailfork only stores, processes and sends it to run the service.
No tracking
One session cookie when you sign in. No advertising cookies, no tracking cookies, no analytics scripts.
Honest about limits
There is no uptime guarantee, and the terms say so. Keep your own copy; with git, you already have one.