Approvals and spending limits
What needs approval, who can approve it and how limits are counted.
Anything that costs money, or could take something offline, waits for a person to approve it. The approval covers the exact resource and parameters, so what runs is what was approved.
What needs approvalLink to this section: What needs approval
| Action | Who can approve |
|---|---|
| Buying a server or a domain | An owner (approve spending) |
| Stopping or rebooting a server | An owner (every site on it goes down) |
| A site's first public launch | Always an owner's review |
| Creating hosting, a database or a service | An owner or administrator (approve launch) |
| Adding, changing or removing DNS records | An owner or administrator (approve launch) |
| Purging an archived site | An owner, after 7 days, separately |
Starting a server, and starting, stopping or restarting an app or database, run straight away for people with infrastructure or deploy rights, and are recorded in the audit log.
Exact pricesLink to this section: Exact prices
Domain purchases, renewals and transfers approve the price you were quoted. Just before buying, the price is checked again, and nothing is bought if it changed. Alternatives are never suggested or bought for you.
Spending limitsLink to this section: Spending limits
Set a monthly spending limit, daily limits on new servers and domain registrations, and a monthly AI budget. A period counts:
- every request that hasn't settled yet (waiting for approval, queued, running), however old;
- requests made in the period;
- requests that finished in the period.
So a request made at the end of one month and approved in the next counts in both, and a limit can't be exceeded around the turn of a month.
AI costsLink to this section: AI costs
Each AI task has a cost limit. Usage is measured the same way for every model provider, so limits and the monthly AI budget work for all of them.