Changelog

• May 14, 2025

  Appwrite 1.6.2 is now available

  We're excited to announce a new update packed with some important fixes for your self-hosted Appwrite instance!

  Most notably, this release includes:

  • New push notification options for iOS and Android

  • Support for S3 endpoint URL

  • Figma OAuth2 provider

  • Fix for disabling email OTP auth method

  • Fix for resending team invitation emails

  • Fix for Amazon OAuth2 provider

  • Fix for Slack OAuth2 provider

  • Fix for high CPU usage in the appwrite container

  We're excited to see what you build! Head over to our migration guide to learn how you can upgrade your Appwrite instance.

  Important

  Please run the migrate command even if upgrading from 1.6.x.

  For the complete list of updates and fixes, check out the changelog below.

  View the changelog on GitHub

• May 8, 2025

  Announcing Init: a new era begins

  We are about to blow your socks off with what comes next for Appwrite.

  Init brings you a new week of major announcements from 19-23 May 2025. For those new to Init: it’s the start of something new here at Appwrite as we announce new products and features every day, for a week.

  We can’t disclose anything just yet, but we can say that this launch will forever change the way you build with Appwrite. A major stepping stone into a new Appwrite era, all with one mission of making software development accessible and fun for all.

  Read the announcement to learn more

• April 16, 2025

  Announcing the Appwrite Network: Appwrite’s vision for a global cloud infrastructure

  We’re excited to launch the Appwrite Network, a global network of cloud regions and edge locations designed to enhance Appwrite Cloud’s availability, performance, and regulatory compliance.

  Starting today, all Pro users can access three regions: Frankfurt (FRA), our first region, and two new regions in New York City (NYC) and Sydney (SYD). These new regions will be available to all Cloud users in the coming weeks, with more regions to follow.

  Key features of the Appwrite Network

  • Reduced latency with global coverage: By distributing regions and edge locations worldwide, we minimize physical distance and routing delays, ensuring faster response times and better user experiences.

  • Regional data control with global access: Choose where your data resides to meet local regulations and optimize for performance, while still ensuring global availability through Appwrite’s interconnected network.

  • Global CDN with built-in DDoS protection: Deliver content faster with our CDN powered by strategically placed PoPs, and stay secure with integrated DDoS mitigation that filters threats in real-time.

  We’re just getting started with the Appwrite Network and can’t wait to share what’s next. Thanks for being part of the journey, together, we’re shaping the future of cloud platforms for developers.

  Read the announcement to learn more.

• March 27, 2025

  Appwrite Cloud backups now faster

  Appwrite Cloud backups are now considerably faster, reducing wait times and improving reliability.

  What's changed

  We made key changes to the backup infrastructure by moving data reading operations inside the network, and implementing I/O optimizations for storage operations.

  Internal testing revealed notable time savings across database backups:

  • 3 minute backup → 1.5 minutes (2x faster)

  • 3.5 minute backup → 1.2 minutes (3x faster)

  • 6.7 minute backup → 2 minutes (3.4x faster)

  • 34.2 minute backup → 5.2 minutes (6.6x faster)

  Most databases showed at least a 2x reduction in backup time, with many achieving up to 7x faster backups.

  These optimizations improve the efficiency of data recovery and management. Your actual performance gains may vary depending on database size and structure.

  Learn more about backups

• March 19, 2025

  Update to budget limits in Appwrite Cloud

  We've updated how budget limits work in Appwrite Cloud to provide more control over organization scaling.

  What's changed

  • Previously, setting the budget to 0 meant the budget was disabled (unlimited usage), and null was not supported.

  • Now, null explicitly disables the budget, while 0 is a valid budget limit, meaning the organization will not scale beyond its allocated resources.

  This change ensures clearer budget management and better control over scaling limits.

  Learn more about budget limits