Bring your own storage and backups

What you get

• App files kept in a bucket your business owns
• Any storage provider that speaks the S3 API
• A second copy of the business's data every night
• Databases copied as standard PostgreSQL dumps
• A manifest listing each piece of every copy
• Exports written to your own bucket
• Uploads, virus scanning and video working the same

How it works

An owner enters the bucket's address, region, name and access keys under Settings, Storage in the dashboard. The keys are stored encrypted, like every other secret. From then on, the apps' storage settings point at that bucket.

Every night, Whisk also writes a second copy of the business's data into the bucket, in a folder for that date. It holds a pg_dump of each database, an archive of the files each app keeps on Whisk's servers, and a manifest. Each piece goes straight from the server into your bucket.

Whisk's own WAL-G and restic backups carry on as before, and point-in-time restores still use them. See backups and restore. The copy in your bucket is yours to keep, move or load elsewhere.

Example

A medical supplies distributor has customer contracts that require records to be held in its own cloud account. Its order and returns apps store files in that account's bucket, and the nightly copy sits beside them under its own retention rules.

For your coding agent

storage: true

Nothing changes in the app: it keeps reading WHISK_STORAGE_ENDPOINT and the other storage settings. An owner sets the bucket in the dashboard; the settings are in the environment reference.