Dedicated instances

A dedicated instance is a complete nyxory — console, operator, build runners, registry, optional AI gateway and run observability — running for one customer in one environment. Nothing is shared with other customers. Instances run today on STACKIT and AWS; Azure is being brought up; a bare-metal or on-premises data centre is a project we scope with you.

What it needs

• A Kubernetes cluster (managed or k3s) with a wildcard DNS entry and TLS for the instance domain.
• A secrets manager of the cloud (the instance reads platform secrets through the External Secrets Operator; nothing is sealed into git).
• Object storage for backups and exports.
• A container registry per instance (cr.<your-domain>), seeded from nyxory’s release registry.

The bootstrap is infrastructure-as-code (OpenTofu) plus one Helm chart that renders every Argo application of the instance. Human decisions — domain, sizes, feature flags — live in one values file per instance.

Who can access what

Your teams use the console and the MCP exactly as on the shared platform. nyxory’s operations access is administrative access to the instance from the EEA and Switzerland only, with multi-factor authentication, as set out in the DPA. Every MCP call lands in the instance’s audit log, with the reason the agent gave for it.

How upgrades land

Every release image (console, operator, agent, build runners, gateway) is pinned per instance. An upgrade is a deliberate change of that pin in your instance’s values, applied by Argo CD; the version is visible in git before it lands.

Optional building blocks

• AI gateway: a model egress with per-application budgets; apps call it with their pod identity, no key in the code.
• Argus: observability for agent runs (the console’s Argus page).
• Operations agent: the agent that runs day-2 operations; available on dedicated instances.

When you leave

Manifests are exportable, volumes can be exported, and the DPA sets the return and deletion terms. The instance is yours to switch off.