Architecture.
Handled Cloud deploys infrastructure into your Cloudflare Account, defined as a "Handled Stack". This Handled Stack consists of Cloudflare Workers, Durable Objects, and KV instances. The key entrypoint to a Handled Stack is a Reverse Proxy worker, which is bound to one or more hostnames you can configure through the dashboard.
The Handled Stack works with any OIDC Identity Provider to handle Identity behaviours and API Security for your application at the edge. The Handled Stack is configured through the dashboard, allowing you to configure environments, branches, and origins. The dashboard supports SSO with your organisations Identity provider to allow for secure access.
Environment configuration.
One Handled Stack can have many environments configured, allowing organisations to integrate and assure their applications before they reach production. Each environment is bound to one or more hostnames, and configurable completely independently from others.
Each bound hostname resolves to the environment you choose. A primary domain and a vanity domain can resolve to one environment: app.example.com and shop.example.net both serve the same identity stack.
To avoid unintended changes to the live environment, configuration changes happen on branches. To change an environments configuration you open a branch, make some changes to origins or configuration, test them, and open a merge request for review. The number of approvals you need is configurable per environment.
Ready to deploy into your Cloudflare account?