Lock-in stopped being a contract problem and became a compliance one
Lock-in used to be a clause you fought over before signing. Since 12 September 2025 it is a compliance obligation. Under the EU Data Act (Regulation 2023/2854, in force since 11 January 2024), every cloud provider serving EU customers has a legal duty to let you leave. The switching rules sit in Chapter VI, Articles 23 to 31. The short version: you can move to another provider or to your own hardware inside a maximum 30-calendar-day transition window, the provider must hand your data back in a structured, machine-readable format, and from 12 January 2027 they cannot charge you a cent for it. A regulator now enforces what you used to negotiate, and the gap between what the law promises and what a provider ships is where the friction lives.
What the switching framework actually requires
The switching chapter is dense, but the obligations that matter to a buyer come down to a handful of concrete rules.
- A bounded exit clock. After you give notice (capped at two months), the provider gets a mandatory transition of no more than 30 calendar days to complete the switch. If they genuinely cannot hit 30 days for technical reasons, they must say so within 14 working days, justify it, and propose an alternative window that still cannot exceed seven months.
- Your data, in a usable shape. Exportable data and digital assets must arrive in a
structured, commonly used, machine-readable format, with a public register of the provider's data structures and interoperability specs. A proprietary blob you cannot parse does not clear that bar. - Functional equivalence, where it applies. For infrastructure-style services, the provider has to support restoring "a minimum level of functionality" at the destination, so the export is something you can stand up again.
- A retrieval window, then erasure. After the transition you get at least 30 more calendar days to pull anything left behind, after which the provider must erase your exportable data.
- The fee timeline. Until 12 January 2027 a provider may charge only the actual direct cost of the switch; after that date, switching charges are banned outright.
One honest caveat the marketing version of this law skips: the Act still permits "proportionate early termination penalties," which is legally distinct from a switching fee. Sign a three-year committed-use deal, walk in month four, and the provider can hold you to the unused commitment. The Data Act kills exit taxes, not the contract you agreed to. Read the commitment terms, not just the switching clause.
Where the law stops being enough
The Data Act guarantees you can get your bytes back. It says nothing about whether the provider could read those bytes while it held them.
Picture the worst case under a perfectly compliant exit. You leave AWS or Dropbox. They hand you a clean, structured export inside 30 days, charge nothing, erase their copy, compliant on every count. But the whole time your files lived there, they sat as plaintext on someone else's disk. Dropbox holds the keys; its only zero-knowledge option runs on Business tiers, not the free account. iCloud is not zero-knowledge unless you switch on Advanced Data Protection. A flawless legal exit does not retroactively unread a file; portability and confidentiality are different guarantees, and the Data Act delivers only the first. "You can always leave" is a stronger promise when the host never had readable access: the worst a zero-knowledge provider can do on your way out is hand back ciphertext it could never open.
Why open-source clients make "you can leave" checkable instead of promised
A switching right is only as good as the export mechanism. The Data Act gives you the legal lever; it does not write the code. You still depend on the provider's exporter working, and when the client doing the encryption is a closed binary, you are trusting a vendor's word that the lever connects to anything. That is the gap we tried to close structurally. Beebeeb's product clients are open source: the web app, the bb CLI, and the Rust crypto core that runs the AES-256-GCM encryption, Argon2id key derivation and X25519 key wrapping. You can read exactly how a file is sealed, which means you can read how to unseal it yourself, and the export format becomes something we cannot quietly degrade. To be precise: the clients are open, the server and this marketing site are not.
The practical exit path today is the bb CLI. It pulls your files, decrypts them locally with your key, and writes them back to disk as ordinary files in ordinary folders, no proprietary container, no waiting on a data-export request. Point it at rclone or WebDAV and you have a portable copy with our infrastructure out of the loop. Native desktop and mobile apps are coming, and Google Drive and Dropbox import is in the same queue; the public roadmap tracks where that work stands rather than dating it for marketing.
| Exit concern | What the Data Act guarantees | What beebeeb adds |
|---|---|---|
| Time to switch | 30 days max (7 months only if technically unfeasible) | Self-serve export now via the bb CLI, no clock to wait out |
| Export format | Structured, machine-readable | Plain decrypted files; format readable in open client source |
| Exit fees | Prohibited from 12 Jan 2027 | None; no minimum-duration or early-deletion penalty on storage |
| Confidentiality during tenure | Not addressed | Zero-knowledge on every tier, Free included; host holds only ciphertext |
How this changes a buying decision
The Data Act lets an EU buyer treat exit as a checklist item with teeth, but two questions it cannot answer for you still matter before you sign: can I parse the export without your software, and could you read my data while you held it? A compliant exit from a provider that kept your plaintext still means it lived on someone else's disk for years. None of that needs a sales call. Storage past the base plan is a flat €10.99 per extra TB up to 99 TB self-serve (custom quote beyond that), with the same encrypted sharing, file versioning and file-request features whether you stay a week or a decade. The law made the door a legal right. The version worth holding every provider to is the one where that door is also transparent: you hold the key, and the host was never able to read your mail.