Get Started
Configuration
ARIA is configured through environment variables (a .env file locally). Here are the ones you'll actually touch.
Core
| Variable | Default | Description |
|---|---|---|
PORT | 3001 | HTTP listen port (API + dashboard). |
DATABASE_URL | — | Postgres connection string, e.g. postgresql://aria:aria@localhost:5432/aria?schema=public. |
REDIS_HOST / REDIS_PORT | localhost / 6379 | Redis for sessions and the background job queue. |
ACCESS_TOKEN_SECRET / REFRESH_TOKEN_SECRET | — | Secrets for the local API’s tokens — set any strong random strings. |
AWS credentials
ARIA’s judge runs on Amazon Bedrock, so you need AWS credentials with access to a Bedrock model. The local stack mounts your host ~/.aws directoryread-only into the containers, so once your CLI is configured no extra wiring is needed.
- Configure credentials — run
aws configure(writes~/.aws/credentials), oraws sso loginfor an SSO profile. Environment variables (AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY) also work. - Pick a region — set
AWS_REGION/JUDGE_BEDROCK_REGIONto a region where you have Bedrock access (defaulteu-west-2). - Enable model access — in the AWS console, open Bedrock → Model access and enable the Claude models you’ll judge with. Without this, judge calls fail with an access error.
The app starts fine without AWS credentials — you only need them to actually run an evaluation (the judge call).
The judge
The judge runs on Amazon Bedrock by default. Newer models are resolved to the correct cross-region inference profile automatically based on the region.
| Variable | Default | Description |
|---|---|---|
JUDGE_BEDROCK_REGION | eu-west-2 | Region for judge Bedrock calls; overrides BEDROCK_REGION. |
BEDROCK_REGION | us-east-1 | Fallback Bedrock region. |
JUDGE_MODEL_ID | — | Override the judge model, e.g. eu.anthropic.claude-sonnet-4-5-20250929-v1:0. |
JUDGE_MAX_TOKENS | 1200 | Max tokens per judge call. |
JUDGE_TEMPERATURE | 0 | Judge temperature (0 = deterministic). |
JUDGE_SYSTEM_PROMPT | built-in | Override the full judge system prompt. |
ARIA can also run a committee of judges across providers. Supply the keys for the ones you want — OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, or the AZURE_OPENAI_* variables — and configure the committee in Settings.
Agent providers
Each adapter reads its own connection variables. The most common:
| Provider | Variables |
|---|---|
| Amazon Connect | CONNECT_INSTANCE_ID, CONNECT_REGION, CONNECT_CONTACT_FLOW_NAME |
| AWS Lex | LEX_BOT_ID, LEX_BOT_ALIAS_ID, LEX_REGION |
| OpenAPI / custom HTTP | Endpoint configured per run (CLI flags or the dashboard). |
Scenarios & reports
Scenarios are read from the scenarios/ directory by default. In containers they are bind-mounted at /app/state/scenarios and reports are written to /app/state/reports. See Scenarios for the file format.