Running state
Release, configuration, models, capabilities, integrations, and operating boundary.
Set the operating boundarywithout surrendering authority.
The same Work can run in a Managed, Dedicated, or customer-controlled deployment. Choose where models, data, integrations, and operations live while Evidence, authority, history, and Settlement remain coherent.
ManagedDedicatedLicensed
Deployment
Change the environment, not the Work.
Where AI runs matters. So do the systems it can reach, the data it can use, the models it can call, and the people responsible for operating the environment.
A Refund Review or a long-running program should not have to be redesigned because infrastructure custody changes. Indwel keeps the operating model separate from the business logic, evidence, approvals, and completion state of the Work.
Deployment models
Choose where the Work runs.
Indwel has one operating system with three delivery models: Indwel Cloud as managed SaaS, an Indwel-operated Dedicated environment, and Licensed software for customer-controlled cloud or on-premises infrastructure, where contracted. The operating boundary changes; Work, Evidence, authority, history, and Settlement remain coherent.
| Deployment comparisonOperating modelInfrastructure custody and operating responsibility. | ManagedIndwel operatedShared cloud with enterprise isolation | DedicatedDedicated environmentDedicated infrastructure and private connectivity | LicensedCustomer operatedRuns inside customer-controlled infrastructure |
|---|---|---|---|
| Platform operations | Indwel | Indwel, dedicated environment | Customer or shared responsibility |
| Infrastructure custody | Indwel-managed estate | Customer-specific estate | Customer cloud or private infrastructure |
| Isolation | Tenant isolation | Dedicated environment | Customer-defined environment |
| Network architecture | Managed connectivity | Private and customer-specific connectivity | Customer-controlled networking |
| Encryption & keys | Managed controls | Customer-specific options | Customer-controlled options |
| Release cadence | Managed | Coordinated | Customer-controlled |
| AI & integration capabilities | |||
| Model access | Approved managed models and endpoints | Approved dedicated and private models | Customer-approved cloud, private, local, or external models |
| Private models | By configuration | Supported | Supported |
| Local inference | Constrained by managed boundary | Optional architecture | Native deployment option |
| Air-gapped deployment | Not in standard Managed | Specialized architecture | Supported architecture |
| Enterprise integrations | Managed connectivity | Dedicated private connectivity | Customer-controlled connectivity |
| Core governanceThe same Work, controls, evidence, and audit history in every deployment | |||
| Conversation + durable Work | Included | Included | Included |
| Work Definitions + Catalog | Included | Included | Included |
| Cognitive Contracts | Included | Included | Included |
| Evidence controls + model boundaries | Included | Included | Included |
| Cognitive Governors | Included | Included | Included |
| Authorized tools + actions | Included | Included | Included |
| Settlement + audit history | Included | Included | Included |
| Commercial | |||
| Commercial model | Platform subscription + consumption | Annual committed deployment + capacity / consumption | Software license + support + deployment services |
| Implementation | Configure & connect | Design & provision | Architect, deploy & operate |
| Best fit | Fastest path to governed production | Isolation, residency, private connectivity | Direct infrastructure control and complex topology requirements |
Exact topology, service responsibility, regional and model availability, capacity, support, and commercial terms are established for the deployment being contracted.
Control beyond infrastructure
Infrastructure control is only the beginning.
Private networking, customer-managed keys, restricted egress, local inference, and disconnected operation answer where AI runs and how data moves.
Enterprise AI also needs clear policy for which models, data sources, connectors, and tools may be used; who can approve consequential actions; and what the system records when work is completed.
Infrastructure control protects the environment in which AI operates, while business authorization determines which consequential acts are permitted there. Indwel keeps both forms of control visible without confusing possession of the infrastructure with authority over the Work.
Indwel architectureThe operating boundary changes; the authority chain does not.
Tenant admission governs entry into the same Work architecture, while security and provider controls protect the inference venue independently of where the deployment is operated.
Enterprise operating entry
Enterprise Operating FoundationSaaS Control Plane
administers→
Enterprise Operating FoundationTenant and Principal Admission
bounds entry→
Conversation and WorkUnity and Programmatic Surfaces
presents→
Conversation and WorkConversation and Work
Protected model use
Enterprise Operating FoundationSecurity, Privacy, and Provider Egress
protects→
Cognitive MachineryGoverned Inference Boundary
Access controls
Available does not mean authorized.
A model, data source, connector, or tool can exist inside the deployment and still be inappropriate for a particular task. Indwel narrows access through three familiar enterprise layers: technical availability, enterprise policy, then Work-specific authorization.
AVAILABLETechnically accessible in this deployment.
APPROVEDAllowed by enterprise policy and operating boundary.
Use the right model inside the right boundary.
One workload may use an approved frontier model while another requires a private or local model because of data handling, jurisdiction, latency, or operating policy.
A deployment determines the technical options available, enterprise policy narrows those options to what the institution approves, and the governing Work establishes which of the approved capabilities may be used for the particular undertaking.
Degraded operation
Fallback should preserve policy.
Even a carefully designed environment must contend with regional outages, model timeouts, expired connector credentials, stale source systems, and external services that return an ambiguous result. Resilience therefore has to account for more than whether another endpoint is reachable.
Those failures should not silently relax model, data, network, or tool policy. If an approved alternative is authorized for the Work, Indwel may use it. Otherwise the Work can narrow, wait, ask for input, preserve progress, expose the dependency, or stop safely.
Crossing an unapproved boundary is not resilience. A fallback model, source, connector, or region still has to satisfy the security, data, policy, and business conditions that matter to the Work.
Operational proof
Know what ran under which controls.
The running environment never stands still: models are upgraded, keys rotated, connectors changed, software patched, and infrastructure moved as policies and business requirements evolve. Organizations need a record of the controls that actually applied to each consequential action, not merely a description of the environment they intended to operate.
Operational access and business approval remain separate. An infrastructure administrator may restart a runtime without gaining permission to approve a payment. An Indwel operator may maintain a Managed environment without becoming an approver of the customer’s business decisions.
After a consequential action, the organization should be able to reconstruct the environment, policy, approvals, and observed outcome that mattered.
Applied controls
Work Definition, evidence, contract, policies, approvals, and applicable constraints.
Observed outcome
Actions, results, failures, interventions, reconciliation, and Settlement.
Recover the Work, not just the data.
Backups, replicas, snapshots, queues, and disaster-recovery environments extend business state beyond the primary runtime. Residency and recovery plans should account for those copies—and for the governing state of unfinished Work.
Recovery should preserve what Work existed, which evidence and policies applied, what had been approved, what remained incomplete, which actions had been attempted, and what still remained before Settlement.
Portability
Move without rebuilding the Work.
Cloud providers, model providers, regulations, and operating requirements change. Work that begins in a Managed environment may later require dedicated infrastructure, private inference, customer-controlled operation, or an air-gapped boundary.
The organization should not have to reinvent the undertaking every time custody moves. Work identity, evidence, approvals, action history, and completion state should move with it.
Portability should preserve business state and controls—not merely data or compute.
Plan for exit from the start.
A portable deployment lets the organization change model providers, withdraw a capability, bring infrastructure under greater internal control, delegate more operation to Indwel, separate a business unit, absorb another, or end an operating relationship.
Not every transition is instant. Some require migration, reconciliation, controlled interruption, or deliberate treatment of Work already in flight. But changing custody should not discard the business state accumulated under the old arrangement.
Commercial path
Choose how Indwel runs.
Deployment begins with the operating boundary you need—not an artificial feature tier. The commercial engagement follows the infrastructure custody, isolation, capacity, support, and operating responsibility your organization requires.
Managed
Indwel handles provisioning, updates, monitoring, and capacity while your institution directs its Work, policies, connected systems, and approvals.
Platform subscription · consumption · enterprise supportLearn about Indwel Cloud →Dedicated
Indwel operates a dedicated environment shaped around your isolation, networking, jurisdiction, encryption, integration, and capacity requirements.
Annual commitment · dedicated environment · capacity / consumptionDesign a Dedicated environment →Licensed
Run Indwel in your cloud or private infrastructure, including local and air-gapped deployments where contracted.
Software license · support · deployment servicesDiscuss licensing →Move the boundary without losing the Work.
Change infrastructure, model venue, operating responsibility, or custody while preserving the Work’s evidence, controls, open obligations, action history, and Settlement state.