The Platform
The Platform is what we instantiate for you during the 14-Day Launch. It’s a layered architecture: each layer builds on the one below it, and the boundary between them is deliberate. The lower you go, the more cloud-specific it is; the higher you go, the more portable.
Everything described here is delivered as Infrastructure-as-Code, documentation, and dashboards that you own — see the Keep-It-All Promise.
The layers
Section titled “The layers”
Layer 1 — Infrastructure
Section titled “Layer 1 — Infrastructure”The cloud foundation: networking, identity, data stores, and DNS/TLS, provisioned as code on either AWS or Azure. This is the only cloud-specific layer — the choice is made during the audit. → Infrastructure
Layer 2 — Containerization
Section titled “Layer 2 — Containerization”On top of the infrastructure we run Kubernetes (managed: EKS on AWS, AKS on Azure). This is the cloud-agnostic boundary: from here up, the implementation is the same regardless of which cloud sits underneath. → Containerization
Layer 3 — CI/CD
Section titled “Layer 3 — CI/CD”The path that takes application code from a commit to a running workload: CI builds and verifies, CD (GitOps with ArgoCD) reconciles the desired state onto the cluster — with safe, automated rollbacks. → CI/CD
Observability — across all layers
Section titled “Observability — across all layers”A Grafana stack (metrics, logs, traces, and alerting) spans every layer, feeding the live, shared dashboards that are your transparency window — and the alerts that drive The Operation. → Observability