Skip to main content
Auxilian is free, and these limits keep it that way. They apply equally to the web app and MCP tools. When you reach one, the request fails with a message that names the limit.

​
Workspaces

​
Projects and tables

​
How storage is measured

Storage is the on-disk size of every table in the project, including indexes and large-value storage. Auxilian checks it before each insert, update, table creation, and column addition. Once the project reaches 50 MB, those writes are refused. Reads, exports, row deletes, and drops still work. To get back under the limit, drop tables you no longer need. Dropping a table frees its space immediately.
Deleting rows doesn’t reliably lower the measured size. Postgres keeps the space inside the table and reuses it for new rows rather than shrinking the table on disk. To compact a large table, export it to CSV, drop it, and recreate it with only the rows you need.

​
Rows and values

​
Rate limits

When a budget runs out, wait a minute and retry. MCP tools return RATE_LIMITED, and the web app shows Too many changes in a short time; wait a minute and try again.
To load lots of data within the write budget, insert 100 rows per call. 60 calls of 100 rows is 6,000 rows per minute.

​
Activity log retention

Activity events are kept for 90 days. The web app shows the 100 most recent.

​
Need more?

If a limit blocks a real use case, email [email protected] and describe what you’re building.