CLOUDFLARE OS
From an idea to a running system
Cloudflare OS turns intent into a complete, governed application on Cloudflare's developer platform.
One deployment coordinates compute, state, intelligence, and access.
HOW THE SYSTEM WORKS
Each service is independent. Cloudflare OS makes them operate as one.
LIVE DEPLOYMENT
Watch the system appear
Deploy on the left. As resources become observable, the architecture comes online here.
DEPLOYED ARCHITECTURE
What each resource does
Ten Cloudflare resources, organized around four operating responsibilities.
Access perimeter
Access application
instance
Authenticates operators and applies policy before traffic reaches the application.
Worker runtime
App router
instance
Receives application traffic and directs every request to the correct runtime path.
Workshop API
instance-backend
Runs the core API and coordinates context, scheduling, state, content, and AI.
Context
instance-gk-context
Selects and governs the context made available to each operation.
Scheduler
instance-gk-scheduler
Coordinates deferred, recurring, and time-based work across the system.
State + content
Blueprints
instance-blueprints
Stores blueprint metadata and lookup records used to assemble experiences.
Avatars
instance-avatars
Stores avatar definitions and lightweight identity-oriented configuration.
Context collections
instance-context-collections
Organizes reusable context through collection metadata and references.
Blueprint content
instance-blueprint-content
Holds larger blueprint documents and content objects outside Workers KV.
Intelligence
Model control plane
instance-ai
Routes model calls while adding policy, visibility, and operational control.