Botkeep
← Hosting use cases

Choose a home for your data.

Relational records or a cache: choose MariaDB, MySQL, PostgreSQL or Redis, with shared resources and a dedicated server slot.

01

Match the engine to the model

PostgreSQL, MySQL and MariaDB support relational data and SQL. MariaDB is a separate engine compatible with many MySQL clients, not an identical replacement: check SQL features and migrate data explicitly. Redis is useful for caches; durability depends on persistence. MongoDB is not currently enabled.

02

A connection string is a secret

The Database page provides the assigned host, port, application credentials and CA certificate. Use TLS with certificate and hostname verification. Keep credentials in server-side environment secrets, never in browser code or Git. URI options depend on your client.

03

Budget for more than records

Indexes, transaction logs, temporary files and backups may consume storage. Connection pools and caches consume RAM. Start with bounded connections, observe actual usage and leave room for maintenance operations.

04

Test recovery, not just creation

Stop the database before making a file backup in the panel. Restore replaces the current files, including credentials, with those in the backup. Keep an independent copy of important data and test recovery before you need it. Changing engines or major versions requires a migration.

Every database occupies one server slot, with no separate database quota. RAM, CPU and storage are shared with your other servers. Choose resources within the available budget: very small allocations may prevent the engine from starting.

Try a concrete starting point

APIs

Express API

A small JSON API with health checks, input validation and graceful shutdown.

6 files · instructions includedExplore project
APIs

FastAPI

A typed Python API with validated responses, a health route and OpenAPI documentation.

6 files · instructions includedExplore project

Enabled profiles can be deployed from the panel. Configure addresses and HTTPS in Domains; a custom domain requires DNS verification. No performance or availability guarantee is implied.