Strategic autonomy

Reclaim control of your data,
whoever hosts it.

Keep a reversible, encrypted copy of your critical data at a provider you choose, with keys you hold. If a provider pulls the plug or reprices, you restart elsewhere.

The problem

Dependence is the risk nobody budgets for.

Regulators, boards, and customers now ask the same question: if your provider fails, changes its terms, or receives a foreign legal request, can you still recover?

Backups tied to one provider

Native snapshots live in the same account, region, and vendor as production. An outage, a lockout, or a pricing change takes both.

Keys held by someone else

When the provider manages your encryption keys, it can be compelled to hand over readable data. Your confidentiality depends on its policies.

Licences that change under you

Per-socket, per-VM, or per-500 GB licences get repriced overnight, and your backups sit in a format only that vendor can read.

How it works

Autonomy built into the architecture.

Not a policy you have to trust. A design that leaves you in control.

  1. 01

    Runs in your environment

    The Control Plane is a virtual appliance you deploy in your own environment. Only consumption metrics go back to Plakar, never backup data, and nothing at all in air-gapped mode.

  2. 02

    Keys stay with you

    Data is encrypted at the source. Passphrases live in your Control Plane or your own secret manager: HashiCorp Vault, AWS, Google Cloud, Scaleway, or OVHcloud.

  3. 03

    Data stays where it belongs

    Write snapshots to storage you choose, on European providers such as OVHcloud and Scaleway or on-premises. Residency rules keep backups, restores, and copies in the right country.

  4. 04

    An Open format

    Kloset, the format your snapshots live in, is Open, with a public SDK. Your backups never depend on one vendor's roadmap, ours included.

What you get

Independence you can switch on today.

Self-hosted appliance

AWS, Google Cloud, OVHcloud, Scaleway, Exoscale, VMware vSphere, or Proxmox VE.

Learn more

Air-gapped operation

An offline license and a self-hosted package repository for installs and updates.

Learn more

Data residency

Tie resources to a country. Backups, restores, and copies stay within it.

Learn more

Your secret manager

Vault, AWS, Google Cloud, Scaleway, or OVHcloud.

Learn more

European inventories

Discover OVHcloud, Scaleway, and VMware resources.

Learn more

Cross-provider copies

Sync a Kloset to another provider or storage tier.

Learn more

Open Kloset format

An Open snapshot format with a public Go SDK, and export to tar or zip. Your backups never depend on one vendor.

Learn more

Portable .ptar archives

One self-contained, encrypted file you can move to any provider or keep offline.

Learn more
Proven in production
“Running on infrastructure and software we control has unlocked a full compliance track for us with French providers.”
Pierrick Gicquelais
Pierrick Gicquelais Lead Infrastructure & AI Platform
Alan

Compliance

Compliance building blocks.

No tool makes you compliant on its own, and Plakar holds no certification itself. It runs and stores inside the perimeter you choose, so backups stay within your ISO 27001, HDS, or SecNumCloud scope, and it gives you the controls NIS2 and DORA expect.

NIS2, Art. 21 Backup management and disaster recovery SLA policies set frequency and retention per tier. Sync tasks keep a second copy, and check tasks verify every snapshot.
NIS2, Art. 21 Cryptography and encryption End-to-end encryption at the source, with independently audited cryptography and keys in your own secret manager.
NIS2, Art. 21 Access control, asset management, and MFA Granular roles, two-factor authentication you can require, an audit log, and inventories of what must be protected.
DORA, Art. 12 Backup policies, restoration, and recovery Policies show the RPO they deliver. Restore any snapshot to its original location or a separate one.
DORA, Art. 12 Segregated backup copies Copies on a different provider, account, or storage tier, or offline in a self-contained .ptar archive.
DORA, Art. 28 Exit strategies for ICT providers A self-hosted control plane, an Open format, and storage on any provider, so leaving one never means losing your backups.

Get started

Bring your resilience strategy home.

Start on the free plan, or map your NIS2 and DORA backup requirements with our team.

See how it fits together on the Control Plane page.