Limits

Limit	Value
Databases per account	5
Storage per database	500 MB
Memory per Redis database	64 MB
Concurrent connections	20 per database (not MongoDB)
Statement timeout	30s (reads only on MongoDB)
Idle in transaction	60s
Longest TTL	30 days
API keys	10

blaze is free and has no billing, so these limits are what keeps it running rather than a tier to upgrade out of.

Storage enforcementCopy Anchor Link

Storage is sampled every five minutes. A database over its limit is suspended (connections refused, nothing deleted) and reinstated automatically once it is back under.

MongoDBCopy Anchor Link

MongoDB enforces less per tenant than the SQL engines, and the limits above apply to it as follows:

• Statement timeout covers reads only. The server's defaultMaxTimeMS stops find, aggregate, count and distinct after 30s. Writes are not bounded server-side, and an operation that sets its own larger maxTimeMS is not overridden. The dashboard Shell and Browser cap every operation, writes included, at 30s.
• No per-database connection limit. MongoDB has no per-user connection cap. The server has a single instance-wide limit shared by every tenant, so pool your connections and close what you do not use.
• Idle-in-transaction does not apply. Transactions need a replica set, and this is a standalone server.
• Storage counts the compressed on-disk size (storageSize). A database over the limit is suspended by removing its user's roles until it is back under. Nothing is deleted.

What the alpha does not have yetCopy Anchor Link

• No backups yet. Treat alpha databases as somewhere to build and test. A dropped database is gone, and there is nothing to restore it from.
• One region, one machine. blaze runs on a single VPS today. Connection strings use hostnames, never IPs, so it can grow without breaking the strings you have saved.

Engine availabilityCopy Anchor Link