Skip to main content
Lerian SCR is the Lerian-owned rail that consults borrower positions at BACEN. You set these variables at deploy time. A service restart makes them take effect. The system plane holds a second set of knobs an operator changes after deployment. See Operations and System plane. In the tables below, the Default / Required column shows the default value. means no default. A bold qualifier marks a value you must set. A row marked Sensitive. carries credential or key material. Inject it from your secret manager at deploy time, and never commit a value. The strict posture covers a production environment name and the saas deployment mode. Required in production marks a value that the strict posture demands. A missing or insecure value there refuses the boot.

Service and runtime


Lerian SCR exposes /health, /readyz, and /version on the main port. See Health and readiness for the probe contract, and Operations for the readiness checks.

Postgres


Postgres holds the audit trail, the credential metadata, and the outbox. An operator applies the schema before the first start. The service reads the schema and never creates it.

Redis


Redis backs the result cache, the idempotency window, and the inbound rate limit.

Streaming


The outbox dispatcher publishes the consultation events. No variable sets the topic, because the service derives it from the event source. The first five variables belong to Lerian SCR. The rest belong to the streaming library, which applies the broker TLS and the SASL credentials to the dial.

Authentication


BACEN channel


The outbound channel reaches the BACEN consultation web service over HTTPS with HTTP Basic credentials. The service reads the two credential variables only when the secret store kind is the environment.

Secret store


The secret store resolves the BACEN channel credential.

At-rest encryption


The audit trail encrypts the borrower data and indexes it blind. Two independent keys do that work. One key for both would leak the relation between the ciphertext and the index. Outside the strict posture the service falls back to well-known development keys, which must never reach a regulated runtime.

Telemetry and metrics