Skip to main content
Lerian SILOC is Lerian’s native messaging integration for SILOC, the deferred-net settlement system that Núclea operates for boleto and card flows. You set these variables at deploy time. A change takes effect only after you restart the service. For the knobs that behave the same across every Lerian Go service — deployment posture, telemetry, and datastore conventions — see BYOC configuration essentials.
Lerian SILOC is an early-stage service. This page documents the current verified configuration surface. Expect it to grow as the rail matures. For example, Lerian plans a systemplane runtime-configuration plane but does not yet expose it. Treat the service’s own environment reference as the source of truth for a given release.
In the tables below, Required marks a variable you must set, globally or under the stated condition. means no default.

Runtime and server

Authentication

Lerian SILOC authorizes protected routes through Access Manager. It runs default-closed: authentication stays on unless you disable it.

PostgreSQL

The replica falls back to the primary host when you leave DB_REPLICA_HOST empty (single-node default).

Redis

SILOC settlement connectivity

Lerian SILOC maintains a single IBM MQ connection to the Núclea SILOC settlement queue manager. Setting MQ_HOST, MQ_CHANNEL, MQ_QUEUE_MANAGER, MQ_SEND_QUEUE, or MQ_RECEIVE_QUEUE makes the service validate the whole connection descriptor fail-closed at startup. MQ_PORT, MQ_TLS_ENABLED, and MQ_SSL_KEY_REPOSITORY alone do not activate that validation.

Certificates

Trust and custody

Observability

Health and readiness

Lerian SILOC exposes GET /health (liveness), GET /readyz (readiness), and GET /version on the main HTTP port. The service boots and serves these probes even before its datastores and settlement connection are reachable. /readyz reports the health of each dependency. See Health and readiness for the probe contract.