One provider, several workflows
Wodby can cover multiple operational surfaces on Wodby instead of forcing teams to split cluster, storage, database, and mail concerns across several vendors.
Integration
Wodby integrations on Wodby
Wodby includes built-in integrations for Cloud, CI, Registry, and Cloud Storage, so teams can keep core delivery workflows inside the same platform surface without depending on a third-party provider for every step.
KubernetesCIRegistryStorage
Keep credentials reusable
A shared provider account or access model can support several Wodby workflows at once.
Match managed services to app stacks
Teams can combine provider-managed infrastructure with Wodby stack-based application delivery.
Supported workflows
How Wodby fits into Wodby
Each supported integration kind maps Wodby into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.
Kubernetes
Wodby Cloud
Use Wodby as a managed Kubernetes target for Wodby stacks.
- Deploy the same versioned stack model onto a managed cluster target.
- Keep cluster operations with the provider while Wodby stays responsible for the app delivery workflow.
- Useful for teams that want managed infrastructure without rebuilding their stack definitions.
CI
Wodby CI
Use Wodby for build and release automation while Wodby manages the runtime stack.
- Lets the team keep build, test, and release logic in the CI system they already use.
- Works well with Wodby CLI and stack-aware deployment workflows.
- Separates pipeline automation from runtime stack management.
Registry
Wodby Registry
Store built images in Wodby and promote the same artifacts across environments.
- Keep image storage separate from cluster runtime and environment configuration.
- Useful when the team already distributes or mirrors images through this registry.
- Supports build-once, deploy-many release patterns.
Storage
Cloud Storage
Send backup archives and storage-backed data from Wodby services to Wodby.
- A practical fit for stateful services that should keep backup archives outside the running environment.
- Works with automatic backup workflows and restore paths.
- Lets teams standardize on an object storage target without changing the app stack itself.
Related features
Explore the surrounding workflow
This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Wodby.
Explore Kubernetes delivery
See how Wodby deploys versioned stacks onto managed Kubernetes targets.
Explore CI/CD workflows
Keep pipelines close to the repo while Wodby handles stacks and runtime services.
See backups and imports
Use storage integrations as backup targets for stateful services and app data.
Browse all integrations
Compare this provider with the rest of the integration catalog and other supported workflows.
Stack fit
Stacks that commonly pair with Wodby
Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.
Next.js
Stack
Next.js application stack for frontend and full-stack projects that need a reusable deployment setup.
Next.js is a strong fit when you want source, build, runtime, and registry workflows to stay tightly integrated with Wodby.
View stackDrupal 11
Stack
Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.
Drupal teams often benefit from keeping stack delivery, backups, and infrastructure in one operational surface.
View stackCloud PostgreSQL
Stack
Connection stack for apps that use managed PostgreSQL services such as Amazon RDS instead of self-hosting Postgres inside the stack.
Cloud database stacks pair well with Wodby-managed delivery when teams want the app workflow and provider plumbing in one place.
View stackOpenClaw
Stack
Private OpenClaw gateway stack for always-on agent workflows with integrations such as Tailscale.
OpenClaw benefits from built-in delivery, storage, and infrastructure workflows when the gateway is operated as a long-lived service.
View stack
Compare providers or keep reading
Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.