One account.Nothing shared.
Each account gets its own workspace, its own storage and its own machine. Here is how that is enforced, where your data goes, and what we are still building.
How accounts are kept apart.
Accounts
Each account has its own workspace and storage, addressed by a key derived from the account id. A request is tied to an account before a workspace is chosen, and one that can't be is refused.
Machines
A Linux machine belongs to one workspace and is never shared between accounts. Its disk is wiped whenever it sleeps.
Network
Machines reach the public internet. Cloud metadata services and private addresses are blocked.
Keys
The platform's model key never reaches the browser. Keys you add are stored encrypted in your workspace's own store.
Admission
An account runs nothing until it is admitted: no workspace, no plan and no compute.
Where your data goes.
Storage
On Cloudflare: accounts and billing in a D1 database, each workspace in its own store, machines on Cloudflare Containers. Card details stay with Stripe.
Model requests
Each turn's context goes to the provider that serves it: DeepSeek on our key, or the provider of a key you add, under their own terms.
Tools and plugins
Tools and plugins receive what their requests carry, under their own terms. Review them before working with sensitive material.
Signing in.
Sessions
Pages are served over HTTPS. The session cookie is HttpOnly and Secure, the sign-in API accepts only this site's origins, and repeated attempts are rate-limited per address.
Passkeys and codes
Sign in with a passkey, or turn on an authenticator app so a password alone is not enough. Backup codes cover a lost phone, and adding a passkey or managing billing asks for your password again.
Still to build
There is no list of sessions to sign out one by one yet; resetting your password signs out every other session. A guesser spread across many addresses is not stopped by the per-address limit alone.
Report a problem.
Write to support@delorun.com with what you found, how to reproduce it and the impact you expect. Don't test against other people's accounts, and don't run anything that degrades the service for others.
There is no paid bounty. Reports are read, acknowledged and fixed, and a real finding is credited on request.