Skip to content

Databases

Overview

Databases are first-class resources in Wodby. They give you a shared place to manage:

Database ownership and sharing depend on how the database is deployed:

  • A container-based database belongs to an app. It always uses the owning app's owner and project access list. To change who can use or modify it, open the app's Sharing page.
  • A managed database is independent of an app. Use the database's Sharing page to change its owner or make it available to additional projects with either Read/Use or Modify/Delete access.

A database also has an environment. For container-based databases created from an app, the environment usually matches the app instance environment.

The database details page also shows the current connection metadata and can reveal the current master password on demand.

Deployment types

Wodby supports two main ways to run a database server:

Type Best when How it works
Container-based The database belongs to one app stack The database runs as part of your app deployment with attached persistent storage
Managed You want an external provider-managed database Wodby connects to a cloud-managed database workflow through integrations

1. Container-based

The database runs as part of your application stack in a container with attached persistent storage.

Add one of the database services to your stack and choose storage size in stack configuration or during app creation.

Its ownership and project access stay synchronized with the owning app. Moving the app to another owner project or changing the app's project access updates the database automatically; the database cannot be shared separately.

2. Managed

The database server is deployed by a third-party cloud provider and connected through the required external service and cloud integration.

Supported managed database kinds include:

  • MySQL
  • MariaDB
  • PostgreSQL