Appearance
Account limits
Every MicroApps account has a ceiling on how many of each resource it can hold. The limits are per account, not per user and not per Region: everyone on the account draws from the same pool. They keep a runaway script or a compromised account from racking up a surprise bill, and they keep capacity fair across everyone on the platform.
The defaults
| Resource | Default | Counts |
|---|---|---|
| Pods | 5 | Pods that exist, running or not |
| Domains | 10 | Custom domains added to the account |
| Networks | 10 | Private networks, including ones we auto-create for a pod |
| Firewalls | 10 | Firewalls, including ones we auto-create for a pod |
| Email accounts | 0 | Mailboxes across all your domains |
| Snapshots per pod | 5 | 4 you take by hand, 1 held for the auto schedule |
| Backups per pod | 5 | 4 you take by hand, 1 held for the auto schedule, until paid backups start |
The backups-per-pod limit stops applying once paid backups start. From then each new backup is billed by its size, so you can keep as many as you like, and each pod's schedule decides how many automatic ones it keeps. The snapshots-per-pod limit stays.
Mailboxes start at zero because email hosting is enabled on request - ask, and we raise it.
The rest arrive with your first top-up: a brand-new account sits at zero across the board until it has credit, so signing up and immediately creating fifty pods is not a thing that happens. Once granted, a limit never drops on its own.
Hitting one is not subtle. The create is refused with a plain message - Pod limit reached for your account, Email limit reached for this account - and nothing already running is disturbed.
Seeing your own
The console shows them under Account Settings, on the Account tab: Account resources gives a used-of-total bar per resource (and an At limit badge when you are there), and Per-pod limits shows the snapshot and backup numbers (backups read No limit once paid backups start). Over the API they are the max* fields on GET /api/user/account; maxBackupsPerPod stays in the response after the start date, but nothing enforces it.
Read your own rather than assuming the defaults. Limits are per account and yours may already have been raised.
Raising them
Limits are set by us. There is no self-service way to raise your own ceilings - the account update endpoint deliberately leaves them out - so nobody turns their own limits up by accident, or on purpose.
Contact support or open a support ticket from the console. We raise limits routinely for legitimate workloads; tell us what you are building and roughly how much headroom you need.