Reusable, versioned stacks for consistent delivery

Application stacks for consistent delivery

A Wodby stack is the blueprint you use to deploy a new app. It defines the app's services, integrations, and configuration once, so you can reuse the same stack across development, staging, and production and keep delivery consistent.

Stacks have revisions, third-party integrations stay inside the stack definition, and each stack has a template that supports a reviewable deployment workflow.

Browse stacksWhy stacks matterStack feature
CatalogBenefitsFAQ

What a stack gives you

Reuse across apps and environments

Keep the same deployment shape across prod, staging, dev, and repeated customer or internal projects.

Third-party integrations in one place

Managed databases, email, networking, storage, and other external services stay with the stack definition.

Versioned upgrades app by app

Service updates mark stacks as outdated, new stack versions are released on upgrade, and apps can adopt them selectively or automatically.

Flexible, reviewable workflow

Keep the stack template aligned with your process and review changes before rollout.

Benefits

Why teams standardize on stacks

The main value is not the number of components in a stack. It is the ability to use one stack to deploy new apps, keep environments aligned, and evolve delivery safely over time.

Configure once, reuse everywhere

Use the same stack across multiple apps and environments such as development, staging, and production.

Keep integrations inside the stack

Store third-party integrations such as managed databases, email delivery, storage, networking, and other external services in the stack.

Upgrade apps on your schedule

When a service update makes a stack outdated, upgrading releases a new stack version, and each app can move to it selectively or through auto-update settings.

Keep changes reviewable

Each stack has a template you can manage through the review and deployment workflow your team already uses.

Stack catalog

Browse application and service stacks

Stacks are grouped by what they are for, from app frameworks and CMS platforms to databases, search, observability, AI, and networking. Jump to a category or search by name or related terms, then open a stack to review its services, integrations, and deployment options.

Alias-aware search works for terms such as `mysql`, `varnish`, `redis`, `mail`, and `email`, and for category names such as `databases` and `observability`.

App frameworks & runtimesCMS & publishingDatabasesDatastores & messagingSearch & indexingObservabilityData & automationAIDeveloper platformsCollaboration & business appsNetworking & identityEmail & platform services

Stacks

App frameworks & runtimes

Language runtimes and framework stacks for building and deploying your own application from source.

Stacks

CMS & publishing

Content management and publishing platforms, with the web, database, and caching services they expect.

Stacks

Databases

Self-hosted database stacks and connection stacks for managed database providers.

Stacks

Datastores & messaging

In-memory datastores, caches, message brokers, and event streaming services.

Stacks

Observability

Metrics, logs, and traces, with the dashboards used to inspect them.

Stacks

Data & automation

Workflow orchestration, data processing, analytics, and automation platforms.

Stacks

AI

Model serving, AI chat interfaces, and coding agent stacks, including GPU-backed inference.

Stacks

Developer platforms

Git hosting, container registries, and backend platforms for development teams.

Stacks

Collaboration & business apps

Team collaboration, customer support, learning, and business application stacks.

  • Mautic

    Self-hosted Mautic marketing automation stack for contacts, segments, email campaigns, and landing pages, with MariaDB, shared NFS storage, background cron and queue processing, and optional outbound email.

    Source repository

    wodby/stack-mautic
    View stack

  • Moodle

    Self-hosted Moodle learning management stack with Nginx, MariaDB, shared NFS storage for Moodle data, a scheduled cron service, and outbound email.

    Source repository

    wodby/stack-moodle
    View stack

  • Odoo

    Self-hosted Odoo business applications stack with Nginx, PostgreSQL, shared NFS storage for the filestore, and optional outbound email.

    Source repository

    wodby/stack-odoo
    View stack

  • Slack Inviter

    Slack Inviter application stack for self-hosting a customizable community invite page with optional Turnstile protection when you already have a working legacy Slack administrator API token.

    Source repository

    wodby/stack-slack-inviter
    View stack

  • Zammad

    Self-hosted Zammad helpdesk stack with PostgreSQL, Redis, Memcached, optional Elasticsearch search, and outbound email.

    Source repository

    wodby/stack-zammad
    View stack

Stacks

Networking & identity

Private networking, remote access, tunneling, and single sign-on stacks.

Stacks

Email & platform services

Outbound email, mail capture for non-production environments, document conversion, and other supporting services.

Need a different stack?

Start from the closest stack in the catalog, compose your own stack from Wodby services, or maintain a custom stack definition.

Build from servicesRequest a stack

FAQ

Common questions about Wodby stacks

What lives in a stack?

A stack is the blueprint you use to deploy a new app. It defines the services, integrations, configuration, boilerplates, and deployment settings that app environments inherit.

How do integrations work in a stack?

Integrations are configured at the stack level, so managed databases, email, storage, networking, and other providers stay attached to the reusable app definition instead of being recreated per app. Environment-specific values can still differ where needed.

How do stack updates and revisions work?

If you enable optional auto updates for managed services, Wodby can issue a new stack revision when service updates become available. Any manual change to the stack configuration also creates a new revision. Apps and app environments using that stack do not have to upgrade immediately, so you can roll revisions out selectively when each environment is ready.

Can I reuse one stack across multiple apps and environments?

Yes. Teams can reuse the same stack across multiple apps or across development, staging, and production while keeping environment-specific values separate.

Can teams review stack changes before rollout?

Yes. Each stack has a template-backed definition, so teams can review stack changes in the workflow they already use and roll updates out deliberately.

Can the same stack run on different infrastructure?

Yes. You can deploy app environments from the same stack to Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes on a VM or dedicated server. Teams can mix them, such as production on managed Kubernetes and development on a leaner setup.