Applications
Sites and environments
How sites, environments and the servers behind them fit together, and what stopping or tearing down actually does.
A site is a Magento store and the repository it deploys from. An environment is a running copy of that site: its servers, its database, its domains, its deploy history.
Every site has exactly one environment, called production. It is created with the site. There is no way to add a second one yet — no staging, no per-pull-request preview environments.
Creating a site
Sites → Create site walks through three steps: connect a git provider if the team has none, pick a repository, then set the name and branch.
The repository list shows the 100 most recently active repositories you have access to, filtered as you type. If yours is missing because you have more than that, the fastest fix is to push to it — the list is sorted by last activity.
Your plan limits how many sites a team can have: 1 on Solo, 5 on Studio, unlimited on Agency. See Plans and billing.
The environment page
The header carries the state of the whole environment: status, repository:branch, and the actions — Visit, admin credentials, SSH details, Start/Stop, Tear down and Deploy.
The tabs:
| Tab | What is there |
|---|---|
| Overview | Servers, attached resources, domains, storage |
| Deployments | History and live logs — the deploy pipeline |
| Commands | One-off bin/magento runs — commands |
| Backups | Daily and manual backups, imports, restores |
| Logs | Live tail of nginx, PHP-FPM and Magento logs |
| Metrics | CPU, memory, disk and network |
| Settings | PHP version, server size, environment variables, deploy commands, deploy hook, danger zone |
Nothing exists until you deploy
Creating a site provisions nothing and costs nothing. Servers are created during your first deploy, and metering starts when they start running. This is also why the Deploy button is disabled until a database, a cache and a search cluster are attached.
Stopping an environment
Stop powers off the application server and every resource server used only by this environment. The machines keep their disks and their IP addresses, and starting them again brings the same store back.
Stopped servers are not billed by Nautvia — metering counts running servers only.
Tearing down
Tear down destroys the servers. It is the way to stop paying for an environment you are not using, and it is not reversible.
What it destroys: the application server and any resource servers only this environment uses, along with their disks, the TLS certificates and the nginx configuration.
What survives: your media volume (it is re-attached on the next deploy), your database backups in object storage, your domains, your environment variables and your deploy history.
Your IP address changes. The next deploy builds a new server with a new address. Nautvia's own temporary hostname follows automatically; your custom domain does not — you have to update its A record yourself. See Domains and SSL.
After a teardown the next deploy is a fresh Magento installation against your existing database — the store's data is in MySQL, not on the server's disk.
Deleting a site
Settings → Danger zone → Delete site removes everything: servers, the media volume, DNS records, the repository webhook and all history. Team-level resources — database clusters, caches, search clusters — survive, because another environment may be using them.
Neither teardown nor deletion is possible while a deployment is running.