You can now manage memberships privacy across all Appwrite plans, helping you protect sensitive member details.
With this feature, you can mark specific membership details like the user's name, email, and multi-factor authentication status as private.
To configure these settings, head to Auth > Security > Memberships Privacy in the Console.
If you have any questions or feedback, please let us know on Discord.
Read more about memberships privacy
We've updated Appwrite Cloud to improve usability and workflows:
Table content no longer gets truncated in views.
The database deletion flow has been redesigned to prevent accidental deletions.
Usage cards now have a cleaner, simpler view.
Fixed broken links on the billing page.
Removed bulk deletions from the database table for added safety.
These changes make the console easier to use. Try them out and share your experience with us.
Join the discussion on Discord
We have updated the Free plan's bandwidth limit from 10GB to 5GB to maintain platform sustainability and performance.
The Free plan remains tailored for projects in the development stage or hobby projects, which typically use less than 5GB of bandwidth.
Learn how to optimize your projects for costs and performance in this article.
If you have any questions, please contact us at pricing@appwrite.io.
We've shipped several updates and improvements to Appwrite Cloud for a smoother experience:
The backups feature popup modal now appears only on Cloud environments, avoiding confusion for self-hosted users.
Improved database screen UI for self-hosted users by removing an unnecessary column.
Added clearer guidance for ID-related fields when creating attributes in modals.
Resolved an issue in the Billing tab where organizations without invoices caused a broken view. The tab now handles this scenario correctly.
Improved consistency by utilizing an .env variable for the growth endpoint.
Adjusted the pill component's height to prevent text overflow issues
Provided better messaging to indicate when credits have expired.
Updated and corrected the text in the plan summary section.
Resolved an issue with modals failing to show correctly in Safari.
Improved API performance under load.
Improved Functions performance for more stable and consistent function executions.
These updates are aimed at improving the overall usability and performance of Appwrite Cloud. Let us know if you encounter any issues!
Explore the Console to see the updates
We've made several updates to improve performance on Appwrite Cloud:
Increased the default CPU for function runtimes on the free tier from 0.5 CPU to 1 CPU.
Updated Python runtimes to include the --preload flag in Gunicorn, resulting in faster cold starts.
Improved the rules fetching logic in the Appwrite router to make better use of caching, reducing latency by up to 50ms for functions executed via domains.
Updated Redis HA clusters to improve redundancy and high availability for caching, queues, pub-sub, and shared state services.
Adjusted our API and CDN compression logic to avoid compressing small responses, improving performance and making usage stats more accurate.
These updates aim to make your projects faster and more reliable, especially under high-demand scenarios.
Join the discussion on Discord
We've added support for new function runtimes and capabilities:
Added support for the latest runtimes, including:
Node.js 22
Dart 3.5
Bun 1.1
Improved error reporting on the Functions executor, ensuring similar errors are grouped together for easier debugging.
These updates ensure Appwrite supports the latest tools and helps you debug faster.
Learn more about supported runtimes
The users.create event now triggers for OAuth, CreateTeamMemberships, and other user creation methods. This improvement makes it easier to automate workflows like welcome emails or user initialization across different scenarios.
To support this, we've updated the internal event architecture to handle more complex event types. This lays the foundation for even more flexible event handling in the future.
Learn more about events in Appwrite
We've resolved several issues to improve reliability across Appwrite:
Fixed a bug where 409 responses during runtime creation were incorrectly treated as errors. Requests now retry until the runtime is ready.
Fixed CDN 502 errors by refining the server compression strategy.
Addressed storage provider 503 errors by adding retry logic, following storage provider's recommended guidelines.
These fixes improve stability and make Appwrite more reliable for your projects.
If you have any questions about these changes, notice anything unexpected, or need clarification, please don't hesitate to reach out to our support team. Your feedback helps us improve and ensure a smooth experience for everyone.
We’re excited to announce our newest initiative: the Appwrite Education program. We’re partnering with GitHub for this new program to contribute to the future education of millions of developers connected to the GitHub Student Developer Pack.
Read the announcement to learn more
Appwrite now supports Deno 2.0 for local function development. When you run appwrite init functions, you'll see Deno as an available runtime option. This allows you to develop and test your functions locally using Deno's modern, secure, and fast runtime.
With Deno 2.0, you can take advantage of built-in tools like the linter, test runner, and formatter, making local development much easier.
For pro developers and teams that need to scale their products.
Start buildingFor pro developers and production projects that need the ability to scale.
For enterprises that need more power and premium support.
Contact us