🧩 Works with Any PHP Site ⬇️ Free Download 🔐 No Passwords Shared ☁️ Your Own Cloud 🧩 Works with Any PHP Site ⬇️ Free Download 🔐 No Passwords Shared ☁️ Your Own Cloud
Website Backup

Back Up Any Website with One PHP Module
No Plugin, No Shared Credentials

WordPress, WooCommerce, OpenCart, Joomla, Laravel or a hand-written PHP site — they all use the same module. You add your domain, upload the folder generated for it to your web root, press Verify in the panel, and backups run automatically. Your FTP and database passwords never leave your server.

No credit card required · Current campaign: free until the end of the year

Setup

Four Steps, Any Platform

The install is identical regardless of what your site is built with.

1️⃣

Create an account and add your domain

Open a free account in the Yedekalma panel and add your domain. The module zip package is generated for that domain only: the folder name and access key are built into it.

2️⃣

Upload to your web root

Unzip the package you downloaded from the panel and upload the folder inside to your web root via FTP or your file manager without renaming it.

3️⃣

Verify from the panel

Press Verify in the panel and the module connects itself. Because the access key already comes inside the package, there is no token to paste.

4️⃣

Schedule

Choose frequency, components and storage target. Everything after this is automatic.

Architecture

Why a Module Instead of a Plugin?

A plugin lives inside your site. When the site breaks, so does the plugin.

🧩

Platform independent

One module for every PHP site. You do not need a different tool for each platform.

🛡

Survives site failure

The module sits outside your CMS, so a broken theme or plugin does not take your backups down with it.

🔄

Independent of CMS updates

CMS core upgrades do not touch the module folder, so it works regardless of your CMS version.

🔐

Credentials stay local

Database credentials are read and kept by the module on your server; you never share database or FTP passwords with us.

📦

No backup storage on our side

Backups go straight from your server to your storage target. Backup files are not stored on our servers.

🌐

No inbound access needed

You do not open database ports or hand out SSH access.

Requirements and limits

The module requires PHP 7.1 or newer (8.1+ recommended) and runs on Linux PHP hosting. Before installing, a compatibility test in the panel checks the PHP version, required extensions, write permissions, outbound access and large-file handling. For databases, MySQL and MariaDB are supported — PostgreSQL, SQLite, MongoDB and SQL Server are not.

The module must be reachable over the web, so it goes in your document root. On frameworks where the document root is a subdirectory (Laravel's public/, for example) install it there.

Folders outside the site root can be added to the backup as Extra folders in the module's own settings screen; one that doesn't work is flagged in red in the panel. Older archives already sitting on your server can be brought into the panel as imported backups.

Comparison

Backup Solutions Compared

1. File Backup Comparison

Feature / Comparison Yedekalma (Automatic) Classic Manual Method (FTP etc.) Other Software / Tools
AES-256 Encryption ✓ Optional, applied on your server before upload ✗ None (files are transferred unencrypted) Varies by product
File Transfer Speed ✓ Optional incremental mode: only changed files ✗ All Files Every Time (Slow) Often a full archive every time
Server Disk Space ✓ Temporary space while packaging only; no permanent copy kept ✗ Temporary compressed files take up disk space Archives often kept on the same server
Central Management ✓ Managed from a Single SaaS Panel ✗ Manual Tracking Required Varies; often one login per site

2. Database Backup Comparison

Feature / Comparison Yedekalma (Automatic) Manual SQL Export Other Software / Tools
Credential Security ✓ Database password is never shared with us ✓ No password sharing (local access) Some ask for database credentials
Scheduled Automatic Task ✓ Easy Scheduling from the Panel (No Extra Tasks) ✗ Must be triggered manually every time Often needs a server-side cron job
Encrypted Storage ✓ With encryption on, the database dump is encrypted too ✗ SQL downloads as plain text Varies by product
Guided Restore ✓ 3-step restore wizard in the panel (component · summary · confirm) ✗ Manual and risky via phpMyAdmin import Varies by product

The "Other Software / Tools" columns describe general practice to the best of our knowledge (August 2026); individual products and versions may differ.

FAQ

Website Backup Tool — Frequently Asked Questions

Yes. Our PHP backup module works with a client-side architecture: you never share your site's database or FTP passwords with us. Your data is compressed on your server and uploaded straight to your own storage target — your own server, Google Drive, Amazon S3 and S3-compatible services (Backblaze B2, Wasabi, Cloudflare R2, MinIO), OneDrive, Yandex.Disk, Dropbox (max 150 MB per archive) or the password-free Receiver Module on a separate server, up to 3 destinations at once. Backup files are not stored on Yedekalma's servers. Optional AES-256 encryption encrypts the archive on your server before it leaves; the passphrase is known only to you; we do not store it and cannot open your backups. Encrypted archives are opened with the Yedekalma module or the WordPress plugin; with encryption off, backups are standard zip/SQL/.eml files.
Any site running PHP 7.1 or newer (8.1+ recommended) with a MySQL/MariaDB database. That includes WordPress, WooCommerce, OpenCart, PrestaShop, Joomla, Drupal, Laravel/Symfony and custom PHP applications. The install steps are identical in every case, which is why there is a single module rather than one plugin per platform.
With classic control panel backups, the whole server archive is taken manually and stays on the server's disk. Yedekalma runs on a schedule, can encrypt the archive on your server (optional AES-256) and transfers it straight to your own external storage target (your cloud storage or the Receiver Module on a separate server). Temporary space is used while packaging, but no permanent copy is kept on your server.
No. You plan your backups in the Yedekalma SaaS panel, and our server triggers the PHP backup module on your site automatically. There's no need to set up an extra cron job on your server.
The module itself is free. You open a Yedekalma account and add your domain; the module is generated for that domain, downloaded from your panel and connected with the Verify button — there is no token to paste. The automatic backup service runs on an annual subscription, and new accounts start with a free trial — in the current campaign until the end of the year, for 1 domain, with no credit card required and no automatic charge at the end.
No. We do not ask for SSH, root or FTP access. The module runs with the web user's permissions and only reads what it can already reach. Backups are triggered over HTTPS and packaged locally on your server.
Yes. Your backups live in your own storage (Google Drive, S3 and so on), completely independent of your server. If the server is lost you install the module on a new one and restore there.
Yes. You can define exclusion paths, which is useful for cache directories, build output and large media you back up separately. Going the other way, folders outside the site root can be added as Extra folders in the module's settings.

Download the Module and Start in Minutes

Free download, four-step setup, free trial until the end of the year (current campaign). No credit card required.

Create Free Account

See all solutions →