Six levers that amplify the open core without reintroducing regional VMs.
01Multi-tenancyUpcoming
Workers for Platforms
True multi-tenant isolation: Dispatch Worker routes by tenant claim / subdomain to isolated User Workers per fund, strategy book, or customer.
- ▸Namespaces, tags for metering and billing
- ▸Per-tenant DOs, Queues, D1/R2 paths, secrets
- ▸Synchronous first deploy — routable when HTTP 200
- ▸Hosted SaaS or dedicated Enterprise account
Docs ↗02Durable executionUpcoming
Cloudflare Workflows
Long-running, step-persisted trade and compliance processes — hours to days — with retries, pause-for-external-events, and human approval gates.
- ▸Full trade lifecycle: validate → risk → execute → reconcile → report
- ▸Atomic kill-switch + flatten sequences
- ▸Compliance reports with approval gates
- ▸Post-trade reconciliation across exchanges and storage
Docs ↗03ComplianceUpcoming
Logpush · Traces · R2 Audit
Regulator-grade observability: Workers Trace Events, HTTP, WAF, Queues, DOs pushed immutably to R2 or SIEM with long retention.
- ▸One-click R2 Logpush + custom fields
- ▸Tail Workers for sample / filter / enrich
- ▸End-to-end traces across Bindings, DOs, Queues, Workflows
- ▸Analytics Engine for metrics; Logpush for audit
Docs ↗04Layers 0–5+Upcoming
Extended Security Stack
Open-core five-layer model plus Enterprise Bot Management, API Shield, Zero Trust Access, mTLS, and AI guardrails.
- ▸Bot scores, JA3/JA4, verified bots on signal ingress
- ▸API Shield: schema, JWT, mTLS, sequence mitigation
- ▸Access SSO, SCIM, device posture for ops surfaces
- ▸AI Gateway: sanitization, rate limit, cost control
Docs ↗05Real-timeUpcoming
Hibernatable WebSockets
Persistent exchange connectivity via Durable Object hibernatable WebSockets — live fills, partials, and books without burning CPU while idle.
- ▸ExchangeConnectionManager DO pattern
- ▸Event-driven risk beside (or instead of) cron
- ▸Cheap keep-alive while DO sleeps
- ▸Pairs with Workflows for durable stream handling
Docs ↗06Limits · AI · DataUpcoming
Institutional Scale
Higher CPU, memory, subrequests, D1/R2/Queue/Vectorize quotas, AI Gateway at volume, and data residency controls on R2.
- ▸Custom limit increases via account team
- ▸AI Gateway logging, caching, multi-provider failover
- ▸R2 jurisdiction + lifecycle for immutable audit
- ▸Hyperdrive for hybrid historical data if needed
Docs ↗