Clear steps. Separate boundaries.
Review Durin’s deployment sequence for separate Workers, tenant resources, identity, provider consent, billing, and recovery evidence.
Verify each boundary before activation.
A production Durin deployment is ready when its account, identity, tenant, provider, network, billing, retention, and recovery prerequisites are each verified.
- Phase 1
Deploy independent surfaces
Website, application, management API, and MCP gateway are separate Workers. Internal tenant, credential, job, mail, and provisioning responsibilities remain private and authenticated.
- Phase 2
Provision and verify the tenant
Reserve tenant identity, allocate dedicated resources, apply migrations, configure retention and encryption, deploy scoped bindings, and run isolation checks.
- Phase 3
Verify the managed path
Configure identity, upstream consent, reviewed schemas, exact client versions, network controls, email, billing, retention, backup, restore, and incident procedures.
Turn trust questions into checks.
Create an account to manage deployment boundaries, provider setup, identity, network coverage, and operational responsibilities.
Create an accountProduction connections use provider setup and trust review.