Core Execution Engine (Local/Staging)
DAG parsing, state machine transitions, and Saga compensation logic verified and passing all stress tests.
✓verified Oct 24, 2026 · 101-step stress test · unedited recording
Core Engine & Staging Environments Operational
The Escepine core execution engine, MCP sandbox, and documentation hub are fully verified and operational for local staging and client-hosted deployments.
Last verified: Oct 25, 2026·local-first·client-hosted
Components
verification eventsOperational
Policy Gateway (Cedar Runtime)
Policy evaluation layer compiled and tested against current schema deviations.
✓verified Oct 22, 2026 · Cedar policy suite · deny-path tested
MCP Sandbox Orchestrator
Ephemeral container provisioning for external tool execution is active.
✓verified Oct 23, 2026 · sandbox provisioning smoke test
Public Documentation Hub
Architectural docs, research papers, and security specs are live and globally distributed.
✓verified Oct 25, 2026 · deployment check · escepine.vercel.app
Deployment Architecture & Data Sovereignty
Unlike standard SaaS AI platforms, Escepine does not host your workflows, tools, or data on shared infrastructure.
01 · Air-Gapped Staging
Our core engine runs in isolated, local staging environments for initial workflow mapping and stress-testing. Your proprietary data never leaves your perimeter during the evaluation phase.
02 · Client-Hosted Production
For production deployments, the Escepine execution plane runs inside your own VPC (AWS / GCP / Azure) or on-prem. We provide the engine; you own the infrastructure. Zero data egress, complete air-gapping of your agentic workflows.
Incident History
No incidents reported.
We maintain a transparent incident log. If an operational issue occurs, it will be documented here with real-time updates, root-cause analysis, and a full post-mortem.
0 incidents
0 degraded minutes
Subscribe to Updates
Get notified when components experience degraded performance or scheduled maintenance.