Account
Plans and billing
What the plan fee buys, what is metered by the hour, and how to stop paying for something you are not using.
Your bill has two parts: a fixed monthly plan fee, and infrastructure metered by the hour.
The plan fee buys limits and features. The metered part is the servers, volumes and backup storage you actually run — the same figures the pricing page publishes, and the same ones your dashboard shows.
The plans
| Solo | Studio | Agency | |
|---|---|---|---|
| Sites | 1 | 5 | Unlimited |
| Team members (excluding owner) | 0 | 4 | Unlimited |
| Deployment history | 10 | 50 | Unlimited |
| Daily backup retention | 7 days | 14 days | 30 days |
| Metrics lookback | 1 day | 7 days | 7 days |
Solo's first month of the plan fee is free. Infrastructure is metered from the first hour it exists, including during that month — those machines cost money the moment they are created.
What is metered
Hourly, at the rates on the pricing page:
- Servers, by size. Application, database, cache and search are each metered separately.
- Media volumes, by provisioned size — a reserved disk, not the space used.
- Backup storage, by total size held.
A month is counted as 730 hours.
Only running servers are metered. Stopping an environment stops its server charges immediately. Volumes and backups keep being billed while they exist, because they still occupy storage.
To stop paying for an environment entirely, tear it down. Stopping pauses the server bill; tearing down ends it.
Reading your usage
The dashboard shows the current hourly rate, a monthly estimate, and a 30-day spend chart built from what was actually metered — not an extrapolation. The billing page carries your invoices.
Usage is reported hourly. A server created at 14:50 and destroyed at 15:10 is metered for the hours it was running.
Payments and tax
Payments are processed by Stripe, which acts as merchant of record and issues your invoices. Prices exclude tax; Stripe calculates and collects VAT or sales tax from your billing details. Add a VAT number there and it appears on the invoice.
Card details are entered directly with Stripe. Nautvia stores only the brand and last four digits.
Changing plan
Billing → change plan. Upgrades take effect immediately and Stripe prorates the difference. Downgrades apply the same way.
A downgrade is refused while your team exceeds the target plan's limits, and the message says what is in the way — "remove 4 sites and 2 team members first". Nothing is deleted for you.
Cancelling
Cancel from the billing page. The plan stays active until the end of the period you have paid for, then stops. You can resume during that window.
Cancelling does not stop metering. Your servers keep running and keep being billed. Tear down your environments if you want infrastructure charges to stop.
When a payment fails
Everyone on the team is notified. Deployments are blocked until it succeeds — but running infrastructure is never destroyed for non-payment. Nothing of yours is deleted because a card expired.
Deploying requires a plan
You need an active subscription to deploy. Existing stores keep serving traffic regardless of subscription state; it is starting a new deploy that is gated.