⚖️ Four Methods Compared 🔓 No Vendor Lock-In 📦 Backups Never Touch Us ✉️ Email Included ⚖️ Four Methods Compared 🔓 No Vendor Lock-In 📦 Backups Never Touch Us ✉️ Email Included
Comparison

Which Backup Method Suits You?
Hosting Backup · Plugin · Manual · Yedekalma

When choosing a backup solution the real question is not "which has more features" but "which one actually works on the bad day". Below we compare four approaches honestly — including where we fall short.

No credit card required · 14-day free trial

Comparison

Backup Methods Compared

This compares categories of method rather than individual products. Any given plugin's feature list can change tomorrow; the differences between approaches are structural and persist.

Capability Hosting
backup
Free
plugin
Manual
backup
Yedekalma
Automatic scheduling
Backup stored OFF the server ~ ~
Email (IMAP) backup ~
Table-level incremental DB ~
Malware scanning ~
Immutable backup (WORM)
Your own encryption key ~
Backup verification / drills
Single-file recovery ~ ~
Multiple targets at once ~
Many sites in one panel
Missed-backup alerts ~
Server / hosting migration ~ ~ ~
Provider independent (no lock-in) ~

✓ usually available · ~ varies or limited · ✕ usually absent. "Varies" columns differ by provider or paid tier.

Four Approaches

The Strengths and Weak Points of Each

None is universally bad; what matters is knowing where each one breaks.

🏢

Hosting backup

Good: free and requires no setup. Breaks when: the backup usually lives on the same infrastructure as your site, so losing the server or the account loses it too. Retention is also typically short.

🔌

Free plugin

Good: quick to install and often enough for a single site. Breaks when: if the site goes down the plugin goes with it; it does not cover email, does not verify restorability, and cannot manage many sites centrally.

💾

Manual backup

Good: full control and no vendor lock-in. Breaks when: consistency. It gets skipped in a busy period and cannot be taken retroactively; the age of your last backup defines the size of the loss.

🛡

Yedekalma

Good: automatic, independent of your site, includes email, verified, and manageable across many sites from one panel. Limit: it is a paid service and requires installing a module on your server.

What Sets Us Apart

Four Real Differences

📦

Backups never touch us

Your data goes straight to your own cloud (zero-server-storage). We are not a storage provider, so you do not buy gigabytes from us and your data does not sit with us.

✉️

Email is a first-class component

Alongside files and databases, IMAP mailboxes are backed up and can be written back. Most alternatives do not cover this.

🔒

Immutable copies

S3 Object Lock (WORM) lets you make a backup unmodifiable. Even ransomware inside your system cannot delete that copy.

🔓

No lock-in

Archives use standard formats: zip for files, an SQL dump for the database, .eml for messages. Your backups stay readable even if you leave us.

When Yedekalma is NOT the right choice

It may seem odd for us to write this, but a service bought on the wrong expectation helps nobody:

Your site does not run PHP — the module needs PHP 7.0+. It is not suitable for purely static sites, Node.js or Python applications.
You use a database other than MySQL — PostgreSQL, MongoDB and SQL Server are not supported.
You have a single very small brochure site — a free plugin may well be enough, and we will say so.
You are looking to back up a computer or phone — we only back up assets on a web server.

FAQ

Backup Comparison — Frequently Asked Questions

A hosting backup is convenient but not sufficient alone, because it usually sits on the same infrastructure as your site. If the server is lost entirely, the account is suspended or ransomware encrypts the disk, the backup is affected by the same event. Keeping at least one copy somewhere independent is the fundamental rule of backup.
For a small brochure site it might. But plugins generally focus on a single site, do not cover email, do not verify that a backup actually restores, and do not let you monitor many sites from one place. And because a plugin runs inside the site, when the site fails your backup tool fails with it.
Manual backups are the most flexible method — as long as they are actually taken. The problem is consistency: in a busy week it gets forgotten, and it cannot be taken retroactively. When data loss happens, the older your last backup, the bigger the loss.
They are already in your own storage; we never hold them. If your subscription ends the files stay exactly where they are. The archives use standard formats — zip for files, an SQL dump for the database, .eml for email — so they open without our tooling.
Yes, there is no technical obstacle, and keeping more than one copy is the general rule of backup anyway. Just avoid scheduling both at the same hour; two backup jobs running simultaneously put unnecessary load on your server.

Compare It Yourself

The best comparison is a trial. 14 days free, no credit card, no automatic charge at the end.

Create Free Account

See pricing →