Using databases with KibanOS
KibanOS runs database services on your own server. They are currently designed for connections between services in the same environment.
Projects and environments
Every installed database belongs to an environment. KibanOS currently allows one installation of each catalog service per environment, rather than multiple named instances of the same service.
Project
├── Development → PostgreSQL
├── Staging → PostgreSQL
└── Production → PostgreSQLA database server can contain multiple logical databases when its engine supports them. KibanOS does not currently provide a dedicated interface for managing those databases or their users.
Internal connections
Services in the same environment share the runtime network kiban-env-{environmentId}. Each environment has a separate network. Use the Compose service name as the hostname and the database's internal port.
| Engine | Internal address |
|---|---|
| PostgreSQL | postgresql:5432 |
| MySQL | mysql:3306 |
| MariaDB | mariadb:3306 |
| MongoDB | mongodb:27017 |
| Redis | redis:6379 |
| Dragonfly | dragonfly:6379 |
| Valkey | valkey:6379 |
| TimescaleDB | timescaledb:5432 |
| ClickHouse (native protocol) | clickhouse:9000 |
| Neo4j | neo4j:7687 |
| Cassandra | cassandra:9042 |
| Memcached | memcached:11211 |
| QuestDB (PostgreSQL wire protocol) | questdb:8812 |
For example, a service in the same environment can connect with:
postgres://USERNAME:PASSWORD@postgresql:5432/DATABASE
mysql://USERNAME:PASSWORD@mysql:3306/DATABASEThe consuming service must support database connection configuration. Installing two services in the same environment does not connect them automatically or replace a database bundled with an application.
localhost. Inside a service, it refers to that service's own container—not another database service or the server. Internal hostnames cannot be resolved from your computer, another environment, or an application hosted elsewhere.Connection metadata
The service's metadata.json declares protocols, internal services and ports, plus references to configuration fields containing credentials. KibanOS uses this metadata to generate connection details for non-web access points in the databases category.
Generated connection strings are generic and may need engine-specific options. For example, MongoDB clients may require an authentication database, while other engines may use API tokens or a different URI format.
Ports and web access
Database catalog templates use Compose expose instead of publishing host ports with ports. An exposed port is available inside the runtime network, but it is not published on the server and is not a firewall rule.
Web interfaces and HTTP APIs are separate. When declared as web access points, KibanOS can route them through its reverse proxy. A routed interface is not automatically private or authenticated; always review the database service's own security settings.
Configuration and credentials
Enter secure credentials during installation. Catalog defaults are not unique secrets and should be replaced before the database is installed. Automatic credential generation is not currently available.
Storage and health
Persistent database engines use named data volumes. Redeploying a service retains those volumes, while deleting the service removes them through the uninstall flow. Memcached is an in-memory cache and has no data volume.
Volume persistence is not a database backup. KibanOS does not currently provide platform-managed database backups, scheduling, or restore. Health checks report engine availability; they do not confirm application integration, permissions, or backup recoverability.
Related tools
Databasus, NocoDB, pgweb, and Redis Commander are database-related tools rather than database engines. Installing one of these tools does not enable platform-managed backups or external database access.
Planned improvements
Future database work includes:
- External access controls and external connection strings.
- Public host and port configuration, including database-protocol TLS.
- Automatic credential generation and credential rotation.
- Platform-managed backups, scheduling, and restore.
- More complete engine-specific connection strings.
Until external access is implemented, an application hosted on another server or platform cannot use KibanOS internal database hostnames directly.