Skip to content

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.

┌─────────────────────────────────────────────────────────┐
│ Layer 3 — CI/CD build, ship & run the app │
│ CI (GitHub / GitLab / Azure DevOps) → CD (ArgoCD)
├─────────────────────────────────────────────────────────┤
│ Layer 2 — Containerization Kubernetes (EKS / AKS) │ ← cloud-agnostic
│ workloads, Helm/Kustomize, ingress, secrets from here up
├─────────────────────────────────────────────────────────┤
│ Layer 1 — Infrastructure AWS *or* Azure │ ← cloud-specific
│ networking, identity, data, DNS/TLS (IaC) (chosen in the audit)
└─────────────────────────────────────────────────────────┘
Observability (Grafana stack) — spans every layer, end to end

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

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

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

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