We run your code and move your money. Both are designed for.

Deployed apps and workers run in isolated container runtimes (Google Cloud Run) and hardened sandboxes (E2B) — never alongside platform services. An app gets its own scoped runtime credentials and its own storage namespace; it cannot reach another app's data through the platform surface.

All user-originated outbound requests pass an IP-level guard evaluated at connection time — blocking access to internal networks and metadata services and defeating DNS-rebinding tricks, not just hostname filters. Every user-URL path on the platform goes through this guard.

All spending is prepaid Aev with hold→capture settlement: funds are reserved before work runs and captured only for work that completes. Database-level uniqueness guards make double-settlement structurally impossible, retries are idempotent, and failed metered calls are automatically refunded to your balance. Delegated spending (end-user-pays) fails closed: if authorization can't be verified, no money moves.

App runtime secrets are provisioned into Google Secret Manager and mounted by reference — they never land in your source, the app manifest, container image layers, URLs, or the browser. Platform API responses are redacted against known secret material as a second line of defense.

Sign-in uses OAuth with RS256-signed OIDC tokens. API authorization happens at centralized chokepoints — not scattered per-endpoint checks. Deployed apps receive derived, per-app scoped keys rather than your account key, and sessions can be revoked server-side.

Background work is panic-isolated so one bad job can't take down the platform. Settlement and deployment state live in the database, not process memory: if a component restarts mid-flight, reconciliation sweeps converge every in-flight hold and deployment to a correct state in bounded time.