Skip to main content
Deployment Model

Choose a Deployment Model with Boundaries Made Explicit

Batoi-managed, partner-managed, and customer-managed patterns differ in runtime, data, network, credential, update, evidence, and support ownership. Portability and control continuity are verified for each target, not assumed.

Explore Platform Architecture Explore Governance and Trust
Batoi control-plane and runtime deployment boundaries

Separation of Core Control and Runtime Execution

Batoi Platform uses a layered model that decouples governance and coordination from runtime execution.

Connected Control Plane
  • Identity and access management
  • Policy enforcement and approvals
  • Project and workspace metadata
  • Audit trails and activity logs
  • Configuration and orchestration
  • Evidence return and operational ownership
Execution Plane (Deployment-Flexible)
  • Application runtimes coordinated through the Build capability
  • Integration workloads
  • Analytics processing
  • Storage and compute
  • Approved public ingress and outbound boundaries

A target is ready only when identity, policy, Guard, ingress, data, credential, evidence, update, rollback, monitoring, and support responsibilities are connected and verified.

What Deployment-Flexible Means in Practice

The Build capability does not lock applications and customer deployments into one hosting model.

Same Product Logic

Portable application logic can be reused when target services, data stores, integrations, credentials, and infrastructure contracts are compatible.

Same Decision Contracts, Verified Enforcement

Targets may use the same identity, policy, Guard, and evidence contracts, but connectivity and enforcement behavior must be verified in every environment.

Same Portability Goal

Organizations can optimize for compliance, residency, cost, locality, private operating requirements, or partner delivery models without rebuilding the product foundation.

Deployment Choices

Choose the operating model that fits your product, compliance posture, and infrastructure ownership preference.

1
Batoi-Managed Products

Batoi operates the platform and the delivered product environment in a managed model for organizations seeking rapid onboarding and reduced operating overhead.

Best suited for
  • Managed SaaS adoption
  • Structured rollout of Batoi-delivered workloads
  • Teams that do not want infrastructure ownership
  • Research, pilot, and learning environments

Also supports private Batoi-managed deployments for country-wide, state-wide, community-scale, and large-enterprise environments when a dedicated operating boundary is required.

Explore Batoi-Managed Cloud
2
Partner-Operated Deployments

Approved partners can deploy and operate Build-coordinated applications and customer environments on agreed infrastructure while Batoi Platform provides governance, orchestration, and visibility.

Best suited for
  • Regional compliance and locality needs
  • Managed service delivery by partners
  • Industry-specific product deployments
  • Public sector and ecosystem-led rollouts

Ideal when local operating presence or partner-led service delivery matters, while governance remains anchored in the platform.

3
Customer-Operated Deployments

Organizations can deploy Build-coordinated applications and workloads in their own public or private cloud environments while using Batoi Platform as the governing layer.

Best suited for
  • Regulated industries
  • Data residency requirements
  • Existing cloud investments
  • Enterprise security controls

Best when the organization wants full infrastructure ownership while keeping governance, auditability, and security controls consistent.

Designed for Portability

Batoi Platform avoids infrastructure lock-in.

Portability principles

Exportable configurations

Transparent policies

Standard interfaces and APIs

Clear separation of data and control

This allows organizations to:
Shift deployments over time
Respond to regulatory changes
Reduce long-term risk

Partner-Led Delivery

Partners play a central role in operating Build-created deployments while governance remains anchored in the platform.

Partners can:
  • Provision environments
  • Manage infrastructure
  • Provide localized support
  • Operate customer deployments under agreed controls
The operating agreement defines:
  • Policy and security enforcement ownership
  • Monitoring and evidence visibility
  • Credential, network, and data boundaries
  • Updates, rollback, incident response, and support
Explore Partners

For Enterprise Architects

Control without constraint.

For Security and Compliance Teams

Governance independent of infrastructure.

For Partners

Deliver services without reinventing the platform.

Frequently asked questions

Supported customer-managed deployment patterns are available when control-plane connectivity, runtime ownership, data location, ingress, credentials, evidence return, updates, and support responsibilities are explicitly agreed.

Deployment changes the technical and operational boundary. The same decision and evidence contracts can be used, but their enforcement, connectivity, data handling, updates, and support must be verified for each target.

Build can prepare supported applications for multiple deployment targets. Portability depends on the application, infrastructure, data, integrations, credentials, policy dependencies, and target readiness; it is verified rather than assumed.