Your database's daily limit: alerts, paused writes and how to write less
Updated: 2026-11-05 · YaDominios
Every site with a database has a daily limit of rows written and rows read, based on its plan: Nébula 50,000 writes a day, Órbita 150,000, Galaxia 500,000 and Cosmos 1,500,000. At 80% we email you. At 100% of writes, we pause that site's writes until midnight (UTC): the site stays up, can be viewed and queried as usual, and nothing is deleted. Reads are never paused, they only trigger an alert. Your site card shows how much you've used today. If your business needs more, contact us and we'll raise your limit.
Who this is for: anyone with a site or app on YaDominios Cloud that uses a database, and anyone who builds it — a person or an AI.
Limits by plan
| Plan | Rows written per day | Rows read per day |
|---|---|---|
| Nébula | 50,000 | 20 million |
| Órbita | 150,000 | 50 million |
| Galaxia | 500,000 | 200 million |
| Cosmos | 1,500,000 | 500 million |
The day is counted in Coordinated Universal Time (UTC). A typical business uses a small fraction of its limit: a store selling a hundred products a day writes a few thousand rows.
What happens at the limit
- At 80% you get an email with your usage and your limit.
- At 100% of writes we pause your site's writes until midnight (UTC). Your site stays up: it can be viewed, browsed and read from its database as usual. Anything that tries to save new data gets a clear error saying writes are paused. You get another email.
- At midnight everything resumes on its own. Nothing was deleted.
- Reads are never paused: if you go over your read limit, we only alert you.
Where to see it
In the panel, on your site card, the Database writes today bar shows your usage and your limit. If writes are paused, the card says so.
Why an app writes so much (and how to write less)
- INSERT OR REPLACE on rows that didn't change. It doesn't update: it deletes the row and inserts it again, and if other tables depend on it through cascading deletes or triggers, each replace can write hundreds of rows. Use
INSERT … ON CONFLICT(id) DO UPDATE SET … WHEREwith a condition that something changed. - Syncs that upload everything. Upload only what changed since last time, with a timestamp per device.
- Per-visit counters. A visit shouldn't write to the database: no counters, no guest sessions, no "last seen".
- Extra indexes. Every index counts as one more write for each row that changes. Keep only the ones a real query uses.
A simple test: sync twice in a row without changing anything. The second time should write zero rows.
If you need more
If your business really writes more than your limit, contact Support: we'll raise your limit the same day, and if writes were paused, they resume right away.
Frequently asked questions
Is anything deleted when I hit the limit?
No. Only writes are paused until midnight (UTC). Your data, your site and your files stay the same.
Does my site stop working?
No. It stays up and keeps reading its database. The only thing it can't do until midnight is save new data.
Can I get a higher limit?
Yes. Contact Support and we'll raise it for your site.