127.0.0.1:8080
DatabStudio backend
Institution, Finance, School, and Health Studio endpoints; CRM integration surfaces.
Developer platform
Build for institutions, on infrastructure they own.
Local APIs, packaged workloads, and operator-controlled deployment. The Datab developer surface is calm and exact: where to install, which API is available, and what version is real.
SDKs and tooling
Pick the surface that matches your stack.
API surfaces
Datab Node, loopback only.
Every service binds to 127.0.0.1 on the node. Partner workloads running on the same node call them directly; off-node access is routed through Atlas HQ federation with consent and signing.
127.0.0.1:8090
Atlas Core
Identity verification, DID/VC, consent, document proof, signing, sync.
127.0.0.1:11434
Ollama
Local LLM runtime invoked by Orula for on-node intelligence.
127.0.0.1:11444
Orula
Approval-gated intelligence: query, report, recommendation, audit.
127.0.0.1:11445
Gu
Protection events, alerts, support sessions, and node health surfaces.
Documentation tracks
Architecture, modules, packaging, agents, security, and operations.
Platform architecture
The product manifest, module boundaries, and platform contracts that describe the Datab stack end-to-end.
Studio module guide
Finance, School, and Health Studio entities, controllers, events, and the CRM audience connector.
Snap packaging
Service ordering, snap-confinement details, Docker socket convention, and the Postgres-role setup step.
Bounded agent design
Policy, approval, audit, and reward integrity rules that constrain Orula and Gu actions.
Security runbooks
Coordinated procedures for unauthorized admin access, database export attempts, node compromise, and channel downgrade.
Operator playbooks
Install, update, recovery, backup, and field-support procedures for the appliance lifecycle.
Build something that runs on the Datab Node.
Partner workloads, integrations, and sector apps. Local APIs, signed packages, and operator-controlled deployment paths.