Service / Magento
Magento support for stores that lose money when they’re down.
Magento 2 and Adobe Commerce, looked after by senior engineers. Security patches, version upgrades, module conflicts, speed and hosting. We rehearse the work on staging first, then run it on your live store without closing the doors.
Symptoms
What people call us about.
- The upgrade has been put off for a year because nobody wants to be the one who runs it
- Cron died quietly and took your order emails, feeds and reindexing with it
- Indexers have been sitting in “processing” for days
- Every security patch breaks a module, and someone has to babysit the release
- Pages still take 5+ seconds with full-page cache turned on
- Your agency answers every bug report with a replatform quote
What we do
We read the cron table before we open a ticket.
Magento problems almost never show up where they start. A “slow site” is usually a stuck indexer or a cache that never warmed. Missing order emails are a dead cron. A checkout that broke right after a patch is normally two modules rewriting the same layout or fighting over the same plugin chain. So before we change anything, we read cron_schedule, indexer state, the composer tree and Elasticsearch health. Then we fix the cause. The symptom goes away on its own.
Keep it current
- Security patches rehearsed on staging, then shipped
- Version upgrades planned against a module-compatibility matrix
- Composer tree & extension audits
- Backups we’ve restored, and a rollback we’ve actually run
When it breaks
- Dead cron jobs & indexers stuck mid-run
- Finding which module a patch fell out with
- Checkout, payment gateway & admin errors
- A written root cause, not another patch on a patch
Make it quick again
- Full-page cache & Varnish tuned to your traffic
- Elasticsearch / OpenSearch sizing & health checks
- Database, indexer & cron schedule cleanup
- Hosting review, and a plan for getting off M1
From the field
A B2B store went down in the middle of an upgrade and stayed down. Two restore attempts failed. The call reached us on day two of the outage.
The upgrade had been run straight against production with two third-party modules that were never compatible. The “backup” was a file copy taken after schema migrations had already run, so every restore put the broken state back.
A clean rollback from a verified pre-upgrade snapshot ended a four-day outage. The upgrade itself ran again weeks later: rehearsed on staging, checked against a module-compatibility matrix, and finished with zero downtime.
Questions
What store owners ask us about Magento support.
What does Magento support cost?
Ongoing support starts at $595/month (Monitor). Dedicated engineering capacity is $1,950/month. If you just need one fire put out, one-off emergencies start at $500 per incident, quoted at a fixed price after a free diagnosis. The full plans are here.
Can you rescue a failed upgrade?
Usually, yes. First job is getting production stable: a clean rollback if there’s a verified restore point, a forward fix if there isn’t. Once you’re trading again, we re-plan the upgrade properly. Staging rehearsal, a module-compatibility matrix, and a rollback someone has actually tested.
Do you still support Magento 1?
Only to get you off it. Magento 1 is past end-of-life, which means no security patches and PCI exposure that grows every month, so we don’t keep M1 stores running long-term. We do plan and execute M1 to Magento 2 migrations, data included.
How fast can you make our store?
We measure before we answer that. Most slow Magento stores we open up are losing whole seconds to cold caches, broken indexers, bloated layouts or a search cluster that’s too small for the catalogue. None of that needs a rebuild. We put numbers on it after profiling, not before.
Do we have to replatform?
Usually not. Replatforming is the right call for a business reason, not for a bug backlog. A Magento 2 store with healthy cron, working indexers and hosting that fits your traffic is a perfectly good place to sell from. Fixing it costs a fraction of rebuilding it.
Related
Free triage
Tell us what your store is doing wrong.
Describe the symptoms in your own words. A senior Magento engineer reads them and replies within two hours with a first take. It’s free, and you’re not committing to anything.