VOOZH about

URL: https://www.plakar.io/

⇱ Plakar | The Open Standard for Backup and Restore


Back up and recover
your AI pipelines
from a single control plane.

Plakar is the open-source standard for efficient, secure backups.
Plakar Control Plane adds the visibility your organization needs across every inventory. It orchestrates your entire resilience posture, with backups defined by hand or as code, from one place.

plakar.mycie.com
Resources AWS inventory
Production Operation
Resource Type Apps Protection
app-server-01 EC2 __GITLAB__ __MYSQL__ __S3__ Protected

Apps on app-server-01

__GITLAB__

GitLab

Policies: Production, Operation

__MYSQL__

MySQL

Policies: Production, Compliance

2h ago
__S3__

S3

Policies: Operation

5h ago
db-primary RDS __PG__ Protected
web-server-01 EC2 __SFTP__ __FS__ Protected
cache-redis ElastiCache __REDIS__ Not protected
object-store-eu S3 __S3__ Protected
analytics-mongo EC2 __MONGO__ Protected
ci-runner-01 EC2 __GITLAB__ Not protected

Backup GitLab

App

__GITLAB__

GitLab

Policies: Production, Operation · app-server-01

Destination store

s3-backup-prod · APPEND_ONLY

Restore GitLab

Recovery point

Restore to

Because breach is no longer a risk, it's a certainty.

State-led ransomware, AI-driven exfiltration, and the erosion of the internal perimeter have turned cyber-resilience from a nice-to-have into the most important line of defense.

96% of ransomware attacks target backup repositories
43% of affected data is unrecoverable after an attack
45% of AI-generated code introduces security vulnerabilities
higher median recovery cost when backups are compromised

So "recoverable" has to actually mean something.

Five things Plakar delivers for security and infrastructure teams.

Radically efficient, by design.

Plakar deduplicates and compresses everything before it leaves your system, collapsing the storage and egress overhead that makes legacy backup so expensive. Protecting the whole estate costs a fraction of what traditional tools charge, so you never have to choose what to leave unprotected.

2 snapshots
SABAC
S+1ABACE
Kloset · unique chunks
ABCE
9 logical → 4 stored · encrypted

It runs on your environment, your storage.

Deploy Plakar on infrastructure you own. One engine protects every source across the estate, written to storage you control.

● Self-hosted

Run it on your environment

One binary, no appliance, no SaaS dependency. Run Plakar on the infrastructure you already operate: on-prem, in a private or sovereign cloud, or on any hypervisor. Your data and keys stay on infrastructure you control.

On-prem Private cloud 👁 Image
AWS
👁 Image
GCP
👁 Image
Azure
👁 Image
OVHcloud
👁 Image
Scaleway
👁 Image
VMware
👁 Image
Proxmox
Bare metal and more…
★ Your own storage

Storage provider agnostic

Snapshots land on storage you own, always with zero plaintext: any S3-compatible backend, local disk, or filesystem. On S3-compatible backends, object-lock immutability and append-only keep them tamper-proof.

👁 Image
AWS S3
👁 Image
Azure Blob
👁 Image
Google Cloud
👁 Image
MinIO
👁 Image
Backblaze B2
👁 Image
Cloudflare R2
👁 Image
NetApp
👁 Image
Local disk
and more…

And your whole backup posture lives as code.

Resilience as Code means your backup posture is defined, versioned, and automated, not clicked through a console. With the Plakar Kubernetes Operator, teams declare their entire backup strategy as native CRDs: sources, storage, schedules, retention, replication, and verification live in Git, reconcile continuously, and ship the same way the rest of your infrastructure does. Manage every policy through the Plakar API, a Terraform provider, or Ansible playbooks.

plakar — zsh
terraform apply
✓ plakar_backup_policy.postgres-prod created
  schedule = "*/15 * * * *" · retention = "30d-immutable"
  replication = [ovh, scaleway]
kubectl apply -f resilience-policy.yaml
✓ BackupPolicy/postgres-prod reconciled · GitOps-ready
ansible-playbook resilience.yml
✓ 12 hosts · policies converged
curl -s api.plakar.io/v1/coverage
✓ {"protected": 1420, "verified": "100%"}

