Your compute, your account,
your credentials
SAM separates the control plane from compute. Your agents run on VMs in your cloud account. Self-hosters deploy everything to their own Cloudflare account. Credentials never leave your boundary.
Bring Your Own Cloud (BYOC)
SAM doesn't provision VMs using platform credentials. Users provide their own Hetzner, Scaleway, or GCP tokens, which are encrypted per-user with AES-256-GCM and a unique IV per credential. The platform never has access to your cloud accounts.
This means agents run on infrastructure that's already covered by your existing cloud contracts, security certifications, and regional compliance. No new vendor to evaluate for where your code actually executes.
Credential Isolation
Every credential is encrypted individually in the database with its own initialization vector. Credentials are never stored as environment variables, platform secrets, or shared state.
Agent API keys and OAuth tokens can be scoped at the user level or overridden per project. When an agent needs a key, SAM resolves it through a tiered lookup: project-specific first, then user-level, then platform default. An inactive project credential blocks fallthrough — it doesn't silently fall back to a broader scope. Cloud provider tokens are scoped per-user.
| Credential | Scope | Encryption |
|---|---|---|
| Cloud provider tokens | Per-user | AES-256-GCM, per-credential IV |
| Agent API keys | Per-user or per-project | AES-256-GCM, per-credential IV |
| OAuth tokens | Per-user or per-project | AES-256-GCM, per-credential IV |
Self-Hosted Control Plane
For organizations that need full ownership, SAM's control plane can be deployed entirely to your own Cloudflare account. The deployment uses Pulumi for infrastructure-as-code and GitHub Actions for CI/CD.
When self-hosting, all data lives in your Cloudflare account's D1 databases, KV namespaces, and Durable Objects. No data flows through SAM's hosted infrastructure.
What About Message Data?
Today, agent session data and chat messages are stored in Cloudflare Durable Objects. For hosted platform users, this means message data resides in Cloudflare's infrastructure. For self-hosters, it resides in their own Cloudflare account.
We're building pluggable storage backends so organizations can route message data to their own databases. Until then, self-hosting gives you full control over where the entire stack runs.
Ready to run multi-agent workflows at scale?
Self-host on Cloudflare's free tier. Bring your own cloud. Your agents, your infrastructure.