Datab
What runs on a Datab Node

Datab Runtime

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

ServicePortRole
containerdContainer daemon.
dockerdDocker on snap-local socket.
postgres5432PostgreSQL 16 in container.
flywayOneshot — runs migrations + exits.
micronaut-backend8080DatabStudio Finance backend.
atlas-core8090Identity + trust + DDSN.
ollama11434Local LLM runtime.
orula11444Intelligence agent (RC1 Preview).
gu11445Security agent (RC1 Preview).
restore-watcherOperator-triggered restore daemon.
compositorOptional kiosk display.

Dependency chain

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

All loopback by default

Layer-2 services (Atlas, Orula, Gu, Ollama) 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.