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.
— 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 leaveDB_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. SettingMQ_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 exposesGET /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.
