Build
Usage, limits and agreements
The free amounts, how usage is counted, and what happens at a limit.
Free amounts#
Every organization gets these amounts free each month, summed over its realms, for evaluation and for personal and non-commercial projects.
| Meter | Free each month |
|---|---|
| Realtime messages | 100 million |
| Users and agents | 50,000 |
| Emails | 3,000 |
| Room minutes | 3,000 |
| Recording minutes | 60 |
A user or agent counts in a month when they use your app at least a day after signing up; sign-ups who never come back are free. Commercial use and anything past the free amounts run under a written agreement with AUVY GmbH, which sets the prices; there is no online checkout. Ask for one through openpulse.org/contact.
How realtime is counted#
| What happens | Counts as |
|---|---|
| Your app sends an event (a message, an update) | 1 message, plus 1 per further started 64 KiB |
| An AI answer streams, start to end | 1 message, however many chunks (again past 10,000 events or 10 MiB) |
| A presence update up to 4 KiB (cursor, typing) | a tenth of a message |
| Delivery to readers, reads, reconnects, open connections, retries of the same post, rejected events | nothing |
Every post answers with what it counted, for example "billed": { "messages": 1, "presence": 0, "runs": 0, "run_events": 0 }, so you can see the count while you build. The Console shows realtime by day and exports CSV.
At a limit#
Without an agreement#
At 80% of a free amount the Console warns you; past 100% it shows you are over. At 110% that kind of new usage pauses until the month turns or an agreement covers it: new messages, new users, sending email, or new rooms and recordings. Reads and everything else keep working, and it resumes within a minute.
{ "ok": false, "error": "free_limit_reached", "realm": "acme", "hint": "…" }With an agreement#
The agreement sets what is included and what happens past it. The Console’s Usage page shows usage against it, and a limit it sets answers the same way as above.
Fair use#
Each realm may post up to 1,000 events a second, or 10,000 with an agreement, averaged over two seconds; an agreement can also set its own rate. Past it the relay refuses the post; nothing is stored or counted, and the SDK resends after the Retry-After delay.
{ "ok": false, "error": "rate_limited", "realm": "acme", "limit_per_sec": 1000, "hint": "…" }Invoicing#
AUVY invoices each agreement directly, as the agreement states, and is paid by bank transfer. The Console shows usage and takes no payment.