Key takeaways:
- Controvo can now target 3CX backups at S3-compatible object storage, so the vendor is your choice, not a fixed default.
- Works with any S3-compatible object storage. We validated it on Wasabi and Backblaze B2, and the same S3 protocol is what every other S3-compatible store speaks.
- You keep your backups on storage you already trust and already pay for, at object-storage prices.
- It also opens the door to keeping backups in a specific region, which matters for partners with data-residency requirements.
- We are not publishing the how. We are telling you it works, and you can put it to work.
Where your 3CX backups end up is not really your choice
Ask ten partners where their 3CX backups live and you will get a familiar set of answers: the default option because it was the path of least resistance, a local disk that is one hardware failure away from useless, or a storage bill that quietly grew as the fleet did. The place your customers’ backups sit is one of the more important decisions you make, and for most people it was never really a decision at all. You took what was in front of you.
We wanted our own backups somewhere specific: object storage we picked, priced the way object storage should be priced, with the option to keep a customer’s data in a particular region when that mattered. The catch is that getting 3CX to put its backups exactly where we wanted was not a checkbox. It took real work to figure out.
What we can now do
We can send 3CX backups to S3-compatible object storage. That means the large, cheap, durable object stores you already know, rather than a single default you are stuck with.
We validated it on Wasabi and Backblaze B2, running real backups to both. Both use the same S3 API that every S3-compatible store implements, which is what tells us this holds across the category rather than being a one-vendor trick.
S3-compatible object storage you can point 3CX backups at includes Amazon S3, Wasabi, Backblaze B2, Cloudflare R2, MinIO, DigitalOcean Spaces, Google Cloud Storage, IBM Cloud Object Storage, Oracle Cloud Object Storage, Scaleway Object Storage, Storj, Akamai (Linode) Object Storage, Hetzner Object Storage, OVHcloud Object Storage, and Seagate Lyve Cloud.
We are deliberately not writing up the method here. This was not obvious to work out, and the whole point is that Controvo does the hard part so you do not have to. What you get is the result: pick your storage, and your backups go there.
Why this matters
The money is the obvious part. Object storage from a vendor like Wasabi or Backblaze is priced very differently from the defaults most people fall into, and across a fleet of customers that gap compounds every month. Backups are one of the few line items you can cut hard without cutting anything your customers would ever notice.
The other part is control. When you choose the storage, you can keep a customer’s backups on a provider you already have a relationship with, spread risk across more than one place, and avoid being locked to a single vendor for something as critical as disaster recovery. For partners who have to keep data inside a particular country, choosing the storage is the first step to keeping backups in-region too. If that describes your market, our international page covers where we are with hosting and local requirements.
None of this changes the day-to-day. You still schedule, run, and track backups across every system from Controvo’s Backup Manager. The difference is where they land.
Try It
Want your 3CX backups on Wasabi, Backblaze, or another S3-compatible store? Open Controvo or get in touch and we will get you set up. Not in the pilot? Apply for early access.
For the full list of what shipped this month, see the Late August & September 2026 release notes.
