Skip to Content
Aionis v0.3.2 is the current Runtime baseline for SDK/API hosts, MCP clients, plugins, Substrate-backed recall, and self-managed agent loops.
Developer Platform OperationsConfiguration

Configuration

Aionis configuration is environment-driven.

Common Variables

VariablePurpose
EMBEDDING_PROVIDERSelects the embedding provider.
OPENAI_API_KEYOpenAI-compatible embedding provider key.
MINIMAX_API_KEYMiniMax embedding provider key when EMBEDDING_PROVIDER=minimax.
RECALL_ENGINE_MODESelects recall behavior. Use hybrid when adding Substrate or multiple recall sources.
RECALL_SUBSTRATE_SIDECAR_ENABLEDEnables Substrate as a recall source.
RECALL_SUBSTRATE_PATHPath to the Substrate evidence database.
RECALL_SUBSTRATE_FAIL_OPENControls whether Substrate configuration errors fail loudly or fall back.
MEMORY_AUTH_MODEConfigure host-facing authentication for self-managed deployments.
TENANT_QUOTA_ENABLEDEnables tenant quota controls when your deployment needs them.
AIONIS_AUTHORITY_RECEIPT_HMAC_ACTIVE_KEY_IDActive signing key id for authority-bearing memory receipts in Server production.
AIONIS_AUTHORITY_RECEIPT_HMAC_KEYS_JSONKeyring used to verify current and previous authority receipt signatures.
AIONIS_AUTHORITY_RECEIPT_HMAC_SECRETSingle-key fallback for smaller deployments; the JSON keyring is preferred.

Local-first Assumption

The fastest setup runs on loopback. For shared or remote deployments, put the Runtime behind the service boundary you control and configure auth, tenancy, and quota policy explicitly.

For the product boundary, see Lite Runtime Boundary.

Authority Receipt Signing Keys

Server production deployments must configure authority receipt signing keys. Aionis signs authority-bearing memory receipts with the active key and verifies existing receipts by key_id, so keep previous keys in the keyring until stored receipts no longer need to be accepted.

AIONIS_AUTHORITY_RECEIPT_HMAC_ACTIVE_KEY_ID=authority-2026-07
AIONIS_AUTHORITY_RECEIPT_HMAC_KEYS_JSON={"authority-2026-07":"current-32-byte-or-longer-secret","authority-2026-06":"previous-32-byte-or-longer-secret"}

Generate these secrets outside the repository with a high-entropy source such as openssl rand -base64 48, then store them in your deployment secret manager. The JSON value may map key ids directly to secret strings or to objects with a secret field.

AIONIS_AUTHORITY_RECEIPT_HMAC_SECRET is accepted for single-key deployments, but AIONIS_AUTHORITY_RECEIPT_HMAC_KEYS_JSON is preferred because it supports rotation without invalidating older stored receipts.

Rotation procedure:

  1. Add the new key id and secret to AIONIS_AUTHORITY_RECEIPT_HMAC_KEYS_JSON.
  2. Set AIONIS_AUTHORITY_RECEIPT_HMAC_ACTIVE_KEY_ID to the new key id.
  3. Keep the previous key in the JSON until receipts signed with it are no longer present or no longer need verification.
  4. Remove the retired key only after that retention window has passed.

APP_ENV=prod rejects ephemeral authority receipt keys and rejects active secrets shorter than 32 bytes.

Last updated on
OverviewEmbeddings