Installation

Each Axion service ships as an OCI Helm chart with a self-contained migration runner. The per-service pages below carry the full, partner-facing install, upgrade, and rollback instructions inline — no external README chasing required.

Services

Service	Chart	Workloads
Sense Backend	axion-sense	Sense API, Sense Worker, Vision pods (detections-api, worker, quality-worker, clusterization-worker, matching, Triton, optional Valhalla)
Sense Web	(TBD)	Sense Web (Vite SPA)
Gen Backend	axion-gen	Gen API, Gen Worker (Hangfire + Tippecanoe)
Gen Web	axion-gen-web	Gen Web (Next.js + AI agent)

Common assumptions

Every chart assumes the same baseline:

• Kubernetes v1.27+ with Helm 3.12+.
• OIDC provider (Keycloak, Azure AD, Auth0, …) reachable from the cluster.
• Private container registry that the cluster can pull from. Images are mirrored from europe-west1-docker.pkg.dev/axionx-infra/axion/... — partners pull, retag, and push to their own registry.
• cert-manager only when the chart's TLS issuer (*.certificate.enabled) is turned on. Off by default; assume the partner's ingress controller terminates TLS.
• Migrations are pre-upgrade Helm hooks. The chart blocks the rollout until schema migrations finish; Helm --atomic --wait is the default install flag in every guide.

What differs between services is which stateful dependencies the chart expects to find already provisioned and reachable — see the per-service pages.

Where each dependency comes from

Dependency	Owned by	Used by
PostgreSQL (axion_sense, axion_sense_tasks, axion_sense_permissions, axion_gen)	Platform infra	Sense Backend, Gen Backend, OpenFGA
ClickHouse (axion_sense)	Platform infra	Sense Backend
Apache Kafka	Platform infra	Sense Backend
S3-compatible object storage	Platform infra	Sense Backend, Gen Backend
OpenFGA	Platform infra (deployed separately)	Sense Backend, Gen Backend
Valhalla	Bundled in Sense Backend chart (opt-in) or external	Sense Backend (Vision)
OIDC IdP	Partner-supplied	All four services

The infrastructure pages — Postgres, ClickHouse, Kafka, Object Storage, OpenFGA, Valhalla — describe each dependency's recommended version, sizing, and access patterns.

Install order

1. Platform infrastructure (Postgres, ClickHouse, Kafka, S3, OpenFGA) — partners typically already operate these; if not, see the infrastructure pages for recommended versions and sizing.
2. Sense Backend — creates and migrates axion_sense + axion_sense_tasks, the OpenFGA model, and ClickHouse schema. Other services depend on this state.
3. Sense Web — needs Sense Backend's API URL. Install immediately after the backend so the Sense surface lands as a single unit.
4. Gen Backend — creates and migrates axion_gen. Connects to the same OpenFGA store as Sense.
5. Gen Web — needs Gen Backend's API URL.

Each pair (Sense Backend → Sense Web, Gen Backend → Gen Web) ships together; the two pairs are independent of each other once the platform infrastructure is in place.