Magento 2 · Mage-OS

Ship Magento without the drama.

Managed hosting and a Magento-aware deploy pipeline. Push to your branch — we build the release on a separate machine, run the upgrade and swap it in atomically. No maintenance mode, and one click back to the last good release.

First month of Solo free · billed by the hour · cancel any time

Why this exists

Magento deploys are stuck in 2015.

Not because the platform cannot do better — because the hosting around it never caught up with how the rest of the web ships software.

Every release is an outage

Maintenance mode goes up, static content compiles on the live box, and customers watch a holding page while you hope nothing breaks.

The pipeline eats the evening

Composer resolution, di:compile, static-content:deploy, setup:upgrade — hand-run in the right order, on the right PHP version, every single time.

Enterprise hosting is sold by the year

The managed option for a Magento store is a $40,000–$300,000 annual contract with a sales cycle attached. Most mid-market stores are not that store.

How it works

Three phases, and only the last one touches your store.

The build happens away from production. Your store only changes when a symlink moves — which takes milliseconds and is reversible.

Your dependencies, your versions

PHP 8.3 or 8.4 per environment, MySQL 8.0 or 8.4, and the composer install that matches the commit you pushed.

Media survives every release

pub/media lives on a dedicated volume mounted into the release. Grow it whenever the catalogue does.

A failed build never reaches production

If composer or di:compile fails, the deployment stops and the live release stays exactly where it was.

The pipeline

Watch a release go out.

deploy log
$ git push origin main→ build.running composer install --no-dev→ build.running bin/magento setup:di:compile→ build.running bin/magento setup:static-content:deploy→ deployment.running setup:upgrade→ deployment.running release swapped✓ live in 4m 12s — no maintenance mode
git push origin main
Build
  • composer install
  • setup:di:compile
  • setup:static-content:deploy

On a build machine. Your store keeps serving traffic.

Release
  • upload release
  • link shared media
  • setup:upgrade

The new release is assembled beside the live one.

Swap
  • atomic symlink swap
  • reload php-fpm
  • warm caches

One symlink moves. No maintenance mode, no downtime.

LivePrevious release stays on disk — roll back in one click.
Resources

Database, cache and search — provisioned and connected.

Each runs on its own machine rather than sharing one box, and the release phase writes the connection details into env.php for you. There is no config to hand-edit.

What you get

Everything a Magento store needs, already wired together.

Push to deploy

Connect GitHub or GitLab. Every push to the tracked branch builds and releases.

One-click rollback

The previous release stays on disk. The guard refuses swaps across PHP versions.

Managed MySQL

8.0 or 8.4 on its own machine, with logical databases and an optional public endpoint.

Redis-compatible cache

Sessions and cache on a dedicated Valkey node, written into env.php by the release.

OpenSearch

Catalogue search on its own node, with a heap tuned to the machine it runs on.

Domains and SSL

Point the DNS record and the certificate is issued and renewed for you.

Backups and restores

Nightly database backups to download, restore, or replace with an import.

Metrics and logs

CPU, memory, disk and network per machine, with deployment and application logs.

Commands and SSH

Run bin/magento from the dashboard, or open a shell in the release directory.

Billed by the hour

Resize before a sale and drop back after. Stopped machines cost nothing.

Told when it matters

Failed deploys, failed backups and payment problems reach you by email.

Team access

Invite developers with their own logins and SSH keys. One invoice per team.

Pricing

A plan for the platform, plus what your infrastructure actually costs.

Three plans from a single store to an agency's whole book. Infrastructure is the same hourly price on every one — no contracts, and no charge for machines you stopped.

Plans from$9.00/month
A typical store, all in$97.77/month
See the full price list
Moving in

We move your store across with you.

Migrations are done together, by hand, with the person who built this platform. Not a support ticket, and not a wizard that half works.

Your current host keeps serving until the cutover. If something looks wrong, nothing has moved yet.

1Import your existing database dump into the new environment
2Sync pub/media onto a dedicated volume
3Deploy the real branch and test on a temporary hostname
4Point DNS when you are satisfied — the certificate issues automatically

Put your next release on a pipeline instead of an evening.

Start on Solo and deploy a store today — the plan fee is free for your first month, and you only pay for the hours your infrastructure actually runs.