Our frequently asked questions

Q: What does Cybee do?

Cybee backs up Windows and Linux servers to European clouds. Every backup is encrypted end to end on your machines before any transfer, stored immutably (S3 Object Lock) on EU object storage, and deduplicated at the source — so only new or modified blocks ever cross the network. Built on Restic, the open-source backup engine renowned for its reliability, Cybee industrializes it with what enterprises need: a lightweight agent for Windows and Linux, a central orchestrator that manages backup windows, bandwidth and priorities across your fleet, and a web console for supervision, reports and restore tests. The result: your backups sit outside the reach of the US CLOUD Act, remain unreadable to anyone but you (client-held encryption keys), survive ransomware attacks, and can be restored at up to 3 TB/h under optimal conditions. And because repositories use the open Restic format, there is no vendor lock-in: your data stays restorable without Cybee, forever.

Q: Is my backup data encrypted?

Yes — end to end. Data is encrypted with AES-256 directly on your machines, before any transfer to the cloud, and authenticated with Poly1305-AES to guarantee integrity. Encryption is not an option to enable: it is how Cybee works, always. The encryption keys remain under your exclusive control. Neither Cybee nor the storage provider ever holds them — which means no one but you can read your backups. If the storage were ever breached or your backup data exfiltrated, the content would be cryptographically unreadable to the attacker. This client-side model is also what places your backups beyond the reach of extraterritorial legislation such as the US CLOUD Act: even under legal compulsion, there is nothing readable to hand over. Confidentiality is cryptographic, not contractual.

Q: Are backups deduplicated?

Yes — at the source, block by block. Before anything leaves your server, Cybee splits data into blocks and checks which ones already exist in the repository. Only new or modified blocks are transferred and stored; identical data across snapshots — or across servers sharing a repository — is stored once. The impact is direct: on homogeneous Windows Server fleets, the observed reduction typically reaches 70 to 90%. That means proportionally less storage consumed, lower S3 costs and far less bandwidth used during backup windows. Deduplication also underpins one of Cybee’s pricing options: when you choose volume-based pricing, you pay for data actually stored after deduplication — not for the raw volume of your servers.

Q: Where are backups stored?

In the European Union, on S3 object storage operated by European providers. Object Lock immutability protects every backup: during the retention period, stored data can be neither modified nor deleted. Because Cybee is a French vendor and the storage chain is European, your backups sit outside the scope of extraterritorial US legislation such as the CLOUD Act and FISA 702. And since data is encrypted on your machines before transfer, with keys only you hold, even the storage provider never sees readable content. Data residency, legal jurisdiction and cryptographic confidentiality: the three layers of EU data sovereignty, combined by design.

Q: How does Cybee protect backups against ransomware?

Through three complementary layers of protection. Modern ransomware targets backups first, to leave victims with no way out. Cybee’s architecture is built so that the last clean restore point always survives. Client-side encryption. Data is encrypted with AES-256 on your machines before transfer, with keys under your exclusive control. Exfiltrated backup data is cryptographically worthless to an attacker. S3 Object Lock immutability. During the retention period, backups can be neither altered nor deleted — which is precisely what ransomware attempts before encrypting production. Least-privilege isolation. Each agent holds permissions strictly limited to its own scope: a compromised server cannot read or destroy the repositories of the rest of your fleet. When the worst happens, recovery is fast: parallelized cloud restores reach up to 3 TB/h under optimal conditions — a restart measured in hours, not days.

Q: What restore performance can I expect?

Cloud restores reach up to 3 TB/h under optimal conditions — dedicated bandwidth and an S3 bucket in the same region. This is what turns a disaster recovery plan measured in days into one measured in hours. Performance comes from the architecture: the Restic repository format enables massively parallelized reads from object storage, and the Cybee orchestrator prioritizes restore tasks over routine operations when an incident is declared. Restores are also granular: from the same snapshot, you can bring back a single file, a folder or a full volume — production-critical data first, archives later. And because you can run restore tests from the console at any time, the performance is verifiable in your own environment, not just promised.

Q: What is Restic and why did Cybee choose it?

Restic is an open-source backup engine with a worldwide reputation for reliability. Source-side deduplication, native client-side encryption, a publicly documented repository format: it has become the reference engine for engineers who take backup seriously. Cybee chose Restic for its transparency — auditable code, no black box, a repository format anyone can verify — and industrializes it with what raw Restic lacks in the enterprise: a deployment-ready agent for Windows and Linux, a central orchestrator managing bandwidth, priorities and backup windows, and a supervision console with reports and alerts. The choice has a structural bonus: because Cybee repositories remain standard Restic repositories, your backups stay restorable with the free open-source tools, without Cybee. Choosing an open engine is choosing no vendor lock-in.

Q: Is Cybee backup data subject to the US CLOUD Act or FISA?

No. The US CLOUD Act and FISA 702 allow American authorities to compel US companies to hand over data they control, wherever it is physically stored — including in European data centers. The exposure comes from the vendor’s nationality, not the server’s location. Cybee’s chain is European end to end: a French software vendor, backups hosted on S3 object storage operated by European providers, no US parent company. There is no entity in the chain that US legislation can compel. And even in a worst-case scenario, there would be nothing readable to hand over: data is encrypted on your machines before transfer, and the keys never leave your control. Jurisdiction protects you legally; client-side encryption protects you cryptographically.

Q: How is the confidentiality of data and backups ensured?

Through cryptography, not promises. All data is encrypted end to end with AES-256, directly on your machines, before any transfer to the cloud. Integrity is guaranteed by Poly1305-AES authentication: any tampering with stored data is detected. The encryption keys remain under your exclusive control, from day one. Neither Cybee nor the storage provider ever holds them — no one but you can read your backups, and no legal or technical process can change that. This is confidentiality by architecture: it does not depend on a contract clause, an employee’s discretion or a provider’s goodwill. It is how the system works.

Q: What backup frequency can I configure?

Backup frequency is freely configurable, per backup plan. Each server (or group of servers) follows its own plan, matched to how critical its data is and how fast it changes. What makes ambitious frequencies realistic is the orchestrator: it executes every task within its optimal window, arbitrating bandwidth, repository locks and priorities across the whole fleet. Frequent backups on one server never collide with production hours or starve the others. Deduplication helps too: since only new or modified blocks are transferred, increasing frequency increases protection far more than it increases volume or cost.

Question 1

Answer

Cybee acts as a processor under GDPR: data is hosted in the EU, encrypted end-to-end with client-held keys, and processed under a data processing agreement [ALIGN WITH FR : détails...

Our frequently asked questions

Is Cybee GDPR compliant?

Which operating systems does Cybee support?

What are the SLAs and support commitments?

Is the service managed? Who supervises my backups?

What happens at the end of the contract? (reversibility)

Does Cybee help me meet NIS2 requirements?

Is Cybee a disaster recovery (DRP) solution?

Is pricing based on machines or data volume?

What retention policies are available?

What backup frequency can I configure?

How is the confidentiality of data and backups ensured?

Is Cybee backup data subject to the US CLOUD Act or FISA?

What is Restic and why did Cybee choose it?

How does Cybee protect backups against ransomware?

Where are backups stored?

Are backups deduplicated?

Is my backup data encrypted?

What does Cybee do?