PCI-DSS & GDPR
Support Contact sales
View Pricing
synopmage

synsmarts for OpenMage

OpenMage Hosting That Knows Before You Do.

A fatal after an extension update, a cron run that fails, a checkout that errors, a category page that drags. synopmage catches it, traces it through the front controller, the block, and the query, and sends back the file, the line, and the patch before your customers notice. Built by the team that ran MageMojo from 2009 to 2021.

Get a Free Diagnostic Get Started

Built for the Way OpenMage Runs.

OpenMage LTS 20.x keeps a Magento 1 store current on modern PHP. synopmage builds your whole store tree into an image, runs its setup scripts before traffic moves, and keeps the previous release serving until the new one is ready.

  1. Modern PHP, Your Pick

    PHP 8.2, 8.3, or 8.4, chosen when you buy. 8.3 is the default, the line OpenMage runs cleanest on.

  2. Your Build, Your Way

    Git push or a prepared Workspace. With a composer.lock the build runs Composer; without one it ships your tree as it is.

  3. Setup Scripts Before Traffic

    A release Job applies pending setup and data scripts once on the new image while the old release keeps serving. A failed script fails the deploy.

  4. Cron That Reports Back

    Default and always cron modes run as two Scheduled Jobs, every minute, never overlapping, each exit status in the job history.

  5. A Release Never Reads Stale Config

    Cache and sessions sit on their own Redis roles. The cache prefix changes with each release; sessions carry across every PHP pod.

OpenMage problems, found and fixed, without a ticket from you.

synopmage watches every request and reads your code alongside it. When something breaks you get the report, not the job of finding out.

  1. A fatal after an extension update

    The report names the extension, the file and line, and hands you the patch. No reading var/report at midnight.

  2. A cron run that fails

    Indexers stale, newsletters not sending, nobody noticed. Every run of both cron modes is recorded, and a failing one comes back with why.

  3. A checkout that errors

    The trace shows the observer and the query that failed. No trying to reproduce it, no waiting for the next customer to hit it.

  4. A category page that drags

    Traced through the front controller, each block, and the MySQL and Redis calls beneath them, to the line. No dashboard that shows a symptom.

  5. A bad UPDATE on the catalog

    Your own MySQL with hourly backups and binlog shipping. Rewind to any minute of the last 14 days.

An incident on a Magento store running on synsmarts, caught, patched, and applied the same morning. Store name withheld.

Critical checkout c41d7b2e · 2026-09-02 · 09:14 UTC

Checkout failing after a module update

Every order attempt since the 09:11 deploy of acme-discounts 3.2.0 ended in a fatal at the cart total.

Details

acme-discounts 3.2.0 calls a method the store's cart no longer exposes. The trace shows the fatal at class-cart-hook.php:88 on every checkout request since the deploy; the patch calls the method that exists and keeps the discount logic intact.

Measured impact

Checkout requests ending in a fatal. Seven minutes from the first error to the fix live.

Before
100%
After
0%
Reduction
100%

Patch

app/code/Acme/Discounts/Hook/class-cart-hook.php +1 −1
@@
1 $totals = $cart->get_totals_v2();
1 $totals = $cart->get_totals();
Approve and apply Download patch

Approved at 09:16, applied by the platform at 09:17, checkout verified clean at 09:18. Checked at each deploy since.

Get a free diagnostic of your store

Moving From Another Magento 1 or OpenMage Host.

Your store moves as it is. Same code, same database, same extensions, migrated free with us doing the work, and your live store stays open while we do it. If you were with us at MageMojo, this is the team you remember, on the platform we always wanted to build.

How the move works
Get a Free Diagnostic Get Started With synopmage

$187.50 / mo starting

Grow when you're ready.