Cloudflare R2 Storage

Process video in your R2 bucket

Rendobar reads job inputs from your Cloudflare R2 bucket and writes outputs back next to them. One API token scoped to that bucket connects it, and Rendobar discards the token after exchanging it once for a key pair.

Overview

Jobs read objects in the bucket as storage:// paths and write outputs back beside them. R2 charges no egress, so serving those outputs costs storage and operations only. The dashboard connects the bucket with one scoped API token, and the R2 docs cover access keys and jurisdictions.

Questions

Does Rendobar keep my R2 API token?

No. Rendobar exchanges the token once for the S3 key pair it stands for, then discards it. The key pair is encrypted with AES-256-GCM, and no endpoint returns it.

Why scope the R2 token to one bucket?

Deleting a bucket doesn't revoke its token, so a token for all buckets keeps reaching every other bucket in the account. Rendobar never creates or deletes buckets, so Admin Read & Write grants more than it uses.

Does Rendobar work with R2 buckets in the EU jurisdiction?

Yes. EU and FedRAMP buckets use their own endpoint. Set the jurisdiction under More options when you connect.

Can R2 outputs have public links?

Yes. Set the bucket's r2.dev address or a custom domain as the connection's public URL, and each delivery comes back with a link on that host.

All integrations