Secure by default • Production ready

Ops & Security

Deploy, configure, and harden the Aetherra Hub and Kernel for production.

Quick start (prod-ready)

  1. Run the Hub behind a reverse proxy with TLS (e.g., NGINX, Traefik).
  2. Set strict CORS and Private Network Access headers.
  3. Enable control-plane APIs only when needed and guard with tokens.
  4. Expose /metrics to your monitoring stack; add alerts for queues and uptime.

CORS & Private Network Access (PNA)

The Hub sets CORS and PNA headers via an after_request hook. Configure allow-lists using environment variables:

Symptoms and fixes:

Authentication & control plane

Control endpoints are opt-in and token-guarded:

Optional AI/Agents APIs have corresponding toggles and tokens:

Reverse proxy example (NGINX)

server {
  listen 443 ssl;
  server_name hub.example.com;

  # TLS config...

  location / {
    proxy_pass http://127.0.0.1:3001;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto https;
    # Preserve CORS/PNA headers from the Hub
    proxy_pass_header Access-Control-Allow-Origin;
    proxy_pass_header Access-Control-Allow-Headers;
    proxy_pass_header Access-Control-Allow-Methods;
    proxy_pass_header Access-Control-Allow-Credentials;
    proxy_pass_header Access-Control-Allow-Private-Network;
  }
}

Endpoints to expose

Hardening checklist

Troubleshooting