It fits the estate you already have.

Dozens of sources and tools, one engine, and the long tail keeps growing. Missing something? Ask for it.

S3-compatible storage

Object-lock immutable, append-only destinations on storage you own. Live

Cloud providers

Agentless VM-level snapshots across your cloud estate. Live
👁 Image

PostgreSQL

Consistent full-database snapshots & dumps Live
👁 Image

MySQL / MariaDB

Encrypted, deduplicated database snapshots Live
👁 Image

Kubernetes

Cluster-native snapshots, GitOps-ready Live
👁 Image

Proxmox

Agentless VM & container snapshots Live
👁 Image

VMware vSphere

Agentless VM protection for hybrid estates Live
👁 Image

Docker

Snapshot container volumes & state Live
View all integrations →

Teams already trust Plakar.

Join us on Discord

"Very efficient, free, open-source, easy as hell to integrate."

r/
r/kubernetes
on Rook-Ceph S3 buckets

"The first big disruption to the backup / archiving world in a long time. Open source & built in Europe. Must have a look for SREs / sysadmins."

B
@bipbip
on X

"Plakar deduplicates and encrypts at the source so your cloud provider never sees your keys. And the snapshot model has no chain dependencies. You can delete any backup without breaking the others."

BF
Bret Fisher
DevOps & Docker Talk

"Restores 1 million items in 3 minutes."

TD
@tom_doerr
on X, benchmarking Plakar 1.1

"Plakar looks pretty slick, especially that Proxmox integration."

k
u/kernelqzor
r/linuxadmin

"Two little French geniuses just released a solution that's going to make you love backups."

K
Korben
on korben.info

Community powered

There must be a way to ensure backups remain accessible 10 or 30 years from now. Built with transparency, tested by the community and trusted for critical infrastructure.

Open source

Plakar is built by a global community of engaged developers, SREs, sysadmins and platform engineers.

Write your own plugins, contribute to the codebase or just help us.

Every chunk, accounted for. Voilà.

Nestor is Plakar's mascot, a chipmunk obsessed with chunks. His companion? Chunky Ptarson, a nut named after the .ptar format he calls home. Nestor carries the snapshots. Chunky is the snapshot.

"You're just… leaving your snapshots out there? Unverified?! Mon dieu. You have to protect your nuts!"

— Nestor, every time someone says their backups "just work"

Stay ahead with Plakar updates

Get exclusive insights, new features and expert tips on backup, storage and immutability.
No spam, ever.

Sign up with your email

We'll send you major product updates, no noise.

Back up anything. Prove it's recoverable.

The complete engine, free and open source. Organization-wide visibility when you need it. Your keys, your data, your recovery path.

Get started Book a demo →

Plakar Blog

Engineers thoughts, release notes and data protection latest news

See all posts Blog
announcement

Introducing the Plakar Control Plane free plan: Open Resilience for everyone, deployed on your terms

We’re launching a free plan for our first commercial product, Plakar Control Plane — a self-hosted backup management platform built on top of open-source Plakar. Fully functional, no time limit, deployed on infrastructure you own.

Victor Coisne · Jun 24, 2026 · 5 min read

Read more

announcement release note community

Plakar v1.1.3 is here

After a long beta and three release candidates, plakar v1.1.3 is finally out. It is the biggest release we have shipped so far: faster restores, much lower memory usage, a smaller cache footprint, a brand new terminal UI, better mounting, a new package manager, simpler integration interfaces, and a far more reliable execution model now that the agent is gone and cached has taken its place. It is stable, fully backward compatible, and ready for production.

Gilles Chehade · Jun 16, 2026 · 11 min read

Read more

release note

Plakar v1.1.0-beta: the foundation for what’s next

plakar v1.1.0-beta marks a major step forward, with significant performance gains, architectural simplifications, and powerful new user-facing features. From faster backups and restores to better mounting, cleaner integrations, and a more reliable execution model, this release lays solid foundations for what comes next. The beta is stable, backward compatible, and ready to be explored.

Gilles Chehade · Jan 26, 2026 · 14 min read

Read more

Pages

Solutions

Resources

Newsletter