All integrations

S3-compatible storage integration

Captures written straight to a bucket you own

Point scheduled captures, or a single Instant Snap API request, at any S3-compatible bucket. The file lands in your storage, under your access policy and your lifecycle rules, where your own systems can read it.

Auto ScheduleInstant Snap API

At a glance

Products
Auto Schedule and Instant Snap API
Providers
Amazon S3, Cloudflare R2, Wasabi, Backblaze B2, MinIO, DigitalOcean Spaces and more
Schedules
Every paid plan: 1 destination per capture on Starter, 2 on Pro, 3 on Business
Access
A key of your own, scoped to one bucket

Why teams deliver to their own bucket

Anything that speaks S3

Amazon S3, Cloudflare R2, Wasabi, Backblaze B2 through its S3 endpoint, MinIO and other self-hosted stores, DigitalOcean Spaces, Linode Object Storage.

For schedules and for the API

Scheduled captures deliver to a connected bucket. An Instant Snap API request with response_type cloud_storage writes its file to the bucket named in the request.

Your policy, your keys

Use a dedicated key scoped to one bucket. Uploads only write objects; nothing on our side reads your captures or any other bucket.

Nothing kept on our side

With a bucket connected, a Web Profile can be set to Do not keep after delivery, so the only copy of each capture is in your storage.

Feeds your other systems

A bucket is something other systems can read: a report builder, a comparison job, an evidence archive, a data pipeline.

Tested before it is used

Save & test checks the bucket with your settings straight away and shows the reason beside the fields if it cannot reach it.

Connect a bucket

  1. 1

    Create a key for this job

    At your provider, create a key that can write, list and delete in one bucket only - not your root credentials.

  2. 2

    Add the destination

    In the app's Cloud Storage, choose Add destination, then S3-compatible bucket, then Next: bucket details.

  3. 3

    Enter the bucket and test it

    Fill in the bucket, region or endpoint and the key pair, then Save & test. If a correct key still fails, try the path-style addressing toggle.

  4. 4

    Deliver to it

    Choose the bucket in your Web Profiles, or send s3_delivery with an Instant Snap API request.

FAQ

Questions about S3-compatible storage

Does it work with Cloudflare R2, Wasabi or MinIO?

Yes. Anything that implements the S3 API works: give the endpoint address instead of a region, and switch on path-style addressing if your provider wants it.

What permissions does the key need?

Writing objects for the uploads. The connection test also lists the bucket and writes and deletes a small test file. Nothing needs to read your captures or any other bucket.

Should the bucket be public?

No. A public bucket makes every capture public, including pages behind a login. Keep it private and share files from it on your own terms.

How do I stop captures piling up?

Set a lifecycle rule on the bucket to expire or cold-tier old captures. Doing it at the storage side is cheaper than deleting them one by one.