The backup Independence

"Independent" gets used loosely in backup marketing. For us it's not one claim — it's three layers, and we think all three have to hold for the word to mean anything.

🔒 Tenant independence. Your backup isn't stored inside the tenant it protects. If ransomware hits, an admin account gets compromised, or you're locked out entirely, the backup isn't going down with it — because it was never inside in the first place.

🏢 Vendor independence. The copy of your data sits on infrastructure you run, not inside another company's cloud. We still need API access to read your directory, like any backup tool does — but where the copy actually lives is the difference. Not our uptime, not our jurisdiction, not our business continuity plan standing between you and your data.

📄 License independence. If you ever stop paying us, your existing backups stay restorable. No SaaS kill switch, no data held hostage to a renewal.

Most backup pitches lead with restore speed or feature coverage. We think the more important question is simpler: where does the copy actually live, and what happens to it if something — anything — goes wrong with the system it's supposed to protect you from.