Service 05 / 05 · Recovery · all services
Production failing? The data secured first, then the cause fixed while you keep selling
When the shop, the CRM or the system your company runs on is failing: the data secured first, the cause measured on live production, small reversible fixes. The business keeps selling while it happens.
A system that crashes several times a day usually gets one of two answers: a bigger server, or a rewrite. Both are slow and neither starts with the cause. I start with the data: a full copy off the failing machine, with no maintenance mode, restored into a working clone so we know it is real. Then I measure on production, because a faster clone hides the bottleneck, and fix the cause with changes small enough to undo in one line. You get the system back, a written record of every change, and an honest list of what is still fragile. If a rebuild is the right next step, the report says so and prices it.
This is the right call when
- 01
Your shop or system goes down several times a week and nobody can say why.
- 02
The admin panel is so slow the team cannot do its daily work.
- 03
There is no backup you have ever restored, and the person who built it is gone.
What you get
What lands on your account
- A full off-site backup, restored and checked before any fix
- The root cause, measured and written down
- Fixes on production, each with a one-line rollback
- A report with before and after numbers, and what is still fragile
How it runs
Three steps. The six-step version, with the brief and the video request, is on the home page.
- 01
Scoping call
30 min, freeYou describe the situation; I ask three questions and propose a shape.
- 02
Audit: subscriptions or your own system
€1,200 / $1,400 net, 5 business daysThe 36-month cost comparison, the order of moves, the risks and a fixed build price. Paid by bank transfer after the call, once you accept the offer; credited in full against a build ordered within 60 days of the report.
- 03
Build, handoff, operate
fixed price from the auditOne engineer builds every layer on your account and documents it. The offer includes a monthly plan by default, so the system is looked after from launch day.
Case studies
The systems behind this service, with the numbers their owners cleared for publication.
Auto-parts shopAn e-commerce shop with ~100k products whose database crashed three times a day, stabilised on live production without planned downtime.
Backup first, proven by a restore; the cause was one missing index, found by measuring on production.
- 19.5 → 2.8
- server load
- 90 s → 1.3 s
- search
- −82%
- server errors a day
Runs on
Linux
Docker
Ansible
Cloudflare
Git
Claude
Questions I get about this
Tap a question to see the answer.
Scoping calls · most weeks
Usually the same or the next business day. The first hours go to read-only inspection and the off-site backup, so nothing changes on the system until there is a copy we have restored.
Server or hosting-panel access and the database credentials. Everything is inspected read-only first; secrets stay out of the repository, and I list what should be rotated when the work is done.
Every change has a backup and a one-line rollback written before it goes in, is tried on a restored clone first, and is measured on production afterwards. If a change does not help, it comes out.
The system keeps running on Cloudflare with no servers to babysit. You can operate it yourself, keep me on for changes, or hand it to another engineer with the docs I leave behind.
Something else? Ask it on the call
A 30-minute call, free
Thirty minutes, then an offer for the audit
Pick a free time in my calendar. Or leave an email: I reply within one business day with three questions and a proposed time for the call, not a deck.