Skip to main content
Lerian SILOC is Lerian’s native messaging integration for SILOC, the card-domain deferred-net settlement system operated by Núclea. The variables below are set at deploy time and require a service restart to take effect. 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. The variables documented here are the current verified configuration surface; expect it to grow as the rail matures (for example, a systemplane runtime-configuration plane is planned but not yet exposed). Treat the service’s own environment reference as the source of truth for a given release.
In the tables below, Required marks a variable that must be set (globally, or under the condition named). means no default.

Runtime and server

Authentication

Lerian SILOC authorizes protected routes through Access Manager, and is default-closed: authentication is on unless explicitly disabled.

PostgreSQL

The replica falls back to the primary host when DB_REPLICA_HOST is unset (single-node default).

Redis

SILOC settlement connectivity

Lerian SILOC maintains a single IBM MQ connection to the Núclea SILOC settlement queue manager. When any of these variables is set, the whole connection descriptor is validated fail-closed at startup.

Certificates

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; dependency health is reported through /readyz. See Health and readiness for the probe contract.