Axiom Cloud limits on Free and Pro

The monthly allowances, database counts, authentication reserves, branch, export and restore limits that apply to each Axiom Cloud project on Free and Pro.

Every Axiom Cloud project has a plan, Free or Pro. The plan sets the monthly allowances of the project's managed database environment. Allowances reset at the start of each calendar month (UTC). The Resources page shows the current figures; see Acore backend databases on Free and Pro for how measured usage appears there and what happens at 80% and at the limit. Prices are published at general availability.

Monthly allowances per project

Allowance	Free	Pro with PostgreSQL	Pro with SQLite (libSQL)
Database storage	100 MB	1 GB	100 MB
Rows read	10,000,000	100,000,000	10,000,000
Rows written	25,000	1,000,000	25,000
Database connections per server process	2	10	2
Requests	10,000	100,000	100,000
Execution time	1,000 seconds	10,000 seconds	10,000 seconds
Egress	100 MB	1 GB	1 GB
Authentication emails sent by Axiom	50	1,000	1,000
Resource operations (provision, retry, resume, restore and similar)	20	100	100
Hosted environments	1	1	1

A Pro project that keeps SQLite keeps the Free database allowances (storage, rows and connections) and gets the Pro request, execution, egress, email and operation allowances. More database capacity on Pro needs PostgreSQL; see Upgrade a project.

Deleting a database, suspending it and installing or upgrading its authentication tables never count as resource operations.

Database counts

A Free account can own at most 3 Free databases across all its projects (branches do not count).
A Free account can run at most 60 resource operations a month across all its Free projects, so creating new projects does not reset the budget.
A Pro database needs an active Pro subscription to be provisioned, retried or resumed.

Authentication reserve

Managed application authentication has its own monthly reserve per environment, so sign-ins never use your application's rows-written allowance.

Entitlement	Free	Pro with SQLite (libSQL)	Pro with PostgreSQL
Authentication rows written (reserve)	25,000	25,000	250,000
Rows per user (sign-ins and token refreshes)	6,000	20,000	60,000
New users per day	100	100	1,000

When a user reaches the per-user figure, that user's sign-ins and refreshes are refused with AXAUTH_QUOTA for the rest of the month. When the reserve is used up, new users are refused first; existing users keep signing in. Signing out, revoking sessions, banning users and changing passwords or roles are never refused for quota.

Preview branches

Limit	Free	Pro
Default lifetime	24 hours	72 hours
Longest lifetime	72 hours	7 days
Live branches per project	1	3
Branch creations per day	3	10
Branch storage	100 MB	100 MB

Preview branches are available to selected projects during the Alpha. See Preview branches.

Restore and backups

Limit	SQLite (libSQL)	PostgreSQL
Point-in-time restore window	Last 24 hours	Last 6 hours
Daily backups kept	7 days	7 days
Previous copy kept after a restore or move	24 hours	24 hours

Daily backups and Owner restores are turned on for selected projects only today, and will be on for every project at general availability. At most one previous copy is kept at a time. Every retention period is published with the operations policy at general availability.

Data editor and export

Limit	Value
CSV export size	50,000 rows or 25 MiB, whichever comes first
CSV exports per project per day	20
Exports running at once per project	1
Rows changed by one confirmed edit	10,000

Platform-wide limits

Some limits protect the shared service rather than one project. They can refuse a request even when your project is under its own allowances:

Shared SQLite (libSQL) capacity near its provider limit can stop the largest consumers until shared usage falls.
Axiom's own authentication mail has a daily platform budget. Projects that send through their own SMTP server are not limited by it.
Cloud sign-in codes have a cooldown of 60 seconds per address.