UNDER THE SURFACE
Platform architecture
Clear responsibilities, from cloud foundation to customer experience.
See it in the workspaceTHE OPENCENTRIC OPERATING MODEL
One platform. Three clear responsibilities.
Your workspace connects to a versioned foundation and an internal operations layer. Customer environments remain separate.
ATLAS
Definitions that can be reviewed.
Versioned module contracts describe capabilities, dependencies, and configuration. The 14-layer catalog provides a shared language for the plan.
- Versioned module definitions
- Dependencies and baseline scope
- Plan validation
Target operating model. Live cloud execution and monitoring are not enabled in this preview.
HUB AND SPOKE, WITH CLEAR BOUNDARIES
Central coordination. Customer-owned environments.
The control plane coordinates approved work. Each customer environment retains its own account boundary and delegated access scope.
Request & review
Customer intent, Atlas plan, cost estimate, approval.
Orchestrate
Versioned modules, scoped execution, change evidence.
Customer cloud
Applications and data in customer-owned accounts.
Target architecture. Provisioning and Terramate orchestration are not active in this preview.
ATLAS / VERSION 0.1.0
The 14 platform layers
Baseline modules establish the foundation. Optional modules extend it as requirements become clear.
01Deployment fabricBaseline
Customer-owned account, approved region, and environment boundaries.
Dependencies: None
Contract definition only. Not an active deployed service.02Compute, storage & networkBaseline
Private networking, capacity, backup targets, and resource ownership.
Dependencies: Deployment fabric
Contract definition only. Not an active deployed service.03Container runtimeBaseline
Image digest, health checks, resource limits, scaling, and recovery.
Dependencies: Compute, storage & network, Identity & access
Contract definition only. Not an active deployed service.04Delivery & supply chainBaseline
Versioned changes, reviewed plans, signed artifacts, and rollback.
Dependencies: Deployment fabric
Contract definition only. Not an active deployed service.05Security & evidenceBaseline
Control applicability, vulnerability findings, and evidence owners.
Dependencies: Identity & access, Delivery & supply chain
Contract definition only. Not an active deployed service.06Platform servicesOptional
Approved databases, storage, messaging, and application services.
Dependencies: Container runtime
Contract definition only. Not an active deployed service.07AI & intelligent systemsOptional
Approved models, tool permissions, usage limits, and evaluation.
Dependencies: Container runtime, Security & evidence
Contract definition only. Not an active deployed service.08Domains & trafficOptional
Domain ownership, certificates, ingress, CDN, and load balancing.
Dependencies: Compute, storage & network
Contract definition only. Not an active deployed service.09Data pipelines & streamingOptional
Batch and streaming contracts, freshness, replay, and recovery.
Dependencies: Platform services, Data modeling
Contract definition only. Not an active deployed service.10Data modelingOptional
Tenant keys, schema evolution, ownership, and migration reviews.
Dependencies: Identity & access
Contract definition only. Not an active deployed service.11Integrations & business servicesOptional
Scoped connectors, idempotency, retries, and controlled write-back.
Dependencies: Identity & access, Security & evidence
Contract definition only. Not an active deployed service.12Data governanceOptional
Sources of truth, retention, classification, lineage, and access.
Dependencies: Data modeling
Contract definition only. Not an active deployed service.13Identity & accessBaseline
Federated identity, tenant authorization, delegated roles, and revocation.
Dependencies: Deployment fabric
Contract definition only. Not an active deployed service.14Tenant administrationBaseline
Onboarding, membership, entitlements, consent, and offboarding.
Dependencies: Identity & access
Contract definition only. Not an active deployed service.