Database Landscape Overview
Database Landscape Overview
Section titled “Database Landscape Overview”This document summarizes all database engines, instances, and storage isolation policies in effect across the Salitech infrastructure.
Database Registry
Section titled “Database Registry”| Database ID | Engine & Version | Host / Stack | Scope | Status | Access Policy |
|---|---|---|---|---|---|
db-umami-postgres |
PostgreSQL 15 | production-01 (/opt/umami) |
Dedicated (Umami) | Active | Isolated to Umami container stack only. |
db-salitech-postgres |
PostgreSQL (TBD) | production-01 |
Platform Storage | Planned | Salitech API only (Service/Repo layer). No agent direct access. |
db-nocodb-postgres |
PostgreSQL | production-01 |
Legacy NocoDB | Removed | Removed on 2026-09-11. |
db-mongodb |
MongoDB | production-01 |
Non-Existent | Not Installed | Not installed on host. |
Core Database Rules
Section titled “Core Database Rules”- Service-Dedicated Databases: Databases bundled within a specific service stack (e.g., Umami’s PostgreSQL 15) must not be repurposed for other applications.
- Platform Access Abstraction: Autonomous agents interact only with the Salitech API and never receive direct SQL connection strings.
- Backup Isolation: Each database instance must have an independent, automated dump and backup lifecycle.