/ Docs / Deployment

Deployment

Quatrion is designed around configurable deployment targets. The public product posture is local-first and cloud-agnostic, with operator-selected boundaries for CAD, storage, identity, secrets, job state, and LLM providers.

Page summary

Deployment patterns for local workstation, on-prem Kubernetes, private cloud, managed Kubernetes, and air-gapped review.

Deployment targets

Local workstation

Workbench-centered pilot flow where raw CAD can remain local and services point to approved local or private endpoints.

On-prem Kubernetes

Kubernetes deployment inside an enterprise-controlled environment with local object storage and operator-managed identity.

Private cloud

Operator-controlled cloud environment using configured storage, registry, gateway, and identity services.

AWS EKS

Managed Kubernetes target with operator-supplied registry, secrets, object storage, identity, and LLM-provider configuration.

GCP GKE

Managed Kubernetes target using the same product contracts and provider-neutral service manifests.

Azure AKS

Managed Kubernetes target with configurable identity, secrets, object storage, and gateway settings.

Air-gapped

Discussed on request for qualified teams; exact topology depends on model, storage, update, and support constraints.

Deployment boundaries

Raw CAD locality

Raw CAD can stay inside the configured local, on-prem, or private-cloud boundary.

Object storage boundary

Artifacts use object/file references. The backing store is operator-configurable.

Secrets handling

Secrets are expected to come from Kubernetes Secrets, an external secret backend, or workstation-local secure storage as appropriate.

Identity

Identity is deployment-specific and typically integrated through OIDC-compatible or gateway-level controls.

Job state

Runs and jobs record state needed for evidence, replay, and operational review.

LLM provider boundary

Model provider and runtime are configurable. Quatrion does not require a managed agent runtime lock-in.

Configurable targets

Gateway URLs, service routes, storage, registry, identity, secrets, and model-provider settings are deployment configuration, not hardcoded product assumptions.

Deployment targets

Deployment boundaries

Bring one assembly. Run one agent. See the evidence.