Built on AWS with security, isolation, and scalability at every layer. Every operator runs in its own isolated environment — no shared compute, no shared data.
Channels
Messages arrive via any channel
OpFleet Platform
API Gateway
Auth & routing
AgentCore
Reasoning engine
Memory Layer
Persistent state
Tool Runtime
Secure execution
Processes, reasons, and orchestrates
Business Results
Outcomes delivered 24/7
<100ms
API latency
99.9%
Uptime SLA
256-bit
AES encryption
SOC 2
Compliance ready
Security
Every layer of OpFleet is designed with isolation and defense in depth. Not bolted on after — built in from the start.
Every operator runs inside its own Firecracker microVM — fully isolated compute, memory, and network. No shared anything.
4 security layers: network perimeter, compute isolation, data encryption, and content filtering. Each one independent.
62 adversarial tests across 12 attack categories — prompt injection, data exfiltration, privilege escalation. All defended.
Architecture designed for SOC 2 Type II and GDPR compliance. Audit trails, data residency controls, and encryption at rest.
How It Works
Three steps to a fully operational AI employee running on enterprise-grade infrastructure.
Define personality, skills, knowledge base, and communication channels. Choose from templates or build custom.
Your operator gets its own microVM on AWS, in your preferred region. Secrets, memory, and tools — all provisioned automatically.
24/7 operation with full persistent memory. Connects to your channels, learns your workflows, and executes autonomously.
System Data Flow
Message sent via Telegram, Slack, or email
Authenticates user, resolves identity & tenant, routes to AgentCore
Per-session container with Firecracker isolation. Boots in <5s.
PERSONA.md, IDENTITY.md, PLAYBOOK.md injected from operator config
Claude Sonnet 4.6 via Bedrock with full tool access (web, browser, code, files)
Progressive streaming back to user channel
Access our detailed architecture documentation — AWS topology, security layers, deployment flows, and data architecture.
The technical details page requires an access code. Contact us to request access.