01
Every workspace is its own microVM
Your agents never share a machine with anyone else’s.
- Each workspace runs in an isolated microVM with its own kernel, memory, disk and processes.
- Workspaces share nothing unless you attach the same shared volume to them.
- Your machine and project templates are private to your account.
02
Logins stay yours
Agents use your accounts without ever seeing a password.
- Import from 1Password, Bitwarden, macOS Keychain or hsec: sent end to end, Shardflux only relays encrypted bytes.
- You approve each login: allow once, or always for this project.
- Remembered logins are encrypted with AWS KMS, filled straight into the page and logged on every use.
03
Secrets are encrypted
Environment secrets reach only the project they belong to.
- Imported secrets are encrypted with AWS KMS; only that project’s workspaces can load them, and every load is logged.
- Tool output that touches a bound secret is redacted before it is stored. If redaction fails, the call is dropped.
- Claude and Codex sign-ins are delivered privately when an agent starts. Your laptop’s login stays separate.
04
Private by default
Nothing in a workspace is reachable until you share it.
- Every port is private. Previews and live desktops open through private links that expire.
- Outbound traffic can be limited to an allow list of destinations per project.
- All connections to the service use TLS.
05
Account protection
Sensitive actions ask for proof that it is really you.
- Two-factor sign-in with an authenticator app, and recovery codes.
- Exports, deletions and security changes need a fresh confirmation (step-up).
- Owners and admins manage who is in your organization.
- An audit log records requests and their results, and you can export it.
06
Your data
Where it lives, who processes it, and how it is deleted.
- Workspaces and the API run in AWS US West (Oregon).
- No advertising or analytics cookies on the site or the console.
- Delete workspaces at any time. At the end of the service, you choose return or deletion.
- A Data Processing Addendum covers your content, with 30 days’ notice before a new subprocessor.
