LeoCore Backup · Verified database backup
Database backup that proves it worked.
Scheduled, encrypted backups for SQL Server, MySQL, MariaDB, PostgreSQL and Firebird, running as a Windows service on your own hardware. Every archive is re-read, checksummed and test-restored — so the first time you find out a backup is good is not the day you need it.
5 database engines 13 storage destinations Perpetual licence from $89 No telemetry, no account required
The problem
A backup nobody has restored is a rumour.
Almost every backup tool tells you a job succeeded. That means the file was written. It does not mean the dump is complete, that the archive opens, that the chain is intact, or that the database comes back. Those are different claims, and only one of them matters at 3am.
How it proves it
Four layers between “job succeeded” and “you can restore”.
The archive is re-read
SHA-256 integrity check and a full re-read after writing, validating the CRC and the AES authentication tag on every entry. Included in every edition, free one as well.
The engine agrees
Engine-level verification — RESTORE VERIFYONLY on SQL Server,
pg_restore --list on PostgreSQL — plus a check of the engine’s own
trailer to confirm the dump actually finished.
It is restored, on a timetable
Automated restore drills bring the archive back into a scratch database on a schedule, run your own validation query against it, drop it and email the result. Proof of recoverability without a human remembering to check.
Every restore point is rated
Verified, proven by a drill, or suspect. Not a green tick that means the file exists — a status derived from what was actually tested.
A recovery kit
Written beside every archive: every database name and its constituent files, the restoration sequence, SHA-256 hashes, all copy locations, and the exact restore commands for that engine. It plainly states that it holds no password.
LeoCore Rescue — free
A standalone executable with no installer, no service and no .NET requirement. It reads a folder of archives that has no catalogue at all, and recovers the archive password from the machine that made the backups. Keep a copy in your storage beside the archives.
Ransomware
The backup is the target. Treat it like one.
Modern ransomware finds the backup share first and encrypts it before touching production, because that is what forces payment. Three defences, all in Datacenter.
Immutable storage
S3 Object Lock in governance or compliance mode, and Azure immutable blobs with time-based retention. An object cannot be overwritten or deleted until its retention expires — not by you, and not by anything running as you.
Append-only credentials
The backup job holds create-only permissions. Deletion happens through a separate restricted identity, so a compromised backup service account cannot erase history.
It notices mass deletion
Each backup is compared with the one before it. When a table is emptied, dropped, or loses most of its rows, you are told — and the copy taken beforehand is held back from retention rather than ageing out.
What it backs up, and where to
Five engines. Thirteen destinations.
Database engines
- SQL Server 2012–2022, Express, and Azure SQL Database
- MySQL 5.7 and 8.x
- MariaDB all versions
- PostgreSQL 10–16
- Firebird 2.5–5.0
- Managed cloud — Amazon RDS, Aurora, Azure SQL
Storage destinations
- Local folder and network share
- Amazon S3 and S3-compatible — Wasabi, MinIO
- Backblaze B2, Azure Blob Storage
- Google Drive, Dropbox, OneDrive, OneDrive for Business, Box, Yandex.Disk
- FTP, FTPS and SFTP
Full, differential, log
Differential and transaction-log backups on SQL Server, MySQL, PostgreSQL and MariaDB, with point-in-time recovery resolving the full → differential → log chain and validating LSN continuity before it starts.
Retention that understands chains
Keep-last-N and minimum retention age, with GFS retention in Datacenter. It never deletes a full backup that a differential or log still depends on.
More than the data
On SQL Server it scripts logins with their SIDs so users are not orphaned on restore, plus server role membership, linked servers and Agent jobs.
Runs unattended
A Windows service, signed out, across reboots, on Server Core, under a gMSA. Hourly minimum frequency with run windows, weekday and monthly rules; late slots run within 30 minutes, missed slots are skipped.
Checked in daylight
Connection, permissions and every destination are tested during the day rather than at 2am. It also finds databases nobody is protecting — while knowing that tempdb and master are not oversights.
Tells you properly
Email on failure or every run, Windows Event Log, and Slack, Teams or JSON
webhooks — one POST per run outcome. A CLI with --json and exit codes
for your own automation. On failure, the complete error, not a code.
Recovery time, measured
Not estimated. Recovery time comes from actual drills, and exposure is read from the newest archive that genuinely exists — an hourly job whose last stored copy is Tuesday reports four days, loudly.
Audit report, one button
Dated, against the controls in ISO 27001, NIS2, SOC 2, HIPAA and DORA. Nothing is asserted — every status is derived from records, and failures stay in. Datacenter.
The estate on one screen
Twelve servers, no console to install and nothing hosted. Every edition publishes its status; the Datacenter console reads them all over a plain file share you already own.
Pricing
One payment. Per server. For ever.
Perpetual licence, lifetime updates available, 14-day money-back guarantee. Restore is never gated by a licence — in every edition, for any archive, for ever.
- 2 databases, 2 jobs
- All five engines
- Hourly scheduling with run windows
- Local, network share and OneDrive
- AES-256 encryption, SHA-256 verification
- Unrestricted restore, for ever
- Commercial use allowed, no ads, no telemetry
- Runs at sign-in, not as a service
- Unlimited databases and jobs
- Full and differential backups
- All 13 destinations, 3 per job
- Windows service — signed out, Server Core
- Email alerts, webhooks, Event Log
- CLI with pre/post-run commands
- Email support, 2 business days
- No transaction-log backups or restore drills
- Everything in Server, plus:
- Automated restore drills and engine-level verification
- Point-in-time restore with full chain resolution
- Immutable storage and Object Lock
- Transaction-log backups, GFS retention
- The estate view across all machines
- Azure SQL, Amazon RDS and Aurora
- SSH tunnels, bandwidth throttling, unlimited destinations
- Priority support, 1 business day
Volume licensing — Datacenter
| Servers | Total | Per server |
|---|---|---|
| 1 | $199 | $199 |
| 3 | $499 | $166 |
| 10 | $1,290 | $129 |
| Site licence, up to 25 | $2,990 | $120 |
Prices in USD, exclusive of tax. Payment taken by Paddle, our Merchant of Record.
Our commitment
Your backups do not depend on us continuing to exist.
What if LeoCore disappears tomorrow?
Your archives are standard Zip64 with AES-256 — 7-Zip opens them on any machine with the password. The recovery kit beside each archive holds the exact restore commands and hashes. LeoCore Rescue is a free standalone executable that reads a folder of archives with no catalogue at all. Nothing in the restore path needs us, a server, or a licence.
Is restore ever gated by the licence?
Never, in any edition, for any archive, for ever. That includes an expired licence, a lapsed renewal and the free Solo edition. Holding a customer’s data hostage to a renewal is not a business model we are interested in.
Does it phone home?
No telemetry, no analytics, and no account required to back up. Credentials are sealed with Windows DPAPI, bound to the machine, and never leave it. Offline activation is available for air-gapped networks — copy the machine fingerprint, paste it into a form, receive a signed licence, and the application never needs the internet again.
How do updates work?
Self-installing. It fetches the installer and verifies its SHA-256 against the published release before running it, rolls back automatically on failure, and never touches jobs, schedules, credentials or history.
Find out tonight, not at 3am.
Solo is free for ever on two databases, with full encryption, verification and unrestricted restore. Point it at a real database and let it prove itself.