-
Notifications
You must be signed in to change notification settings - Fork 310
realtime update #2825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
realtime update #2825
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,29 @@ | ||||||||||
| --- | ||||||||||
| layout: changelog | ||||||||||
| title: "Appwrite Cloud: Realtime usage limits and billing enforcement" | ||||||||||
| date: 2026-03-23 | ||||||||||
| --- | ||||||||||
|
|
||||||||||
| Starting **April 15, 2026**, we will begin actively enforcing Realtime usage limits and billing on Appwrite Cloud. | ||||||||||
|
|
||||||||||
| Since launching Appwrite Cloud in beta, we have not actively enforced Cloud limits for Realtime. We are now transitioning to full enforcement so that usage is measured and billed according to your plan. This change ensures fair usage across the platform and allows us to continue investing in Realtime and the rest of the Cloud offering. | ||||||||||
|
|
||||||||||
| **Realtime limits:** | ||||||||||
|
|
||||||||||
| - **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M. | ||||||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Pro include 6M messages/month" is missing the third-person singular 's'. It should be "Pro includes 6M messages/month" to be grammatically correct and consistent with "Free plan includes" at the start of the same sentence.
Suggested change
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fix subject-verb agreement. The phrase "Pro include 6M messages/month" should be "Pro includes 6M messages/month" to maintain proper subject-verb agreement. 📝 Proposed fix-- **Messages:** Free plan includes 2M messages/month; Pro include 6M messages/month. Additional messages are billed at $2.50 per 1M.
+- **Messages:** Free plan includes 2M messages/month; Pro includes 6M messages/month. Additional messages are billed at $2.50 per 1M.📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||
| - **Concurrent connections:** Free 250, Pro 500. Additional connections are $5 per 1,000. | ||||||||||
| - **Max message size:** 256 KB on Free; 3 MB on Pro. | ||||||||||
|
|
||||||||||
| Bandwidth consumed by the Realtime service also counts toward your plan’s **general bandwidth** allowance—the same pool used by your other Appwrite Cloud traffic (for example, API and Storage). See your plan’s bandwidth limits on the [pricing page](/pricing). | ||||||||||
|
|
||||||||||
| You can view your current Realtime usage in the **billing usage breakdown** in the Appwrite Cloud console. Full details and plan comparison are on our [pricing page](/pricing). | ||||||||||
|
|
||||||||||
| To improve performance and reduce costs, we recommend using [Realtime queries](/blog/post/announcing-realtime-queries) to filter events server-side so your app receives only the updates it needs. Fewer messages mean lower usage and a better experience for your users. | ||||||||||
|
|
||||||||||
| {% arrow_link href="/pricing" %} | ||||||||||
| View pricing and limits | ||||||||||
| {% /arrow_link %} | ||||||||||
|
|
||||||||||
| {% arrow_link href="/blog/post/announcing-realtime-queries" %} | ||||||||||
| Reduce messages with Realtime queries | ||||||||||
| {% /arrow_link %} | ||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The file is named
2026-03-19.markdoc, which conventionally represents March 19, 2026, but thedatefield in the frontmatter is set to2026-03-23(March 23). Every other entry in this directory follows the convention of matching the filename to the frontmatter date (e.g.,2025-03-19.markdochasdate: 2025-03-19). If the changelog is sorted or keyed by thedatefield, this file will appear to belong to March 23, not March 19, leading to confusing ordering. The date should be corrected to match the filename, or the filename should be renamed to2026-03-23.markdoc.