Skip to content
AOZUMIDocs

Limits and data safety

AOZUMI DB is experimental. The limits are the same for every workspace, and there are no backups yet. Plan for both.

Limits

LimitValueOver it
Size of a database256 MBWrites past it fail with SQLITE_FULL.
Time per statement5 secondsThe statement is stopped with SQLITE_INTERRUPT.
Requests per database100 a secondHTTP 429 with Retry-After.
Databases per workspace3, standalone and apps' togetherThe console stops offering New database, and the API answers workspace_limit.
Requests per API key60 a minuteHTTP 429 with Retry-After, on the AOZUMI DB API routes only.
Rows per statement in the console1,000The rest are not shown.

The console's Settings page shows the same limits. Each database's card shows its size against 256 MB.

AOZUMI DB Settings. Three tables: This workspace, with the role, access, server URL and how to connect; Limits, with 256 MB a database, 5 seconds per statement, 100 requests a second and 3 databases per workspace; and Not in the console yet, listing backups, app tokens and usage.

SQL the server refuses

These fail with SQLITE_AUTH, so one database can never reach another or a file outside it:

  • ATTACH and DETACH
  • VACUUM INTO
  • Any PRAGMA outside a short safe list, which includes table_info, user_version, foreign_keys and integrity_check

Data safety

  • Deleting is permanent. Delete database asks you to type the database's name. Its tables and rows are gone once you confirm.
  • Destructive SQL asks first. On the console's SQL page, a script that drops a table, index, view, trigger or column, or deletes or updates every row, waits for Run it anyway. Over the API and MCP, it comes back with confirm_destructive until it is sent again confirmed.
  • Writes are opt-in. The SQL page and the API run read-only unless writes are turned on, and only owners, admins and Manage keys can turn them on.
  • App databases may be reset. A database created from an app's settings may be reset while AOZUMI DB is in testing.
  • One copy. Each database lives on one server. There is no replication.
  • Size only. The console shows each database's size, not usage graphs.

Questions

Can I restore a deleted AOZUMI DB database?
No. There are no backups you can restore while AOZUMI DB is experimental, so deleting a database, or dropping a table, cannot be undone.
How do I keep a copy of my data?
Export what you need regularly: run select queries on the SQL page and download the results as CSV, or read the tables from a script with your token.
Can I raise the limits?
Not while AOZUMI DB is experimental. Every workspace gets the same limits.

Checked against the product on .