Magento rescue and maintenance
Older Magento 2 stores, abandoned builds, custom installations nobody maintains anymore. We stabilize first and modernize only where it pays.
Store down right now
If checkout is broken, you are being charged for a bug, or a patch window closed while nobody had access: use either line below, or send the store URL by email. Both numbers belong to the firm that does the work.
Mon–Fri, 09:00–18:00 Riga time (EET/EEST).
Written, if that is easier: info@magentohub.com.
How a store ends up here
Somebody built it.
A Magento 2 store, a Hyvä or Luma theme, a pile of modules, an integrator who left.
Then they left.
The handover notes are stale, the last patch is from 2023, the cron runs when it feels like it.
The store still earns.
The money is real, so a rebuild is a risk nobody wants to price.
We take the middle road.
Stabilize, secure, then modernize in phases, only where the payback is obvious.
Signs it is time
Any one of these is worth an audit. Tick the ones that match your store and the count becomes the agenda for the audit.
The first four weeks
Access and inventory
repository, server, database, who holds the credentials · week 1
week 1
Stabilize
patches, backups that restore, cron and indexers under control · week 1–2
week 1–2
Evidence
the audit report, same format as the free audit · week 2–3
week 2–3
Estimate
hours and a total for each finding, in priority order, nothing started · week 3
week 3
Keeping
patched as soon as it publishes, monitoring, one contact · after that
after that
€90 an hour, two hour minimum, estimate first.
We reply with hours and a total before we touch anything. You approve the hours, not a package. The same rate for a two hour fix and for a two hundred hour upgrade; it does not go up because the store is on fire, and there is no retainer to buy, no hour bank and no minimum term.
The estimate arrives in writing before a single hour is booked: every finding with its hours and the total in euros, ranked, and you fund the ones you choose. If a finding turns out smaller than estimated, we invoice the smaller number.
What the store looks like from the outside
AlkOutlet.lv, kept since 2024: the home page at phone width, the way a phone visitor is served it, then the whisky category and the product page, both as captured. The sheet in the last row is the public sample report, not this client's.

Sample Audit Report: Hyvä Store With 3,400 SKUs
Sample Score: 58/100. Three Selected Findings Shown.
- F-01Magento security patches missing (latest 2.4.5-p3)Critical4h
- F-02Mobile checkout LCP 5.1s, Apple Pay and coupon flow blockedCritical16h
- F-04robots.txt blocks GPTBot, ClaudeBot, PerplexityBot unintentionallyCritical1h
Three of the sample audit's sixteen findings, in the shape the report arrives in.

The sample report’s findings are invisible from the admin, and so were this account’s two heaviest jobs — the ERP stock sync and the checkout itself, twenty hours between them.

Questions before the handover
The audit is free and external. Rescue starts when you approve the estimate, not before.
Magento 2.2 and up, and Adobe Commerce. For 1.9 the honest answer is a migration plan; we write that plan and we do not pretend a rewrite is cheap.
The audit itself needs no access: it reads the store from outside. A rescue does — read-only admin and SFTP to start, then whatever the work needs. We record what we touch.
You do. Commits go into your repository, your branch, your review process.
Yes, that is the white-label shape, even when the agency is not the one paying.
Yes. Stabilizing comes before the report, and we tell you which findings can wait and which cannot.
No Magento 1 feature work, we do not sell hosting, and we will not propose a re-platform we cannot defend on cost.
Monday to Friday, 09:00–18:00 Riga time (EET/EEST).