Skip to main content

Installation

This guide covers detailed installation instructions for Aurora, including development setup, production deployment with Docker Compose, and Kubernetes deployment.
For a quick local setup, see the Quickstart guide. This page provides more detailed instructions for different deployment scenarios.

Prerequisites

Required

  • Docker 20.10+ and Docker Compose 2.0+
  • Git for cloning the repository
  • LLM API Key from OpenRouter, OpenAI, Anthropic, or Google AI

Optional

  • Kubernetes 1.25+ with Helm 3.0+ (for K8s deployment)
  • Docker Buildx (for multi-platform builds)
  • Cloud Provider Accounts (AWS, GCP, Azure - only if using cloud connectors)

System Requirements

  • RAM: Minimum 4GB, recommended 8GB+
  • CPU: 2+ cores recommended
  • Disk: 10GB+ free space for Docker volumes
  • Ports: 3000, 5080, 5006, 5432, 6379, 8080, 8200 must be available

Installation Methods

Prebuilt Images

Fastest method - pull images from GHCR

Build from Source

For development or custom modifications

Kubernetes

Production deployment with Helm
Use prebuilt images from GitHub Container Registry for the fastest setup.
1

Clone and initialize

2

Configure environment

Edit .env to add your LLM API key:
Required configuration:
.env
3

Start with prebuilt images

To use a specific version:
Available versions: github.com/orgs/Arvo-AI/packages
4

Configure Vault token

Retrieve and set the Vault root token:
Add to .env:
.env
Restart services:
Prebuilt images are production-ready and tested. They’re rebuilt on every commit to the main branch.

Method 2: Build from Source

Build Aurora locally for development or to test custom modifications.

Development vs Production

Development mode mounts source directories for hot reload. Production mode uses optimized builds without source mounts.

Method 3: Kubernetes Deployment

Deploy Aurora to Kubernetes using Helm charts.
1

Prepare configuration

Copy the values template:
Edit values.generated.yaml to configure:
values.generated.yaml
2

Build and push images

Build images for your registry:
This:
  • Reads configuration from values.generated.yaml
  • Builds images for linux/amd64
  • Tags with current git SHA
  • Pushes to your configured registry
  • Updates values.generated.yaml with the new tag
3

Deploy with Helm

Or manually:
4

Initialize Vault (first time only)

After deployment, initialize Vault:
Save the unseal keys and root token securely. Update the Kubernetes secret:
Restart Aurora services to pick up the token:
5

Verify deployment

Kubernetes deployment requires additional configuration for:
  • Ingress controllers (nginx, Traefik, etc.)
  • TLS certificates (cert-manager recommended)
  • Persistent volume provisioning
  • Network policies
See the Kubernetes Deployment guide for details.

Environment Configuration

Core Variables

Required environment variables in .env:
.env
The make init command automatically generates secure values for POSTGRES_PASSWORD, FLASK_SECRET_KEY, AUTH_SECRET, and SEARXNG_SECRET.

Optional Integrations

Add these variables to enable optional features:
.env
See the Environment Variables guide for all available options.

Makefile Commands

Aurora provides a comprehensive Makefile for common operations:

Development

Production

Kubernetes

The make down command works for both development and production deployments.

Verify Installation

Check Services

Verify all services are running:
You should see containers for:
  • aurora-server (Flask API)
  • aurora_celery-worker-1 (Background tasks)
  • aurora_celery-beat-1 (Scheduled tasks)
  • aurora_chatbot-1 (WebSocket server)
  • aurora_frontend-1 (Next.js UI)
  • aurora-postgres (Database)
  • weaviate (Vector database)
  • redis (Message queue)
  • aurora-vault (Secrets management)
  • aurora-seaweedfs-* (Object storage)
  • aurora-memgraph (Graph database)

Test Endpoints

View Logs

Troubleshooting

Clear Docker cache and rebuild:
Check which ports are in use:
Stop conflicting services or modify ports in .env:
.env
Check Docker resource limits:
Increase Docker memory allocation to at least 4GB (8GB recommended).
Reset the database:
Weaviate requires more memory. Check logs:
Increase Docker memory or disable vector search temporarily.

Next Steps

Configuration

Configure LLM providers and adjust agent settings

Cloud Connectors

Add AWS, GCP, Azure integrations

Production Deployment

Deploy Aurora to production with best practices

Architecture

Understand Aurora’s architecture and components

Upgrading

To upgrade to a newer version:
Always backup your data before upgrading:

Uninstalling

To completely remove Aurora: