Your GitHub Actions workflows, on machines you control.

Sailfork runs the workflows already in .github/workflows. Jobs run in isolated sandboxes on your own Linux machines, and spill over into your AWS or Hetzner account when those are busy.

See what will run before you switch

The compatibility report reads the workflow files on your default branch and lists anything that will not run here, what needs setup, and what may fail. It is in the repository’s settings, and on the Runs page when a repository has no runs yet.

What runs

  • Push, pull request, schedule and manual triggers
  • Matrix jobs
  • JUnit test reports on every run
  • A GITHUB_TOKEN for each job, scoped by the workflow's permissions and revoked when the job ends
  • Environments, secrets and approval gates before a deploy
  • Live logs, rerun and cancel from the web app and the CLI
  • A plain message when a job ran out of memory
  • Artifacts kept for 30 days

Drydock, one daemon on your machine

Drydock is a daemon you install on a Linux machine. It dials out to Sailfork, so a machine behind NAT works with no open port. It updates itself from releases whose signatures it checks first, and on bare metal with KVM it runs gVisor on KVM. Organization owners set limits, allowed images and network rules for every host.

Isolation

Each job runs in a gVisor sandbox. Traffic to private ranges, cloud metadata addresses and mail ports is blocked. Each host rechecks those rules every 10 seconds, and a canary job tries the forbidden destinations for real every 10 minutes. A host whose firewall is not intact stops taking jobs.

Fast repeat runs

Caching is opt in, through actions/cache and the cache option of the setup actions. Sailfork speaks both of GitHub’s cache protocols and keeps up to 10 GiB per repository. Your machines can also keep a warm image baked for a repository, so setup does not start from nothing.

Sandboxes for agents

The same machines run the test commands your agents start, and serve public preview links for a port of a running sandbox, so a reviewer can open what the agent built.

Where jobs run

Sailfork hosted

Sailfork's own machines, billed per second. Turn it on in the organization's CI settings once billing starts.

Your Drydock machines

Laptops, servers and bare-metal hosts you run. Personal repositories use hosts registered under your handle.

Your AWS or Hetzner account

When your machines are busy, jobs spill over into a cloud account you own.

Your Depot account

An organization can connect its own Depot account and run jobs there.

Questions

Loading Sailfork