Connection stack for apps that use a managed MariaDB service instead of running the database inside the application stack.
Start with this stackWhy teams use this stack
Start with the right services already linked
Use a ready, configurable service baseline.
Keep stack configuration in Git
Version stack.yml and import approved changes as new revisions.
Stay secure with automatic stack maintenance
Control eligible updates and environment maintenance windows.
Reuse one stack across environments
Create development, staging, and production with tailored configuration.
Connect and reuse integrations
Keep connection stacks ready for supported DB providers.
Services
These are the services enabled by default when you create a new instance from the Cloud MariaDB stack.
Stack services can be configured, added or removed for specific instances, and their versions can be changed as your workload evolves.
| Stack service | Base service | Role |
|---|---|---|
| Cloud MariaDB | Enabled 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.
Integrations
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.
Supported managed database providers
Explore all integrations for this stack to browse managed database providers supported by this stack.
Git-managed configuration
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 instances 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
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 instances in place, so every update stays visible and reviewable.
Choose which app instances 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 instance auto-upgrades work.
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
Reuse the same database stack for development, testing, and production environments without rebuilding the service definition each time.
FAQ
Connection stack for apps that use a managed MariaDB service instead of running the database inside the application stack. Instances created from this stack inherit the services enabled by default, attached integrations, hosting options, and stack revision history.
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 instance can still be configured individually.
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 instances stay on their current revision until you upgrade them manually or enable stack auto-upgrades with a maintenance window.
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 instance.