⚙️ Laravel Project Backup 📦 No Composer Package 🔐 Passwords Stay With You ☁️ Your Own Cloud ⚙️ Laravel Project Backup 📦 No Composer Package 🔐 Passwords Stay With You ☁️ Your Own Cloud
Laravel Backup

Back Up Your Laravel Site Automatically
Files · Database · Email — One Module

You do not need to add a package to your project or write an artisan command. The Yedekalma module runs independently from your project's web root and backs up application files, your MySQL database and — if you use them — your mailboxes. Backups go straight to your own cloud.

No credit card required · free trial until the end of the year

Specific to Laravel

What Do You Actually Lose on a Laravel Site?

Before choosing a backup plan you need to know where each kind of data lives.

💾

Database

All of your application's business data lives in the database and has no copy in your code repository.

📁

User uploads

Files under storage/app are not tracked in version control — losing them is permanent.

🔑

.env configuration

Environment variables never enter the repository; recreating them after a server loss takes time.

🗃

Cache and sessions

File-based cache and session data is not critical but speeds recovery considerably.

📜

Log files

Application logs needed for incident analysis exist only on the server.

🧩

Vendor and build output

Dependencies can be reinstalled, but version drift can cause unexpected behaviour.

Setup

Laravel Backup in Four Steps

1️⃣

Create an account and add your domain

Open a free account in the panel and add your domain; the module zip is generated for that domain only. Nothing is installed inside Laravel itself.

2️⃣

Upload to your web root

Unzip it and upload the folder inside to your site root (your-project/public) via FTP without renaming it.

3️⃣

Verify from the panel

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

4️⃣

Create a schedule

Pick frequency, components and storage target. Backups run automatically and can be restored with the wizard when needed.

Highlights

What You Get with Laravel Backup

🔐

We never see your passwords

The module runs on your own server. Your database and FTP credentials are never sent to our panel.

☁️

Straight to your own cloud

Backups go directly to your own server, Google Drive, Amazon S3 and S3-compatible services, OneDrive, Yandex.Disk, Dropbox (max 150 MB per archive) or a Receiver Module; backup files are not stored on our servers.

⚡

Incremental transfers

Optional: only changed files, changed tables and new emails are transferred. How it works.

↩️

Wizard-based restore

Restore fully or partially with a 3-step wizard; when moving to another domain in your account, the database is mapped and connection settings are updated.

🦠

Malware scanning

Optional file and database scanning (detection only); in email backups, messages carrying malicious attachments are left out of the archive and reported.

🔒

Immutable copies

An unchangeable copy for the retention period you set, in an S3-compatible bucket with Object Lock enabled. Learn more.

Technical requirements for Laravel

The module needs PHP 7.1 or newer (8.1+ recommended) — virtually every Laravel installation qualifies. On the database side MySQL and MariaDB are supported: Laravel projects using MySQL or MariaDB are supported, and the module picks up the database connection from your project's .env file automatically. PostgreSQL, SQLite and SQL Server are not.

The module is installed as an independent folder in your web root. It does not touch Laravel core files and is not installed as a theme, plugin or extension — so Laravel updates never break your backups.

FAQ

Laravel Backup — Frequently Asked Questions

No. You add nothing to your project and change no code. The module is uploaded as an independent folder inside your web root, so your deployment pipeline and composer dependencies are untouched.
In Laravel the web root is usually the public directory, so the module must go under it (for example public/yedekalma) to be reachable from a browser. Placing it in the project root makes it inaccessible over the web. Locations outside public, such as storage/app or the project root that holds .env, are added to the backup from the “Extra folders” section of the module's settings screen.
No. The database component supports MySQL and MariaDB only. If you use PostgreSQL you can still use the file and email components and keep backing up the database with your own tooling.
Yes. You can define folders to exclude from backups. Excluding regenerable directories such as cache and build output noticeably reduces backup size.
Yes. Once the module is installed on the new server as well, you can remap the target database during restore. See our website migration page for the full process.

Protect Your Laravel Site Today

Try it free until the end of the year in the current campaign. No credit card, and nothing is charged automatically when the trial ends.

Create Free Account

See the four-step setup →