Skip to main content
This reference lists the environment variables that configure Matcher, the reconciliation engine. Lerian sets these values when it installs or upgrades Matcher. Use this page to find what a setting does, its default, and what Matcher checks at startup. When a required variable is absent or invalid, Matcher does not start. With ENV_NAME=production, Matcher applies extra checks. The Required column names each one as “Production”. Some variables only set the starting value of a runtime document. Lerian can change those documents on a running Matcher through Systemplane. The runtime documents section lists them.

Application

HTTP server

Authentication

Tenancy

PostgreSQL

Redis

RabbitMQ

Object storage

Matcher writes export files to this S3-compatible storage.

Infrastructure timeouts

Telemetry

Rate limits

Each limit is a maximum number of requests per window. A maximum must be between 1 and 1000000. A window must be between 1 and 86400 seconds.

Idempotency

Outbox

Ingestion

Matching

Exceptions and webhooks

Export and cleanup

Archival

With the archival worker on, the hot retention, batch size, and lookahead must each be at least 1.

Governance

Extraction engine

Connectors

AI features

Each feature has an on switch, an API key, and a model. Document extraction and rule suggestions also need the consent in the ai_gates runtime document. By default, that consent is off.

Event streaming

Runtime documents

Matcher keeps eleven runtime documents in the Systemplane namespace matcher, under /system. The variables below set the starting value of each document. After Lerian writes a document through Systemplane, the stored document wins over its variables. The rate_limit document cannot turn the limits on while RATE_LIMIT_ENABLED is unset or false.