Personas
Who it's for
The Regulated-Enterprise Platform Engineer
Lead persona- The pain
- Engineering wants to ship agents. Security says no containers. Compliance says no managed sandboxes. The internal answer is to manually review every agent action — which makes agents useless.
- What they need
- A hardware-isolated execution environment they own, with audit evidence for auditors, that runs in their VPC.
The Mid-Market Compliance-Driven Buyer
Leading indicator- The pain
- Same problem, but no platform team big enough to self-host. They want a product, not an infrastructure project.
- What they need
- A hosted confidential agent runtime with regional residency. The compliance posture without the ops burden.
The Agent Framework Builder
Adopts, doesn't buy- The pain
- Needs an execution backend for their framework. Managed SaaS only or AGPL licenses are blockers.
- What they need
- A well-documented, Apache-licensed sandbox they can wire into LangChain, Mastra, or custom frameworks.
The SaaS Builder Optimizing Unit Cost
High-volume adopter- The pain
- Runs millions of short-lived agent tasks. Cares about predictable margins and density.
- What they need
- The runtime for cost reasons; the control plane for multi-host orchestration. Not a confidential buyer.
The Security Researcher / Threat Modeler
Credibility signal- The pain
- Evaluates sandboxes for red-team labs, malware handling, CTF infrastructure.
- What they need
- A published threat model + attestation chain they can review independently. Their endorsement drives enterprise sales.
Who it's NOT for
- • Hobbyist on macOS expecting native Firecracker (Linux + KVM only)
- • Customer wanting a drop-in E2B API replacement (self-hosted first)
- • Buyer of a fully turnkey AI platform (Enclave is infrastructure)