Security and data
Isolation
Section titled “Isolation”Every fork is its own Firecracker microVM: its own kernel, its own memory, its own network namespace, a private copy-on-write disk restored from the snapshot. Forks cannot see each other, the host, or any other customer. Inside the VM your services run under Docker exactly as the recipe says.
The snapshot a fork restores from is immutable; a fork writing to its disk changes only its own copy.
Network
Section titled “Network”- A fork reaches the internet outbound (to pull packages, call third-party APIs). Inbound, only HTTP through the edge reaches it:
https://<id>.forkstage.runto the app’s port,https://<id>-<port>.forkstage.runto other HTTP ports. Databases and queues are never exposed. - The address works for anyone who has it while the fork runs. Do not bake customer data.
- TLS on fork addresses is a wildcard certificate from Let’s Encrypt, renewed automatically; a watch outside our network checks it every 15 minutes.
What we store
Section titled “What we store”| What | Where | For how long |
|---|---|---|
| GitHub login, name, id, avatar, verified email | control-plane database (Amsterdam) | while your account exists |
| Recipe text, stack name, repository name, folder | control-plane database | while the stack exists |
| Repository source and snapshot (code, seed data) | the host that baked it (Frankfurt), encrypted-at-rest disk | while the stack exists |
| Fork records: who, when, ready time, how it ended | control-plane database | 24 h on the dashboard, counted monthly |
| Proofs: commands, exit codes, output tails, tests | control-plane database | 30 days |
| API tokens | hashed (SHA-256); the plain token is shown once | until revoked |
| GitHub App installation ids and repository lists | control-plane database | while linked |
We do not read, train on, or share your code. Pull request diffs are fetched with a short-lived installation token, applied inside the fork, and not stored.
Secrets
Section titled “Secrets”- The CLI stores your workspace token in
~/.forkstage/config.jsonwith owner-only permissions. - Hosts are credentialed from the control plane’s environment, never from the database or a repository.
- The shell’s WebSocket uses a 60-second ticket signed with the host credential; the credential itself never leaves the control plane.
Access to your workspace
Section titled “Access to your workspace”Sign-in is GitHub only. Workspace admins manage limits, tokens and GitHub installations. Non-members get “no such workspace”, never a hint that it exists.
Reporting
Section titled “Reporting”Security concerns: security@forkstage.com. We acknowledge within two working days.