Maho Cloud - Your store, our servers.

The official cloud for Maho Commerce, built and run by the team that makes Maho. Connect your Git repository, pick a plan and a region, and get a dedicated server on the safest, most modern stack for a Maho store. It deploys, backs up and watches itself. Nobody knows Maho better.

Create your account See how it works View pricing

Deploy from Git

A repository and a branch. We provision the server, build the Docker image, issue the certificate and deploy. Every run is logged, live.

Operations on autopilot

Nightly snapshots and offsite backups, verified each morning. Uptime, SSL, DNS and disk checks. OS patches in your window. Maho cron and reindex.

Infrastructure as code

Dockerfile, compose file, php.ini, deploy script and env vars, versioned and applied by deploy. Same files, same server, on every rebuild.

Dedicated servers in the EU

One Hetzner Cloud server per store on Arm vCPUs, in Falkenstein or Helsinki. Resize in place. Private networks between stores. Database ports never public.

From repository to live store

Three steps. You bring a Git repository that builds. We bring everything under it.

Create Your Store

Enter the domain, the Git repository and the branch. Choose the PHP version and the database engine at the same time.

Pick a Plan and a Region

Choose the plan and the data centre closest to your customers. Checkout runs through Stripe, and you can change plan later without migrating.

We Build and Ship It

The server is provisioned, your image is built, the certificate is issued, cron is installed and monitoring starts. The whole run streams into the deployment console, live.

Migrating from another host? Put the new store behind HTTP basic auth while you import data and test it. Point DNS across when you are ready. The old site keeps serving until you do.

By the Maho team, on the stack Maho was made for

Features Monitoring Agencies Pricing

Fully managed, fully yours

We write Maho, so we know what a Maho server needs: the safest, most modern and most current stack there is for it. We run the server, the certificates, the OS updates, cron and the backups. You keep every file that shapes your stack, editable from the dashboard.

Deploys That Know Maho

Every deploy runs your migrations, flushes the cache and starts the catalog reindex on its own. The reindex is detached, so a large catalog never holds up the deploy, and we follow it to the end and email you if it fails. Maho cron runs every five minutes from the first boot.

Deploy on Your Terms

Connect a repository and a branch. We handle the deploy key, the build and the rollout, and keep the full log of every deployment. Deploys start when you press Deploy, not on every push.

One Store, Many Domains

Point several domains at one store and choose which storefront or website scope each one opens. Leave it blank and the domain serves your default store, exactly as Maho does on its own.

Your Config, Your Rules

The Dockerfile, docker-compose.yml, php.ini, deploy script and environment variables are all editable from the dashboard, with defaults generated for your stack and plan. Every deployment keeps the exact configuration it ran with, so you can see what changed when something breaks.

Live Logs

Container logs and your store's own var/log files, streamed to the browser as they are written. Deployments get their own console, and the reindex that follows keeps streaming into it.

Backups You Can Trust

Daily server snapshots with one-click restore, plus a nightly copy of your database and files to offsite storage. All three are checked every morning for age, and the newest database dump is decompressed to prove it reads. Download a dump from the dashboard at any time.

Safe by Default

Security patches land on the OS automatically. Every response carries the security headers scanners ask for, every domain gets a Let's Encrypt certificate, and database ports are never published to the internet. A store you have not launched yet can sit behind HTTP basic auth.

SSH When You Need It

Git is the normal way in: work locally, push, deploy. When that is not enough, add a public key and get a shell inside your running application, with SFTP and rsync over the same key. Port 22 stays closed until you add a key, and closes again when you revoke the last one. For a supplier or a script that only uploads, create an SFTP user with a password or a key, locked to one folder.

The Most Modern Stack There Is

FrankenPHP on PHP 8.2 to 8.5, in Docker, with MySQL, MariaDB, PostgreSQL or SQLite on their current major release, on Arm vCPUs. Everything is pinned, so a rebuild never changes your stack behind your back, and you move to the next PHP with one setting and a redeploy.

Resize Without Migrating

Move between plans and the same server is resized: your IP address, your data and your domain stay put. The server restarts to do it, so expect a short interruption. CPU and memory change, the disk keeps its size, which is what keeps a downgrade possible later.

Continuous monitoring

Uptime, every 5 minutes
TLS expiry, 14 days ahead
DNS, daily
Disk space, alerts at 75% and 90%
Backups, every morning
OS security updates, daily

Built for agencies, too

Build the store on your account, hand it to the client when it is ready, and keep exactly the access you need afterwards.

Hand Over to Clients

Build on your own account, then transfer ownership by email. The store appears on your client's dashboard straight away and they take over billing from there. No account yet? The transfer completes when they register and confirm their address.

Access That Fits the Job

Invite collaborators with the right to deploy, to read logs, or both. Server configuration, billing and deletion stay with the owner. Developers work locally, push to Git, and press Deploy.

Private Networks

Connect stores over a private network so they reach each other internally. Database ports bind to the private interface and are never published to the internet.

Full Activity Log

Every provision, deployment, key change, plan change, reboot and restore is recorded against the store, with its status and the time it ran. Searchable and filterable across all your stores.

Resell Maho Cloud. Host your clients' stores under your own brand, on your own servers. How it works

Choose your region

Two Hetzner Cloud data centres in the EU, chosen per store when you create it. Your data stays where you put it.

Europe

Falkenstein, Germany · Helsinki, Finland

20 TB traffic included

Operational

Need a region that is not listed? Tell us where and we add capacity based on what customers ask for.

Simple pricing

One price per store, billed monthly or yearly. No setup fee, no add-ons, every feature on every plan.

Starter

For a new store or a small catalog

€39 /mo

per store

2 Arm vCPUs
4 GB RAM
40 GB SSD
20 TB Traffic
Fully Dockerized Infrastructure
FrankenPHP + MySQL / MariaDB / PostgreSQL / SQLite
Auto SSL via Let's Encrypt
Daily Backups + Offsite Copies
Uptime, TLS, DNS & Disk Monitoring
Live Log Streaming
Full Deployment Control
Team Access & Handover
SSH Into Your Container

Get started

Ready to launch your store?

Official Maho hosting, from the team that builds it. Connect your repository, pick a plan and a region, and watch the first deploy run.

Create your account See the plans What is Maho?