Skip to main content
Noxus is built with a decoupled, cloud-native architecture that can be deployed across a variety of environments—from single virtual machines to highly available Kubernetes clusters.

Deployment Philosophy

Our infrastructure is designed to give you complete control over your data and compute resources. All deployment scripts, configurations, and automation tools are maintained in our noxus-infra repository. Whether you’re running in a public cloud, a private data center, or a strictly regulated air-gapped environment, Noxus provides the tools to ensure security, scalability, and operational excellence.

Architecture

Understand the core components, traffic flow, and runtime topology of the Noxus platform.

Deployment Options

Choose the right path for your needs: from simple VM setups to enterprise-grade Kubernetes.

Choosing a Deployment Model

Noxus-infra’s choosing-a-deployment guide covers the failure modes of each model in more detail.

What You Need Before Starting

Every deployment model requires the same four things:
1

A domain you control DNS for

The platform serves three hostnames: <domain>, api.<domain>, and relay.<domain>. These must match the FRONTEND_URL, BACKEND_URL, and RELAY_URL variables — the Backend builds absolute URLs from them, so a mismatch produces redirects that dead-end rather than an obvious error.
2

An identity provider

An Auth0 tenant with an application configured for your domain, or an OIDC provider. TLS is mandatory — Auth0 refuses non-HTTPS callbacks.
3

Registry credentials

To pull the platform container images.
4

A platform version

A single version selects every service image. Mixed versions are not supported — the Backend and Workers share a schema and job format.
PostgreSQL must be 15 or newer. The platform’s migrations create the vector, uuid-ossp, and pg_trgm extensions on first boot. On Azure Database for PostgreSQL these must additionally be present in the azure.extensions allowlist, or the Backend fails to start with a permission error.

What Runs in Noxus

The platform consists of several core services that work together to orchestrate and execute your AI workflows. The Backend and Frontend are always required. Relays and the Agent Sandbox are optional — but the sandbox is required for plugins and for isolated Run Code execution, and it is off by default. See Agent Sandbox.

Core Infrastructure Pillars

Configuration

Manage environment variables, secrets, and connections to databases and storage.

Security

Implement robust authentication, SSO, and granular authorization scopes.

Operations

Monitor system health, manage logs, and handle backup and recovery procedures.

Getting Started

If you’re new to deploying Noxus, we recommend starting with our Architecture guide to understand how the system components interact, followed by the Virtual Machine deployment for your first proof-of-concept.

View Architecture

Dive into the technical details of the Noxus platform components.