Your bucket. Your data.
Pipe every Orshot render directly into your own S3, Cloudflare R2, Dropbox, or Google Drive. Your domain. Your retention. Your access control.
Included on every paid plan
Four providers supported
Amazon S3, Cloudflare R2, Dropbox, and Google Drive — pick what fits your stack.
Your credentials
Connect with your own IAM role or API key — we never store more than we need.
Direct upload
Renders stream straight to your bucket. No round trip through our storage.
Your retention
Set your own lifecycle rules and keep data as long as you need.
Connect a bucket in two minutes.
Add your storage credentials once per workspace. Every render for that workspace lands in your bucket, named exactly how you want it.
- S3, R2, Dropbox, or Google Drive — toggle per workspace
- Use IAM roles, access keys, or scoped tokens
- Customize the object path template per render
- Auto-cleanup — or keep forever, your call
Built for teams with their own data rules.
If your security team needs data to stay in your account, Orshot stays invisible. We render, you store.
- No render data retained on Orshot servers
- Works with your existing bucket policies and encryption
- Per-workspace isolation so clients never share storage
- GDPR and DPA compatible
Custom file paths
Template the S3 object key per render — use variables from the payload.
Signed URL support
Generate time-limited signed URLs for any stored render on demand.
Sub-2s render-to-bucket
Warm-started workers deliver straight to your bucket — no extra hop.
Keep your data. Skip the dependency.
Available on every paid Orshot plan. Connect your bucket, render, own the files.