External systems connected through one integration model

Integrations for delivery, data, and external services

Integrations connect stacks and platform workflows to external systems and built-in platform capabilities. Use them for Git repositories, CI pipelines, image registries, backup storage, managed databases, SMTP delivery, VPN access, and variables and secrets.

That keeps provider access centralized instead of scattering credentials, provider settings, email relays, and operational glue across application code, environment files, and ad hoc scripts.

Browse integrationsWhy integrations matterFAQ

What integrations help with

Source, build, and images

Connect Git providers, CI pipelines, and registries so source, builds, and images stay inside one delivery model.

Backups and managed data

Send automatic backups to external storage and connect cloud database services to managed database providers.

Email, secrets, and private access

Keep SMTP relays, provider credentials, API keys, and VPN access outside application code and managed through integrations.

Built-in platform integrations

Use Wodby CI, Wodby Registry, and Wodby Cloud Storage together with third-party providers from the same catalog.

Benefits

Why teams centralize integrations

Integrations keep external providers inside the same operating model as stacks, services, apps, backups, and deployment workflows.

Centralize provider access

Keep Git providers, CI systems, registries, storage, managed databases, SMTP, VPN, and secrets in one integration catalog instead of wiring them separately in every repo.

Keep third-party credentials out of code

Variable integrations centralize API keys, tokens, DSNs, and provider-specific settings instead of scattering them across repositories and environment files.

Cover delivery and operations together

Integrations are used for source retrieval, build pipelines, image storage, backup uploads, managed databases, outbound email, and private connectivity.

Mix built-in and third-party providers

Use Wodby CI, Wodby Registry, and Wodby Cloud Storage together with AWS, GCP, Azure, DigitalOcean, GitHub, GitLab, Docker Hub, and other providers.

Integrations catalog

Browse integrations by category

Search for providers, integration types, or related terms, then open the provider page to review the supported kinds and setup details.

Search also works with related terms such as `s3`, `gcs`, `rds`, `email`, `secrets`, `dockerhub`, and `circleci`.

Storage & backupsManaged databasesGit providersPrivate networkingSMTP & emailRegistriesCIVariables & secrets

Storage & backups

Storage & backups

Storage integrations receive automatic backup archives from container-based services and send them to providers such as Wodby Cloud Storage, Amazon S3, Google Cloud Storage, Azure Blob, and DigitalOcean Spaces.

Managed databases

Managed databases

Database integrations connect cloud database services such as Cloud PostgreSQL, Cloud MySQL, and Cloud MariaDB to managed offerings like Amazon RDS, Cloud SQL, Azure Databases, and DigitalOcean Databases.

Git providers

Git providers

Git integrations connect repositories from GitHub, GitLab, and BitBucket so builds can pull application source code.

Private networking

Private networking

VPN integrations let workloads reach private networks and internal services through providers such as Tailscale.

SMTP & email

SMTP & email

SMTP integrations let services such as OpenSMTPD relay outbound email through providers like Amazon SES and Brevo.

Registries

Registries

Registry integrations store built images in Wodby Registry, Docker Hub, or other compatible registries.

CI

CI

CI integrations connect build pipelines such as Wodby CI, GitHub Actions, and CircleCI.

Variables & secrets

Variables & secrets

Variable integrations store third-party credentials such as OpenAI keys, Stripe secrets, Sentry DSNs, Slack tokens, and other provider settings outside application code. Teams can also create custom variable providers by entering a provider name, defining fields, and choosing which environment variables Wodby should add to connected app service containers.

Need a different integration?

Start from the providers already in the catalog, or contact Wodby if you need a provider or integration kind that is not listed yet.

See integrations featureRequest an integration

FAQ

Common questions about Wodby integrations

What is an integration on Wodby?

An integration connects a stack or workflow on Wodby to an external system or provider, such as Git, CI, storage, managed databases, SMTP, VPN, registries, or variables and secrets.

How are integrations different from services?

Services are the building blocks that run inside stacks. Integrations connect those stacks and workflows to external systems or built-in platform capabilities.

What are variable integrations used for?

Variable integrations store third-party credentials such as API keys, tokens, DSNs, and other secret-based settings outside application code, while still making them available to the workloads that need them. Wodby also supports custom variable providers where you define the provider name, field names, and the environment variables that should be added to connected app service containers.

Can I create a custom variable provider?

Yes. You can create a custom variable provider by entering the provider name, defining the fields the integration should collect, and choosing which environment variables Wodby will add to the connected app service container when that integration is attached.

How do storage integrations work?

Storage integrations are used by automatic backup workflows and other storage-backed features. They let services upload backup archives to providers such as Wodby Cloud Storage, Amazon S3, Google Cloud Storage, Azure Blob, and DigitalOcean Spaces.

How do database integrations work?

Database integrations are used by cloud database services such as Cloud PostgreSQL, Cloud MySQL, and Cloud MariaDB. They keep the app connection to managed databases such as RDS, Cloud SQL, Azure Databases, and DigitalOcean Databases inside the same Wodby workflow.

Can a provider support more than one integration kind?

Yes. Some providers support multiple integration kinds. For example, a cloud provider can expose storage, managed database, and Kubernetes-related capabilities at the same time.

Does Wodby include built-in integrations?

Yes. Wodby includes built-in options such as Wodby CI, Wodby Registry, and Wodby Cloud Storage alongside third-party providers.