Ntfyx
Service limits.
Message allowances depend on Free, Plus or Pro. Public Topics allow anonymous reading and sending; protected Topics support verified answers and Call reminders.
Updated
Topics and devices
#These limits apply per Inbox unless stated otherwise. A temporary browser also uses a browser slot. Deleting a Topic releases its record; pausing it does not.
| Resource | Limit |
|---|---|
| Plan allowances | Free / Plus / Pro: 100 / 1,000 / 20,000 total messages per UTC day; 1 / 5 / 50 monitors and subscriptions |
| Total Topic records | 1000 for every plan; Topic count is not a paid entitlement. |
| Sources | 20 per Topic · 100 per Inbox |
| Receivers | 1 primary phone (iPhone or Android) + 2 browsers |
Daily budgets and rate limits
#Daily budgets reset at UTC midnight. This does not reset pending requests, storage or Topic state. Idempotent retries do not create duplicate logical events. Accepted replies, cancellations and receipts do not consume the new-message budget, but API rate limits still apply.
| Operation | Limit |
|---|---|
| All new messages | Free 100 / Plus 1,000 / Pro 20,000 per UTC day, including requests, monitor results and subscribed updates |
| Call reminders | Free 10 / Plus 100 / Pro 200; also consume one total message |
| New answer requests | Free 10 / Plus 100 / Pro 500; also consume one total message |
| Pending requests | At most 1000; storage reservation can reject earlier |
| New-event rate | 30 / minute per Source, burst 10; 120 / minute per Inbox |
| Control writes | 60 / minute per principal; 300 / minute per Inbox. Includes answers, claim, cancellation and receipts. |
| Read and sync | 120 / minute per principal; at most 100 events per page |
| Pairing creation | 10 / 10 minutes per IP, plus device protections. An IP address does not prove identity. |
Message sizes
#Limits apply to the complete encoded payload. Oversized content is rejected, never silently truncated and approved. The payload and encrypted-envelope limits must both pass.
| Content | Limit |
|---|---|
| Plaintext payload | 16 KiB including title, body, options and context |
| Encrypted envelope | 96 KiB including encoding, recipient ciphertexts and signature |
| Reply text / Deny note | 4 KiB / 2 KiB |
| Choice options | 2–8 options; ID 1–32 ASCII characters; label at most 120 Unicode characters |
Deadlines and temporary access
#The service checks expiry during reads and submissions. Cleanup jobs reclaim space; they do not determine whether an expired answer is valid.
| Item | Lifetime |
|---|---|
| Pairing QR | 5 minutes · single use |
| CLI question | 15 minutes by default · at most 24 hours |
| Claude permission question | 90 seconds for the request and remote wait; 100-second hook timeout |
| Temporary demo | 15 minutes · at most 10 events · source expires automatically |
Storage and retention
#Ordinary messages cannot use the capacity reserved for accepted requests and answers. A new request reserves room for its maximum answer and necessary terminal records before acceptance. Insufficient capacity refuses the request early; the service must not accept a question and later drop its Deny because ordinary storage is full.
| Storage | Limit / retention |
|---|---|
| Inbox ciphertext | 4156.25 MiB total · 3750 MiB ordinary + 406.25 MiB reserved |
| Public messages and protected relay ciphertext | At most 24 hours, within the storage limit |
| Public send retry receipts | Seven days of minimal IDs and content hashes; no message body |
| Requests and answers | Pending until the deadline; retained 1 days after reaching a terminal state |
| iPhone local history | Up to 90 days / 10,000 records; active requests and pending answers are protected |
| Web local history | Up to 30 days / 5,000 records delivered to that browser; can be cleared locally |
| CLI consumption ledger | 30 days after terminal state; active requests are protected |
| Service idempotency / consumption tombstones | 30 days of minimal IDs, hashes and terminal state; no extension of content retention |
Muting and notification grouping
#Muting a Topic changes phone alerts, not delivery, encrypted storage or the ability to reply. Muting ends at the selected time. Rapid ordinary progress may share a system notification per opaque task ID; requests retain distinct notification identifiers. Notification routing does not require a plaintext project or Topic name.
In iPhone builds that offer daily quiet hours, you can set a repeating range, including overnight; the default is 22:00–09:00. This feature depends on the installed build and does not stop messages or replies.
Hourly service monitors
#Free / Plus / Pro include 1 / 5 / 50 monitors. Checks run hourly. Paused monitors keep their slots until deleted. Accepted result messages and weekly summaries use the same daily message allowance as other messages. Quota exhaustion delays message delivery while checks continue; pending delivery is bounded and newer results may be coalesced.
Message content expires after 24 hours; numeric check observations have their separate seven-day window.