Sheet 01 of 01Scale · 1:1Rev · A
Drawing — Deployment

Installed on your ground. Never rented.

Udal ships as one signed bundle onto your own Kubernetes cluster. Same installer for AWS, Azure, on-prem, and fully air-gapped networks.

Legend
▲ signed artefact
■ your infrastructure
○ fail-closed control
→ GitOps flow
   ┌────────────┐   PR + signed digest   ┌────────────┐   manual gate   ┌────────────┐
   │   git ▲    │ ─────────────────────▶ │  argo cd   │ ──────────────▶ │ prod ■     │
   └────────────┘                        └─────┬──────┘                 └─────┬──────┘
                                               │                              │
                                          admission ○                    audit chain
                                               │                              │
                                        ┌──────▼──────────────────────────────▼──────┐
                                        │   your cluster · your data · your ground   │
                                        └────────────────────────────────────────────┘
§ 01 — Spec
01
One
Signed bundle

Images, charts, wheels — one artefact, signed with the release key, verified at install. Same bundle for connected and air-gapped.

02
Any
Kubernetes cluster

EKS, AKS, GKE, OpenShift, Rancher, VMware Tanzu, bare metal. One Helm chart, one operator, one upgrade path.

03
Zero
Outbound calls

The air-gapped install has no phone-home path. Models serve from pre-staged weights. Licences verify offline.

§ 02 — Principle

"Same installer for a live AWS account and an air-gapped data centre. That's the point."

No parallel product for the sensitive customers. No exceptions.

§ 03 — Substrate

Wherever your data already lives.

Target · 01eu-west-2
AWS

EKS + Bedrock, in-region.

One config file, one command. Terraform stands up VPC, EKS, RDS PostgreSQL, IAM/IRSA and KMS. Bedrock in your account, in your region.

Target · 02uksouth
Azure

AKS, in your tenant.

AKS with Azure Database for PostgreSQL and Key Vault CSI. Azure OpenAI stays in-tenant. Same chart, same accredited profile, different substrate.

Target · 03on-prem / gke
Any K8s

GKE, OpenShift, bare metal.

A conformant Kubernetes cluster is enough. The chart carries every component — one install, one upgrade path, bring your own Postgres and IdP.

Target · 04high-side
Air-gapped

Zero outbound, by design.

One signed bundle. Open-weights models on your own GPUs from a pre-staged volume. Offline licence verification. Key-based signing throughout.

§ 04 — Sequence

Boring on purpose.

The paved road from install to upgrade. Nothing surprising — which is the whole point in a regulated environment.

Step 01

Preflight

Sandbox runtime probe. If the cluster can't isolate, install aborts before a single Helm value is written.

Step 02

Fail-closed install

Accredited profile is one switch. Miss a control — the runtime refuses to start and names the exact gap.

Step 03

GitOps promotion

Dev, staging, prod in one repo. A pull request advances a signed image digest. Production has a manual gate.

Step 04

Admission control

Kyverno verifies every Udal image against the release key at admission. Unsigned images are rejected, not audited after.

Step 05

HA execution

Durable workflow backend drives runs. Stateless services scale horizontally. Postgres runs managed multi-AZ.

Step 06

Observability

Prometheus scrapes on every service. OpenTelemetry traces to Jaeger, Splunk or Datadog. Always on — even air-gapped.

The whole platform. One installer.

Install Udal in your environment.

Technical briefing, not a sales deck. A human replies within one working day.

Request access