Magento support services keep a Magento 2 store secure, working and ready to change. In practice that means applying Adobe's security patches without breaking checkout, keeping third-party extensions compatible, fixing the bugs your team reports, and watching the parts of Magento that fail quietly: cron, indexers, queues and logs. We provide this as a monthly plan for merchants on Magento Open Source and Adobe Commerce, as part of our wider Magento development company work.
What you get is a named developer team that learns your store once and then looks after it every month, with a senior lead who decides what gets done first. You get a staging environment that mirrors production, a written patch history, a ticket log that shows where every hour went, and a monthly summary in plain English. If you have been relying on whoever is free when something breaks, this replaces that with a routine.
What Our Magento Support and Maintenance Services Cover
Every plan includes the same core routine. The higher plans add more developer hours, minor version upgrades and load testing before peak season.
| Item | What we do | What it means for you |
|---|---|---|
| Security patches | Apply Adobe's security releases and isolated patches on staging, run a regression check, then deploy to production | Your store is not sitting on known vulnerabilities, and checkout still works after the patch |
| Extension compatibility checks | Review each third-party module against the target Magento and PHP versions before any update | Fewer surprises where an extension update takes down the cart or the admin |
| Developer hours | Bug fixes, small features, content type changes, admin tweaks and configuration work from your request list | One place to send requests, with hours logged against each ticket |
| Health monitoring | Uptime checks, cron and indexer status, failed queue messages, exception and system logs, disk space | Problems such as stuck order emails or stale prices get caught before customers report them |
| Backup checks | Confirm database and media backups exist and run a restore test on staging on a set schedule | You know the backup actually works, not just that a job ran |
| Minor version upgrades | Moves between 2.4.x releases, including PHP, search engine and dependency changes (Care Plus and Pro) | You stay on a release Adobe still supports instead of facing a large, risky jump later |
| Pre-peak load test | Simulated traffic against staging before your busiest season, with fixes for the slowest pages (Care Pro) | You find the bottleneck in October rather than on Black Friday |
| Monthly report | Patch level, changes shipped, hours used, open risks and next month's plan | A clear record for your finance team and for any future developer |
How Our Magento Maintenance Services Start and Then Run Monthly
The first month is heavier than the rest because we have to learn the store. After that, the work settles into a predictable cycle.
- Takeover audit (week 1). We collect access, read composer.json and composer.lock, review custom code in app/code and the theme, list every third-party module with its version and vendor, and check the current patch level and PHP version. We also run Adobe's Security Scan Tool against the storefront. You get a short written risk list ranked by urgency.
- Environment and deployment setup (weeks 1 to 2). If there is no staging site, we build one with a sanitized copy of your data so customer details are not exposed. Code goes into a Git repository you own, and we document a repeatable deployment process so no one edits files directly on the live server.
- Baseline fixes (weeks 2 to 4). We clear the urgent items from the audit first: missing patches, broken cron, failed indexers, full disks, abandoned modules with known issues. These are usually the cause of the "random" problems your team has been living with.
- Monthly patch and change cycle. When Adobe publishes a security release, we apply it on staging, run our checkout and admin regression checklist, and deploy in a low-traffic window you approve. Your request tickets are worked through in priority order within your plan's hours.
- Monthly review. We send the report and hold a short call to agree the next month's priorities, flag anything that needs a larger quote, and note upcoming end-of-support dates for your Magento and PHP versions.
Magento Support Deliverables and What a Healthy Store Looks Like
We do not promise sales or rankings from maintenance. What we can show you are measurable signs that the store is being looked after properly:
- Current patch level, documented. Your store runs the latest security release for its 2.4.x line, or there is a written reason why not and a date for the fix.
- Clean scan results. No unresolved high-risk findings from the Security Scan Tool, and admin users reviewed for old accounts and missing two-factor authentication.
- Working background jobs. Cron runs on schedule, indexers are valid, and queue consumers process messages instead of piling them up.
- A tested restore. A recent backup has been restored to staging and confirmed to load.
- A module register. Every extension listed with version, purpose, license status and whether it is still maintained by its vendor.
- A ticket log. Each request with date, hours, what changed and which commit it lives in.
Magento Support Services Pricing
Magento support runs as a monthly plan with a fixed block of developer hours, so your cost is predictable and you can move between plans as your needs change. The main cost drivers are the number of hours you need, how much custom code and how many third-party modules the store carries, whether you want minor upgrades included, and how busy your peak season is. Large one-off projects, such as a major upgrade from an old release or a full Hyvä front end, are quoted separately.
Magento Care
$490 /month
Billed monthly
- Up to 8 hours of development
- Adobe security patches applied on staging, then live
- Extension compatibility checks
- Uptime, checkout and cron monitoring
- Backup checks and monthly report
- Response within 1 business day
- Minimum term
- 3 months, then month to month
- Setup
- $350 code and server audit
Magento Care Plus
$890 /month
Billed monthly
- Up to 16 hours of development
- Everything in Magento Care
- Minor 2.4.x version upgrades included
- Monthly performance review (Varnish, Redis, indexers, search)
- Response within 8 business hours
- Minimum term
- 3 months, then month to month
- Setup
- $350 code and server audit
Magento Care Pro
$1,690 /month
Billed monthly
- Up to 35 hours of development
- Everything in Magento Care Plus
- Pre-peak season load test
- 1 after-hours emergency fix a month
- Monthly call and CRO suggestions
- Same-day response on business days
- Minimum term
- 3 months, then month to month
- Add-on
- Extra hours: $45/hour. Hyva theme or major upgrade: quoted separately
All prices in USD. Need something different? Ask for a custom quote.
If your store needs more hours, a different mix or an emergency cleanup first, ask us for a custom Magento support quote.
Inside a Magento Patch Cycle: Why Updates Need a Developer
A Magento patch is not a one-click update. Adobe publishes security releases as versioned packages (the "-p" releases such as 2.4.7-p3) and occasionally as isolated patches for urgent issues. Applying one properly involves several steps, and each step can surface a problem that a store owner would not see coming:
- Updating the package with Composer, which may pull newer versions of dependencies that your custom modules rely on.
- Running
bin/magento setup:upgradeto apply database schema and data changes. - Recompiling dependency injection with
setup:di:compile, which is where incompatible plugins and type errors usually appear. - Deploying static content for each theme and locale, and flushing caches including Varnish.
- Reindexing and confirming cron and queue consumers restart cleanly.
- Testing the paths that make money: search, category pages, product options, cart, coupons, shipping rates, each payment method, order emails and the admin order grid.
Patches also interact with your PHP version and server stack. A release may require a newer PHP or a newer version of OpenSearch, so we check the server requirements before scheduling the work. That is why we never patch production first.
Adobe Magento support and your own developers
If you run Adobe Commerce, your license includes access to Adobe's support team for problems in the core product. Adobe support does not cover your custom code, your theme or third-party extensions, which is where most real-world issues live. We handle those parts and work alongside your Adobe support tickets when a problem crosses into the core, sharing logs and reproduction steps so tickets move faster.
Is Magento End of Life? Where Magento 2 Support Stands Today
No, Magento 2 is not end of life: Adobe still ships new 2.4.x releases and security patches for both Magento Open Source and Adobe Commerce. The confusion comes from Magento 1, which reached end of life on June 30, 2020 and no longer receives official security patches. Any store still on Magento 1 should treat migration as urgent.
What does end is support for individual minor releases. Adobe publishes a lifecycle policy with end-of-support dates for each 2.4 minor version, so a store that stays on an old minor release eventually stops receiving patches even though Magento itself is alive. Part of our job is tracking those dates for your store and planning upgrades before they arrive. There is also Mage-OS, a community-led distribution of Magento Open Source, which some merchants follow as an extra source of fixes.
Plenty of merchants still choose Magento, mostly mid-size and B2B businesses with complex catalogs, customer-specific pricing, several storefronts or deep ERP connections. For simpler stores, staying on Magento may not be the cheapest option, and we will say so.
Magento Support Agency, Freelancer or In-House Developer?
There are three common ways to cover Magento maintenance and support. Each has a place.
| Option | Works well when | Watch out for |
|---|---|---|
| In-house Magento developer | You ship features every week and the store is central to the business | One person holds all the knowledge; patching competes with feature work; holidays and turnover leave gaps |
| Freelancer | Your needs are occasional and you have a trusted person who knows the code | Availability during an outage, no second reviewer, and no staging or process unless you set it up |
| Magento support agency | You want a routine, documentation, a second pair of eyes on every change and cover when someone is away | Agencies that resell hours without learning your store; ask who will actually work on it |
Many of our clients combine options: an in-house developer handles features while we take patching, monitoring and upgrades off their plate.
Signs Your Store Needs Magento Technical Support Now
- The admin shows a version that is more than one security release behind, or nobody knows the current patch level.
- Order confirmation or shipping emails go out late or not at all, which usually points to cron or queue problems.
- Prices or stock on the storefront do not match the admin until someone manually reindexes.
- Saving a product in the admin takes a long time or times out.
- An extension update was rolled back because it broke something, and the vendor has since released several more versions.
- Your payment provider or a customer has reported suspicious card activity. Magento stores are a frequent target for card-skimming scripts injected into checkout, and this needs immediate attention.
- You are still on a PHP version that has reached end of life.
Magento Maintenance Tools We Work With
| Category | Tools |
|---|---|
| Platform and patching | Composer, bin/magento CLI, Magento Quality Patches Tool, n98-magerun2 |
| Security | Adobe Security Scan Tool, Sansec eComscan, admin two-factor authentication |
| Environments | Docker-based local setups, staging servers, Git, Adobe Commerce Cloud tooling where relevant |
| Monitoring and profiling | Uptime monitoring, New Relic, Blackfire, Magento system and exception logs |
| Stack | PHP, MySQL or MariaDB, OpenSearch, Varnish, Redis, RabbitMQ, Nginx |
| Load testing | k6 or Apache JMeter scripts against staging |
Why Merchants Choose 95 Solutions for Magento Website Support
- Senior-led. Mustafa leads strategy on every account, with 11+ years in digital marketing and a computer science degree, so priorities are set by someone who understands both the code and the revenue it supports.
- Merchant experience. He has been Head of Marketing for a Florida-based resort wear brand since 2016, so we treat peak season, promotions and checkout as the business-critical paths they are.
- Platform-neutral. We also work on Shopify, WooCommerce and BigCommerce, which means we can tell you honestly when Magento support costs more than the platform is worth to you.
- You keep control. Code lives in your repository, servers and Adobe accounts stay in your name, and every change is documented.
- Hours that fit. Our working hours cover the full US business day and overlap UK business hours, and contracts are in USD through our US LLC.
Who Our Magento Support Plans Fit, and Who They Do Not
A good fit if you:
- Run a Magento 2 or Adobe Commerce store that brings in meaningful revenue and cannot afford a broken checkout.
- Have no in-house developer, or have one who should be building features instead of patching.
- Inherited a store from an agency or freelancer who is no longer available.
- Want a documented, staged process instead of fixes made directly on production.
Probably not a fit if you:
- Need a 24/7 on-call operations team with guaranteed overnight response. That is better served by a managed hosting provider with its own operations staff.
- Are still on Magento 1. You need a migration project first, not a support plan.
- Run a small, simple catalog and want the lowest possible running cost. A hosted platform will likely cost less to keep running.
Related Magento and Ecommerce Services
When your request list includes new functionality rather than fixes, our Magento extension development team builds it as an upgrade-safe module. If you are weighing a move away from Magento, see our Shopify migration service. For stores on other platforms, our ecommerce website maintenance plans follow the same routine. Not sure where your store stands? Request a free audit and we will start with your patch level and extension list.