Datab Runtime

What runs on a Datab Node

A Datab Node is not a single binary — it's a supervised set of services running under snapd. This page is the reference for what each service does, what port it binds, and how they depend on each other.

Service inventory

Service	Port	Role
containerd	—	Container daemon.
dockerd	—	Docker on snap-local socket.
postgres	5432	PostgreSQL 16 in container.
flyway	—	Oneshot — runs migrations + exits.
micronaut-backend	8080	DatabStudio Finance backend.
atlas-core	8090	Identity + trust + DDSN.
model-runtime	configurable	Optional, pluggable local inference runtime for Orula.
orula	11444	Intelligence agent (RC1 Preview).
gu	11445	Security agent (RC1 Preview).
restore-watcher	—	Operator-triggered restore daemon.
compositor	—	Optional kiosk display.

Dependency chain

containerd → dockerd → postgres → flyway → micronaut-backend
                                          → atlas-core
                        model-runtime → orula
                                       gu

All loopback by default

Layer-2 services (Atlas, Orula, Gu, and any enabled model runtime) bind 127.0.0.1. Only the backend (port 8080) accepts LAN connections; everything institution-facing flows through it.

Detailed boot order and operator commands: see Operator Docs.