Skip to main content
This option runs Noxus services as managed containers while leveraging cloud-native managed data services. This architecture provides high availability and automatic scaling with reduced operational overhead.

​
Supported Platforms

Terraform configurations live in the noxus-infra repository.

Google Cloud Run

Available today. Cloud Run, Cloud SQL (PostgreSQL), Memorystore (Redis), and Cloud Storage.

Azure Container Apps

In progress. The target architecture is documented in the repository, but the Terraform is not yet published. For Azure today, use the Kubernetes path on AKS.

​
Infrastructure as Code

The Terraform handles container services, networking, IAM, and managed data services.

​
Deployment Steps

1

Clone the repository

2

Configure your variables

Fill in your project, domain, admin email, platform version, and Auth0 application credentials. There are no default Auth0 values — you must supply your own tenant.
3

Apply

4

Point DNS at the services

The stack outputs frontend_dns, backend_dns, and relay_dns. Create the matching records before the managed certificates can issue.
The platform is split into several independent container services to allow for granular scaling and resource allocation.

​
Practical Notes

Workflow runs and knowledge-base ingestion are long-running and outlive request timeouts. Workers therefore run as always-on instances with a fixed replica count, not scale-to-zero — which removes most of the serverless cost argument for the platform’s largest component.If knowledge-base ingestion is central to your workload, prefer Kubernetes, where dedicated worker pools keep ingestion from affecting agent latency.
The beat service runs scheduled jobs. Pin it to exactly one replica — two schedulers double-enqueue every scheduled run.
You get separate services, not pools with distinct queue subscriptions and independent autoscaling. Per-workspace worker isolation is a Kubernetes-only capability.
Agent responses hold a connection open for minutes. Default request timeouts truncate them mid-response — raise the timeout on the container service’s ingress.
Only enable Noxus Relays if you need webhook/event receiver endpoints for external integrations.
Deploy the sandbox as an additional internal service and point SANDBOX_MANAGER_URL at it. Without it the plugin system is silently disabled — see Agent Sandbox.

​
Configuration Strategy

  • Secrets Management: Inject sensitive credentials (database passwords, API keys) via cloud-native secret bindings (GCP Secret Manager or Azure Key Vault).
  • Environment Variables: Keep non-sensitive configuration in the platform’s environment variables.
  • Service Naming: Maintain consistent names (noxus-frontend, noxus-backend, etc.) across all environments to simplify monitoring and operations.

Environment Configuration

Shared variable model across deployment options.

noxus-infra Repo

Access Terraform modules and deployment scripts.