Nautvia

Getting started

Introduction

What Nautvia is, what it runs your Magento store on, and what it deliberately does not do yet.

Nautvia hosts Magento 2 and Mage-OS stores and deploys them from your git repository. You push to a branch; Nautvia fetches that commit, installs dependencies, compiles, and swaps the release in with a symlink. The store stays up while it happens — no maintenance mode.

It is built for merchants and agencies on Magento Open Source and Mage-OS — the ones Adobe Commerce Cloud prices out, and who would rather not run their own servers to escape it.

What you get

  • Managed infrastructure. An application server, MySQL, a Valkey cache and OpenSearch, provisioned for you. You never touch a provider console.
  • A Magento-aware deploy pipeline. setup:upgrade, di:compile and setup:static-content:deploy run in the right order, and the store only switches over once they have all succeeded. See The deploy pipeline.
  • Domains with automatic TLS. Certificates are issued and renewed for you. See Domains and SSL.
  • Daily database backups, restores that never overwrite your live data, and imports from your old host. See Backups and restores.
  • Shell access, live logs, one-off bin/magento commands and infrastructure metrics.
  • Support tickets in the dashboard, answered by the person who built the platform. A failed deploy has a Get help button that opens one with the deployment already attached.
  • Hourly billing for the infrastructure you actually run, on top of a fixed plan fee. See Plans and billing.

What it runs on

Everything is provisioned on Hetzner Cloud. You pick the location when you create a store — Germany, Finland, the United States or Singapore — and everything that store runs on is built there. There is currently one provider.

Servers run Ubuntu 24.04. PHP comes from the ondrej/php repository. MySQL is 8.0 or 8.4; the cache is Valkey 8 (Redis-compatible); search is OpenSearch 2.

What Nautvia does not do yet

Being clear about this saves you an evening:

  • One environment per site. Every site gets a single environment called production. There is no staging or preview environment yet.
  • No horizontal scaling. One application server per environment. You grow it by resizing, not by adding replicas. There is no load balancer and no CDN integration.
  • No bring-your-own-cloud. You cannot point Nautvia at your own AWS or DigitalOcean account.
  • Rollbacks restore code, never data. See Rollbacks.
  • Migrations are done by hand, together. That is a deliberate choice rather than a missing feature — see Migrating a store.

Where to start

If you are starting a store from scratch, go to Quickstart. If you have a store running somewhere else, read Migrating a store first — the order of operations matters, and doing it in the wrong order means downtime.