Total outage
Your shop only shows a white page or 500 errors. No frontend, no backend — nothing works anymore.
Your shop is down, the checkout is throwing errors or a plugin is blocking everything? In a crisis you do not need a meeting, you need a senior developer who finds and fixes the problem. Immediately.
These four scenarios are classic emergencies. If one of them applies to you — use the quick triage or call directly. I will prioritise your shop immediately.
Your shop only shows a white page or 500 errors. No frontend, no backend — nothing works anymore.
Customers can no longer pay or order. A direct revenue killer — every hour counts double.
A Shopware or plugin update has wrecked the system. Features gone, layout broken, backend dead.
Your server collapses during the sale. Loading times explode, orders fail, database at its limit.
In an emergency, the last thing you need is yet another person who keeps you waiting hours for a response. Here is the process I follow — no theatrics.
Send me an emergency email or call directly. URL, a short description and your number are all I need to take over immediately.
I need SSH/FTP and, if available, Tideways access. With profiling and logs I find the cause in minutes, not hours.
I isolate the problem and bring the shop back online. Cleanly, without opening up new construction sites — and without should-be-fine patches.
Once the fire is out, we analyse how to rule out this error for the future. Monitoring, tests, processes — whatever is needed.
So there is no discussion about the invoice after the emergency — here are the terms, in black and white.
| Period | Hourly rate |
|---|---|
| Weekdays | 180 h |
| Evenings & Saturdays | 250 h |
| Nights, Sundays & public holidays | 350 h |
Outside office hours and at weekends it may take longer — but I will get back to you.
Other appointments get postponed as soon as your emergency comes in. That is what the express rate is for.
live in actionI know Shopware down to the core. With tools like Tideways and Sentry I find error sources where others are still guessing — because I have used performance profiling as a daily tool for years, not as a buzzword.
6+ years of Shopware — lead developer on critical migrations and live systems
Profiling first — Tideways & Sentry are open on my screen daily, not just in emergencies
No contract needed — you do not have to be a customer first. An emergency is an emergency.
Plain language instead of tickets — I explain what was broken and how I fixed it. In sentences you understand.
An email can wait. A call cannot. I answer the phone as soon as I can — and if I cannot, I call back.