Good to know

What to know before you deploy Cloud MariaDB

The Cloud MariaDB stack represents a MariaDB server hosted at a cloud provider rather than in your cluster. Nothing runs in the app environment: the service has no containers or volumes and points to a managed database you select.

Create the managed database first

Before creating the app, add the managed database under Databases using the required cloud integration. Then, while creating the app, pick that database as the server for the service.

One database and user per environment

Wodby declares a single database and a single user for each environment, named after the app and its environment. The user's password is generated once and can be revealed on the service's Tokens tab.

Linked services get connection details

An app service linked to this one gets the host, port, database, user, and password as environment variables. The host is the managed server's address, so read the variables instead of hardcoding it.

No terminal, settings, or backups

Because the service has no container, there is nothing for the web terminal to open. You manage server parameters, storage, and versions on the managed database, and the service has no backups, imports, or actions.

Read the Cloud MariaDB stack guide for setup steps, settings, and limits.

Services

Start with the right services, then make the stack your own

The Cloud MariaDB stack comes with these services already connected. The table shows which ones are enabled by default when you create an app environment and, where services depend on each other, how they are linked.

When you add the stack to your organization, the copy is yours to change. Changes go into a draft that you publish as a new stack revision, and app environments pick them up when they upgrade.

Add services

Add any service from the catalog, such as a cache, a search engine, or a mail relay, and link it to the services that use it.

Remove what you do not need

Leave optional services out when you create an app, disable a service in one app environment, or remove it from the stack for every environment.

Change how services connect

Point a link at another service in the stack or, where the link allows it, at a service of another app or at custom values such as a managed database. Change it for the whole stack or for one app environment.

Stack serviceBase serviceRole
Cloud MariaDB
Cloud MariaDBEnabled by default

Explore the full stack service catalog for configs, settings, actions, cron, volumes, links, backups, and imports attached to each service in this stack. The stack configuration guide covers adding services, removing them, and changing links.

Integrations

Choose managed database integrations for this connection stack

This stack is built to connect your apps through managed database integrations. Keep each reusable connection at stack level and use the same model across environments.

Pick the managed database provider that fits each environment without rebuilding how the app connects.

Explore all integrations for this stack to browse managed database providers supported by this stack.

Git-managed configuration

Keep your stack configuration in Git

Store the application blueprint in a stack.yml template alongside your code. Version service definitions, defaults, settings, and environment behavior while Wodby turns approved source changes into controlled stack revisions.

Version the application blueprint

Review stack configuration through commits and pull requests before it reaches an environment.

Import updates as new revisions

Follow an approved branch or semantic-version tags without changing running app environments in place.

Keep service updates enabled

Control Git template updates and service auto-updates separately, so customized stacks can still receive eligible releases.

Explore Git-backed stacks and see how they work with automatic updates.

Security and maintenance

Stay secure with automatic service updates

Enable service auto-updates at stack level to pick up eligible security patches and maintenance releases. Wodby creates a new stack revision instead of changing running app environments in place, so every update stays visible and reviewable.

Choose which app environments should auto-upgrade and limit production rollouts to a local-time maintenance window. Development and staging can move sooner while production follows your security and maintenance policy.

Explore automatic updates to see how policies, revisions, maintenance windows, and app environment auto-upgrades work.

Environments

Create development, staging, and production environments

Launch development, staging, production, or customer-specific environments from the same Cloud MariaDB stack, then tailor values and configuration to each one.

Start from a consistent baseline

Use the same enabled services and integrations across development, staging, and production.

Customize each environment

Override values, configs, and settings without changing the shared stack definition.

Explore environments for development, staging, and production workflows.

Get started

Create a new Cloud MariaDB database environment

Reuse the same database stack for development, testing, and production environments without rebuilding the service definition each time.

FAQ

Common questions about the Cloud MariaDB stack

What does the Cloud MariaDB stack include?

Connection stack for apps that use a managed MariaDB service instead of running the database inside the application stack. App environments created from this stack inherit the services enabled by default, attached integrations, hosting options, and stack revision history.

How can one stack support multiple apps and environments?

You can reuse the same stack for multiple similar apps and for development, staging, production, and other environment types. The stack defines the shared services and defaults, you can set different values for env types such as dev and prod, and each app environment can still be configured individually.

How do stack updates work?

When an included service gets an update, the stack can be marked as outdated or create a new revision automatically under its update policy. Existing app environments stay on their current revision until you upgrade them manually or enable stack auto-upgrades with a maintenance window.

How do integrations work with this stack?

Use the Integrations section to attach reusable connections created from supported providers. That keeps SMTP relays, backup storage, managed databases, and other external services connected to the stack instead of configuring them separately for every app environment.