Quick Start

Get Aberon running in 60 seconds. No internet required after download.

Prerequisites

  • Docker Engine 24+ and Docker Compose v2
  • 2 GB RAM

Step 1: Download and extract

tar xzf aberon-0.1.0.tar.gz
cd aberon-0.1.0

Step 2: Load Docker images

docker load < aberon-backend.tar.gz
docker load < aberon-frontend.tar.gz
docker load < postgres-16-alpine.tar.gz
docker load < nginx-alpine.tar.gz

Step 3: Configure

nano .env

Set two required values:

POSTGRES_PASSWORD=your-secure-password
JWT_SECRET=at-least-32-random-characters-here

Optional — set admin password (otherwise auto-generated, printed in logs):

DEFAULT_ADMIN_PASSWORD=YourAdminPass123

Step 4: Start

docker compose up -d

Wait ~30 seconds for all services to start, then verify:

docker compose ps

All 4 services should show "healthy":

  • postgres
  • backend
  • frontend
  • gateway

Step 5: Open Dashboard

Open http://<your-server-ip>:3000 in your browser.

Login:

  • Email: admin@aberon.internal (or your DEFAULT_ADMIN_EMAIL)
  • Password: your DEFAULT_ADMIN_PASSWORD (or check logs: docker compose logs backend | grep password)

Step 6: Connect your first agent

Install the Python SDK:

pip install sdk/aberon-*.whl

Create an API key: Dashboard → Settings → API Keys → Create

Then in your Python code:

import aberon

client = aberon.Client(
    endpoint="http://<your-server-ip>:3000",
    api_key="aberon_sk_...",
)

agent = client.register(name="my-agent", framework="langchain")

with agent.trace() as t:
    with t.span("llm_call", kind="llm") as s:
        result = your_agent.run(query)
        s.set_tokens(input=100, output=50)
    t.set_cost(0.02)

Go back to Dashboard → Traces. Your trace appears in real-time.

See the full SDK reference for all available methods, decorators, and multi-agent trace linking.

Demo Mode

Want to see Aberon pre-populated with realistic data?

Before first start, add to .env:

SEED_DEMO=true

This creates 3 agents, ~60 traces (with errors, slow requests, guardrail blocks), 3 policies, approvals, and a hash-chain audit log.

What's next?