Your data, in a cloud you own
Every file your team uploads to a project or job mirrors automatically into a storage bucket you own, in your own cloud account. You pick the region, you hold the encryption key, and if you ever stop using DroneBundle, every file is still yours.
Your bucket, your account, your keys
The copy is yours in every sense that matters. It sits in your account, in the region you choose, locked with a key only you hold.
A Bucket You Own, in the Region You Choose
Mirror into an Amazon S3 bucket in your own cloud account, billed to you and governed by your own policies. Pick the region so data stays in the country or jurisdiction you work under, and point DroneBundle at your own encryption key so every mirrored file is locked with a key you can rotate or revoke. Without it, nobody reads the files, including us.
Set Up Once, Guided From Inside the App
Create the bucket, grant DroneBundle scoped access to that one bucket and nothing else, and turn mirroring on. An in-app guide walks each step with the exact policy to paste, so you never leave to dig through cloud documentation. From then on every new upload is copied across on its own.
A Connection Test Before You Rely On It
One click runs a full dry run against your bucket. DroneBundle confirms it can reach the bucket, write a check file, and read it back, the same way real uploads will. If something is off, the result names exactly what to fix. A green status stays visible in your workspace, so you always know the mirror is healthy.
A Mirror That Runs Itself
Set it up once and it keeps a faithful, growing copy of your files in storage you control, with nothing to manage day to day.
Mirrored Automatically
Every file your team uploads to a project or job is copied across moments after it lands, with nothing for you to trigger or remember.
It runs in the background and asks nothing of you once it is on.
An Append-Only Archive
The mirror only ever adds and updates, so deleting a file inside DroneBundle never removes it from your copy. Changed files update, unchanged files are skipped, and duplicates never pile up.
Your bucket becomes a durable, growing archive of the work.
Laid Out by Project and Job
Copies arrive in the same structure you move through in the app. A project file lands under its project, a job file under its project and job, with the original name kept intact.
The bucket makes sense on its own, without opening DroneBundle.
Built to Feed Your Own Systems
Once files sit in your bucket, a backup routine, a data pipeline, or a mapping system can read them straight away. It sits alongside API access and webhooks as one more way your systems reach your data.
Events through webhooks, and the files behind them here.
Why Teams Keep Their Own Copy
A copy that exists only in a supplier's account is a gap. Data Ownership closes it, whether you do it for the rules you work under or simply as insurance against lock-in.
You Own the Data Outright
The copy sits in your account, billed to you, under your own retention and access rules. Stop using DroneBundle tomorrow and every file is still yours.
Keep Data Where the Rules Require
Choose a bucket in the region you need and keep a compliant copy, without changing how your team works day to day.
Encrypted With a Key Only You Hold
Every mirrored file is locked with your own key, one you can rotate or revoke at any time from your own console.
Sits alongside DroneBundle’s other enterprise connections, including API access, webhooks, and GDPR and data residency.
Keep a copy in storage you control
If holding your own copy of the data is a requirement, or simply a preference, we will help you get it wired up to your own cloud.
