Deployment & Residency
Central governance. Your choice of where it runs.
One governance model across the organisation, and data that stays where your regulator, your client agreements or your board require it to stay. These are not in tension, because the two planes are separable.
The plane split, without the architecture diagram.
The Control Plane holds identity, catalogue, manifests, policies, evaluations and releases. The Execution Plane runs the compiled plan and holds run state. They can live in different places. That is what lets you keep one governance model and still keep your data where it must stay.
Stays central, always
Control PlaneUser identity and role assignments Hub catalogue metadata Crew Manifests and versions Policy definitions Evaluation suite definitions Release records and checksums Credit ledger Audit index (pointers, not payloads)
Moves with your deployment model
Execution PlaneCase and matter content Knowledge Pack indexes and chunks Run state and checkpoints Retrieved evidence text Generated artefacts and drafts Model gateway request payloads Tool and Action payloads Audit record payloads
Five deployment models.
The same manifests, the same compiler, the same audit model in every one. What changes is where execution happens and who operates the infrastructure.
| Model | Where execution runs | Operated by | Typical buyer |
|---|---|---|---|
| KrewOS Cloud | Managed, shared, Singapore region | wGrow | SME and standard enterprise |
| KrewOS Cloud Dedicated | Managed, dedicated compute and storage | wGrow | Higher isolation or performance needs |
| Enterprise — Customer VPC | Your cloud account, your network | Jointly, under a runbook | Residency and private-system access |
| Enterprise — Hybrid | Central control, local runtime and knowledge | Jointly | Private data with managed governance |
| Enterprise — Private / Local | Your infrastructure, air-gap capable | You, with support | Restricted or disconnected environments |
Residency commitments.
Stated precisely, because a vague residency claim is worse than none — it fails the first time procurement reads it carefully.
Singapore is the default region
The workspace region is chosen at workspace creation and is immutable for that workspace. Moving regions means creating a new workspace and migrating, which we will help with but will not pretend is a toggle.
Model calls are constrained by policy
Every model profile declares its approved provider jurisdictions and the provider’s retention terms. A crew cannot route to a provider outside the profile’s approved set, and the routing decision is recorded on the run.
Customer-managed keys
Available on Cloud Dedicated and all Enterprise models. Not available on shared Cloud. We state which tiers rather than implying it is universal.
BYOK and private model adapters
Use your own provider contracts, or connect a self-hosted or regionally-hosted model behind the same model-profile policy, evidence and audit machinery.
| Capability | Cloud | Cloud Dedicated | Customer VPC | Hybrid | Private |
|---|---|---|---|---|---|
| Singapore-region execution | Yes | Yes | Your region | Your region | Your site |
| Customer-managed keys | No | Yes | Yes | Yes | Yes |
| Private network access to your systems | No | Peering | Native | Native | Native |
| BYOK model credentials | Yes | Yes | Yes | Yes | Required |
| Disconnected operation | No | No | Partial | Partial | Yes |
| Central governance across entities | Yes | Yes | Yes | Yes | Scheduled sync |