What you gain, what you give up today, and what comes with you when you move.
Comparison
Feature
Sailfork
GitHub
Price per seat
No charge per seat. Plans are metered by storage.
Team is $4 and Enterprise is $21 per user a month. Source
Where the agent runs
On the server, against the agent’s own branch, so nothing is cloned. Tests run in a sandbox on your machines.
Copilot cloud agent runs in a cloud sandbox, or in a GitHub Actions-based environment. Source
Hold an agent’s write at a path until a person approves
Yes. A path rule set to ask holds the write until a person approves it in the browser.
Not documented. The agent works on one copilot/ branch, and workflows on its pull request wait for a person. Source
Path rules on pushes
Path rules for agents and branch rules for pushes.
Rulesets can restrict file paths and require reviewers by path. Required reviewers is not available on user-owned repositories. Source
Hosted MCP server
Yes, 108 tools, OAuth sign-in and a read-only endpoint.
Yes, at api.githubcopilot.com, with OAuth and a read-only mode. Source
Stacked pull requests
Yes.
Yes, generally available on every github.com plan since October 6, 2026. Source
Full clone, medium repository
1.56 seconds. Sailfork’s own test, 2026-11-05.
2.36 seconds, same test.
CI compute
Sailfork hosted at $0.012 per unit-hour (1 vCPU with 2 GiB), billed per second, or your own machines, your AWS or Hetzner account, or your Depot account at no charge from Sailfork.
Hosted Linux runners cost $0.006 a minute for two cores. Self-hosted runners have no per-minute charge. Source
An opt-in push rule that matches ten credential shapes.
Push protection blocks secrets before they land. It needs GitHub Secret Protection and is off by default. Source
GitHub cells checked against GitHub's own docs on November 13, 2026, and rechecked monthly.
As of November 13, 2026, neither GitHub nor GitLab documents holding an agent's write at a path until a person approves it. GitLab flows, GitHub Copilot cloud agent
What GitHub does better
GitHub has the larger ecosystem: the Actions marketplace, integrations built for it, hosted runners, stars and follows, and years of maturity that Sailfork does not have yet. If your team depends on any of those, check them first.
When you move
Comes with you
Every branch and tag, with full history
Pull requests and their reviews
Issues, labels, milestones and releases
Wikis, collaborators and teams
Git LFS objects
Branch protection, rulesets and the merge queue
Stays behind
Secrets: set them again on Sailfork
GitHub Actions marketplace actions that call api.github.com
Stars and follows
Anything that depends on the CODEOWNERS file format