Integration

Wasabi integrations on Wodby

Use Wasabi Object Storage as an external backup destination on Wodby. Connect the regional service URL and an access key pair, then choose a bucket for archives from backup-capable services.

Storage

Store backups in Wasabi

Keep backup archives in a Wasabi bucket outside your application environment.

Connect the bucket’s region

Use the regional S3 service URL for your bucket, such as s3.eu-central-2.wasabisys.com, together with a Wasabi access key and secret key.

Plan backup retention

Choose retention with Wasabi’s minimum storage duration in mind: deleting objects early can still incur storage charges.

Supported workflows

How Wasabi fits into Wodby

Each supported integration kind maps Wasabi into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider configuration into workloads.

Storage

Object Storage

Send backup archives from Wodby services to a Wasabi Object Storage bucket using its regional S3 endpoint.

  • Create a Wasabi subuser with read and write access to the buckets you want Wodby to use.
  • Connect the bucket’s regional service URL, access key, and secret key.
  • Allow bucket listing for the picker, or enter the exact bucket name when adding a backup destination.

Configuration surfaced to workloads

Service URLAccess KeySecret Key
See backups and imports

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 Wasabi.

See backups and imports

Use storage integrations as backup targets for stateful services and app data.

View page

Browse all integrations

Compare this provider with the rest of the integration catalog and other supported workflows.

View page

Stack fit

Stacks that commonly pair with Wasabi

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.

  • Self-hosted PostgreSQL database stack for applications that want a managed Postgres service inside the same delivery workflow.

    PostgreSQL is a representative stateful stack when backup archives should land in external object storage.

    View stack

  • MariaDB

    Stack

    Self-hosted MariaDB database stack for applications that want a managed relational database inside the Wodby workflow.

    MariaDB stacks benefit from off-platform backup targets managed through a storage integration.

    View stack

  • WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.

    WordPress projects commonly want external backup storage for stateful production environments.

    View stack

  • Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.

    Drupal sites benefit from backup workflows that push archives outside the running environment.

    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.

Browse all integrationsIntegration feature overview