Store backups in Wasabi
Keep backup archives in a Wasabi bucket outside your application environment.
Integration
Wasabi integrations on Wodby
Use Wasabi Object Storage as an external backup destination on Wodby. Connect an access key pair, then choose a bucket for archives from backup-capable services. Wodby detects each bucket’s region, so one integration can serve buckets across regions.
Storage
Use one integration across regions
Provide a Wasabi access key and secret key with access to your backup buckets. Wodby finds each bucket’s region automatically; no endpoint URL is needed.
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
Store backup archives in Wasabi buckets with automatic region detection and one access key pair.
- Grant the key access to find bucket locations, check buckets, read and write objects, and discard failed multipart uploads.
- Connect the access key and secret key; Wodby detects each bucket’s region automatically.
- Allow bucket listing for the picker, or enter the exact bucket name when adding a backup destination.
Configuration surfaced to workloads
Access KeySecret Key
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.
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.
PostgreSQL
Stack
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 stackMariaDB
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 stackWordPress
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 stackDrupal 11
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.