Tenant isolation
- Every operation on tenant data requires and filters by the organization
- Requests for another organization's resources answer not found
- Every API route maps to a permission that is checked on the server
Security
Built so one organization never sees another.
BeansHost is a control plane for production agents, so isolation, encryption and an honest record are part of the design rather than settings you have to find.
How BeansHost protects your organization
Six layers, enforced on the server.
Encryption
- Environment variables encrypted with AES-256-GCM
- AWS keys, AWS session credentials and Azure tokens encrypted the same way
- Values are never displayed again after you save them
API keys
- Shown once and stored only as a SHA-256 hash
- Scoped to calling agents or reporting runs, and optionally to one agent
- Expiry from 30 days to never, and revocable at any time
Access
- Email and password sign-in with a six-digit verification code
- Seven built-in roles with fixed permissions
- Only owners change owners, and the last owner cannot be removed
Audit
- Privileged actions written with actor, result and status code
- Rows cannot be changed, or deleted inside the 365-day window
- Secret values are never written to the log
Data minimization
- Prompts and responses are never stored
- Run records hold status, duration, provider, error category and byte counts
- Agents run in your own cloud account, not in the control plane
Platform protections
Defaults that hold up under real traffic.
The control plane runs on Cloudflare Workers with data in Neon Postgres. Internal services talk over private service bindings and are not reachable from the public internet.
- Sign-in throttling with exponential backoff per address and per account
- Rate limits per address and per user at the API gateway, and per plan for agent calls
- Request bodies capped at 5 MiB at the gateway and 1 MiB for agent calls
- OAuth state bound to the browser that started the connection
- Content Security Policy and HTTP Strict Transport Security on the console
- AWS connections through a cross-account IAM role with an external ID
- Azure connections through Microsoft Entra, with no passwords to paste
- A circuit breaker pauses calls to an agent after repeated failures
Transparency
What we will tell you straight.
BeansHost is in early access. We would rather you know where the product stands than discover it later.
No certification yet
The platform has not been independently audited and does not hold a compliance certification today. We publish what the product does, and we will say so when that changes.
Your cloud, your controls
Because agents run in your Vercel, Render, AWS or Azure account, your existing provider controls, network rules and billing alerts still apply to them.
Responsible disclosure
Found something? Email security@beanshost.com with the details. Please give us a reasonable chance to fix it before sharing it publicly.