ZoophostDocs

Deploy a database

Create a managed PostgreSQL, MySQL, MongoDB, Redis or ClickHouse instance from a plan slot and read its connection details.

Managed databases3 min read

Managed databases run on Zoophost infrastructure and are sold as slot packs. One database instance uses one slot.

Engines

PostgreSQL, MySQL, MariaDB, MongoDB, Redis, ClickHouse, Dragonfly and KeyDB. Each is a stock engine on its standard protocol, so existing client tools and drivers work.

Plans

Plan Slots Per database
DB Starter 2 0.5 vCPU, 512 MB RAM
DB Growth 6 1 vCPU, 1 GB RAM
DB Scale 16 2 vCPU, 2 GB RAM

Plans add up: a Starter plus a Growth plan gives eight slots. Every database takes its resources from the plan its slot came from.

Buy a plan on zoophost.com/databases. The console shows the balance under Database plan balance on the Databases page.

Create the database

  1. Console → Databases → Deploy database.
  2. Choose the Engine.
  3. Enter a Name, optional. If you skip it, the name defaults to <engine>-db.
  4. Pick a Plan slot — the card shows free slots and the resources per database.
  5. Confirm the Deployment target, which is assigned by Zoophost.
  6. Choose Deploy — uses 1 slot.

Provisioning takes about a minute. The new database appears in the list with its engine, version, status and port.

The database page

Connection

Field Notes
Internal connection string Reachable from apps running on Zoophost, without leaving the private network
Host, Port, Database, User, Password Individual values for clients that want them separately
External connection string Only when a public endpoint exists; includes the public port

Use the internal string whenever the client is a Zoophost app. It is faster and keeps database traffic off the public internet.

Details

Engine, version, image, SSL mode, status and creation date.

Backups

The backups table lists Status and Created for each backup. Create backup takes one on demand. See Backups and plans.

Actions

Start, Stop, Restart and Create backup are in the header. Restart after changing engine configuration.

There is currently no Delete action in the console. To retire a database, open a support ticket with the database name; the instance is removed and its slot freed.

Names and credentials

  • Names are lowercase and unique within the organization.
  • The password is generated. Use the eye icon to reveal it and the copy control to take it.
  • Credentials do not expire. Rotating them is a support request today; store the current value in your app's environment variables rather than in code.

Sizing advice

  • 512 MB is for development and small services. A production Postgres with normal connection pooling wants at least 1 GB.
  • Redis and KeyDB are memory-bound. Size for the dataset, not the request rate.
  • ClickHouse is disk- and CPU-heavy. Give it a Growth or Scale slot.
  • One database per app is easier to reason about than a shared instance with many schemas, and slots make that affordable.

Next

  • database
  • postgres
  • mysql
  • mongodb
  • redis
  • slot
  • plan

Ready to use this

PostgreSQL, MySQL, MongoDB or Redis on managed infrastructure.

  • Any engine from the same slot pack
  • Deploying from a slot costs nothing extra
See database plans
Still stuck? Open a ticket from Support tickets in the console, or email [email protected]. Include the service name, the exact error and what you already tried.