Update top performing blogs + Add a new "News" category

src/routes/blog/category/news/+page.markdoc

@@ -0,0 +1 @@
+

src/routes/blog/post/appwrite-compared-to-supabase/+page.markdoc

@@ -11,6 +11,8 @@ unlisted: true
 callToAction: true
 ---
 
+Updated on October 6, 2025
+
 If you are looking to build a mobile app, website, tool, or any other application that needs a backend, then you also know the daunting tasks that await. This is probably what brought you to this blog in the first place: looking for a solution to take care of your backend. One of these solutions is a Backend-as-a-Service (BaaS). It provides pre-built backend infrastructure and services to simplify app development, handling server-side tasks like data storage, user management, APIs, server maintenance, security, database management, and more. Two of these solutions are Appwrite and Supabase, and although both are solid options for your BaaS, they’re somewhat different.
 
 This article will give you a rundown of Appwrite and Supabase to understand the feature sets. Then, we’ll provide a quick Appwrite vs Supabase comparison so you can understand how each provider will fit your specific needs.
@@ -162,7 +164,13 @@ Any developer-first product, regardless of how good and simple it may be, will n
 
 # Conclusion
 
-While Appwrite and Supabase are great Backend-as-a-Service (BaaS) offerings that support numerous SDKs, they differ in engineering approaches. The choice between Appwrite and Supabase hinges on your needs and preferences.
+Both Appwrite and Supabase are strong platforms that make it easier for developers to focus on building instead of managing complex backend systems. They share many similarities but differ in how they approach development.
+
+Supabase offers a familiar experience for developers who prefer working closely with SQL and PostgreSQL. It’s a good choice if you want more control over your database structure, queries, and configurations at the database level.
+
+Appwrite, meanwhile, takes an all-in-one approach. It brings together authentication, databases, storage, functions, real-time features, messaging, and even hosting into a single platform. Whether you use Appwrite Cloud or self-host, you get a consistent and flexible experience that allows you to manage your entire stack in one place.
+
+If you’re looking for a complete, integrated platform to handle everything from your backend to hosting, Appwrite offers a simple and unified solution. But if you prefer the flexibility of direct database control and a more traditional SQL setup, Supabase is a good choice.
 
 Here’s a table that compares both Appwrite and Supabase:
 
@@ -176,13 +184,14 @@ Here’s a table that compares both Appwrite and Supabase:
 | Functions marketplace | Has a marketplace featuring a variety of function templates and integrations such as Discord bots, payments with Stripe, ChatGPT API, etc. | No functions marketplace |
 | Permissions | A simple-to-use permissions system that is consistent across all Appwrite products | Complex permissions system that needs knowledge of SQL to get started |
 | Messaging providers | 10 providers covering SMSes, emails, and push notifications | Zero |
+| Integrated Hosting | Yes | No | 
 
 Here's a price comparison between Appwrite and Supabase to help you choose the one that best suits your needs:
 
 | Feature | Appwrite | Supabase |
 | --- | --- | --- |
 | Pricing Model | Tiered pricing | Tiered pricing |
-| Paid Plan | Starts at $15 per month | Starts at $25 per month |
+| Paid Plan | Starts at $25 per month | Starts at $25 per month |
 
 # Resources
 

src/routes/blog/post/appwrite-vs-firebase-vs-supabase-functions-comparison/+page.markdoc

@@ -10,6 +10,9 @@ category: product
 featured: false
 callToAction: true
 ---
+
+Updated on October 6, 2025
+
 Serverless functions are a powerful tool for developers designed to provide flexibility and simplify backend tasks. With serverless functions, you can focus more on writing code and less on managing infrastructure, making your work faster and more efficient.
 
 In this comparison, we'll take a look at the serverless functions offered by three popular backend-as-a-service platforms: Firebase, Supabase, and Appwrite.
@@ -109,6 +112,26 @@ Appwrite's flexibility in language support and modularity makes it a great choic
 
 By understanding the strengths and limitations of each platform, you can select the one that best aligns with your project goals and development workflow.
 
+# Frequently asked questions (FAQs)
+
+**1. What are serverless functions and how do they work?**
+
+Serverless functions are small pieces of backend code that run only when needed, without you managing any servers. Instead of keeping a server running 24/7, the platform automatically spins one up when your function is triggered, runs your code, and then shuts it down. It’s cost-efficient, scalable, and perfect for handling tasks like API calls, webhooks, or background jobs.
+
+**2. Why do developers use serverless functions?**
+
+Because they save time and reduce complexity, you can focus on writing logic instead of configuring servers, scaling infrastructure, or handling deployments. Serverless functions are great for apps that need to grow quickly or handle unpredictable workloads.
+
+**3. Which platform offers the most flexible serverless functions?**
+
+Appwrite stands out for flexibility. It supports multiple languages: JavaScript, Python, PHP, Dart, Ruby, and Go, and works across different frameworks. You can trigger functions with HTTP calls, events, or schedules, and even deploy directly from GitHub. It’s open source too, so you can self-host or use the managed cloud.
+
+**4. Do serverless functions have performance issues?**
+
+Sometimes. The first run after inactivity can be slightly slower, called a cold start. Platforms like Supabase reduce this with edge functions, while Appwrite lets you optimize using async or delayed executions. Once active, performance is generally smooth and reliable.
+
+# More resources
+
 - [Appwrite Function docs](https://appwrite.io/docs/products/functions)
 - [Firebase Cloud Functions docs](https://firebase.google.com/docs/functions)
 - [Supabase Edge Functions docs](https://supabase.com/docs/guides/functions)

src/routes/blog/post/how-to-back-up-your-appwrite-data/+page.markdoc

@@ -9,6 +9,8 @@ author: bradley-schofield
 category: product
 ---
 
+Updated on October 6, 2025
+
 Backing up and restoring data is an extremely important part of running servers. It's a virtual safety net against most bad things that can happen. Made a bad config change? Restore a backup. Messed up an update? Restore a backup. Corrupted Drives? Restore a backup.
 
 Not only that, backups can also come in handy when migrating data to other systems, like migrating a development server into a production environment or vice versa.
@@ -128,8 +130,39 @@ We hope you enjoyed this article! We love contributions and encourage you to tak
 
 If you get stuck anywhere, feel free to reach out to us on our [friendly support channels](https://appwrite.io/discord) run by humans.
 
+# Frequently asked questions (FAQs)
+
+**1. Why should I back up my Appwrite instance regularly?**
+
+Backups protect your data from accidental deletions, failed updates, or hardware issues. They also make it easy to migrate between servers or environments. Regular backups ensure you can restore your setup quickly without losing user data or configurations.
+
+**2. What parts of Appwrite do I need to back up?**
+
+You only need to back up two main things:
+
+- The MariaDB database (stores all project data)
+- The Docker volumes for functions, uploads, and builds.
+
+Everything else is stateless and can be regenerated automatically by Appwrite.
+
+**3. Can I back up Appwrite while it’s running?**
+
+It’s possible, but not recommended. To avoid incomplete or inconsistent backups, it’s best to shut down your Appwrite instance before running backup commands. This ensures all data is captured correctly.
+
+**4. How do I restore an Appwrite backup to a new server?**
+
+Move your backup files to the new server, place them next to the `docker-compose.yml`, and run the restore commands for the database and volumes. Don’t forget to copy your `_APP_OPENSSL_KEY_V1` environment variable, it’s required to decrypt your data.
+
+**5. Where should I store my Appwrite backups?**
+
+Keep backups in multiple safe locations, ideally a mix of local storage and cloud storage. This protects you from local disk failures and makes recovery easier if your primary environment goes down.
+
+**6. How often should I back up my Appwrite database?**
+
+It depends on how frequently your data changes. For active projects, schedule daily or hourly backups of the MariaDB database to prevent data loss. You can automate this using cron jobs or CI pipelines. For smaller or less active projects, weekly backups are usually enough. Just make sure to store them securely and test restores occasionally.
+
 Here are some handy links for more information:
 
 - [Appwrite contribution guide](https://github.com/appwrite/appwrite/blob/master/CONTRIBUTING.md)
 - [Appwrite Github](https://github.com/appwrite)
-- [Appwrite docs](https://appwrite.io/docs)
+- [Appwrite docs](https://appwrite.io/docs)

src/routes/blog/post/how-to-optimize-your-appwrite-project/+page.markdoc

@@ -10,6 +10,8 @@ category: product
 featured: false
 ---
 
+Updated on October 6, 2025
+
 As your Appwrite project scales, performance and resource management become critical, not just to keep your app running smoothly, but also to avoid unexpected usage spikes. While Appwrite is designed to scale effortlessly, it's important to proactively optimize your usage so you don't reach resource limits prematurely. Effective optimization helps reduce costs, improves performance, and enhances user experience without compromising on functionality.
 
 This guide provides a detailed overview of techniques to optimize your Appwrite project, covering API request management, caching strategies, file compression, image optimization, and other methods to ensure your app performs well while staying within your desired resource limits.
@@ -245,8 +247,30 @@ Optimizing your Appwrite project ensures you not only provide a better experienc
 
 These optimizations aren't just about cost savings—they are about making your app more scalable, efficient, and reliable as it grows. Rather than waiting until you hit plan limits, taking a proactive approach builds trust and ensures your users always experience the best possible performance, even as your app scales.
 
-Further reading and resources:
+# Frequently asked questions (FAQs)
+
+**1. How can I reduce API request usage in Appwrite?**
+
+Use smart querying with `listDocuments()` and filters instead of multiple requests. Combine queries, enable pagination, and use the Realtime API for live updates instead of polling. This reduces server load and speeds up responses.
+
+**2. What’s the best way to cache data in an Appwrite app?**
+
+Cache frequently accessed or static data using localStorage or IndexedDB on the client, and use Redis for server-side caching. Set expiry rules to prevent stale data and limit unnecessary API calls.
+
+**3. How do I optimize file storage and image performance?**
+
+Enable bucket compression (gzip or zstd) and serve images using the Preview API for resizing or converting to formats like WebP. For global apps, add a CDN to deliver files faster and reduce server strain.
+
+**4. Can Appwrite automatically scale my project?**
+
+Yes. Appwrite Cloud handles automatic scaling for traffic spikes and workload increases. For self-hosted setups, you can scale manually using Docker containers to distribute services across multiple servers.
+
+**5. How can I prevent hitting resource or budget limits?**
+
+Set usage alerts and budget controls in the Appwrite Cloud Console. You can define spending caps and get notified before reaching limits, helping you manage resources proactively and avoid unexpected overages.
+
+# Further reading and resources:
 
-- [Serverless functions 101: Best practices](http:appwrite.io/blog/post/serverless-functions-best-practices)
+- [Serverless functions 101: Best practices](http://appwrite.io/blog/post/serverless-functions-best-practices)
 - [Appwrite Queries documentation](https://appwrite.io/docs/products/databases/queries)
 - [Appwrite Buckets documentation](https://appwrite.io/docs/products/storage/buckets)

src/routes/blog/post/open-source-firebase-alternative/+page.markdoc

@@ -10,6 +10,8 @@ category: product
 callToAction: true
 ---
 
+Updated on October 6, 2025
+
 If you are looking to build a mobile app, website, tool, or any other application that needs a backend, then you also know the daunting tasks that await. This is probably what brought you to this blog in the first place: looking for a solution to take care of your backend. BaaS provides pre-built backend infrastructure and services to simplify app development, handling server-side tasks like data storage, user management, APIs, server maintenance, security, database management, and more. Two of these services are Firebase and Appwrite.
 
 Appwrite and Firebase are both solid options to choose as the Backend-as-a-Service (BaaS) for your app. However, their feature sets can vary substantially. In this article, we will give you a rundown of Appwrite and Firebase to understand how each provider will fit your specific needs.
@@ -141,15 +143,21 @@ Hosting refers to the service that allows developers to deploy and serve web app
 
 # Conclusion
 
-While both Appwrite and Firebase are great Backend-as-a-Service offerings that support numerous SDKs and integrations, they differ in terms of capabilities and pricing. The choice between Appwrite and Firebase hinges on the specific needs of a project. Appwrite stands out with its open-source nature, self-hosting capabilities, pricing affordability, and emphasis on privacy. The community is very welcoming and is praised for it. Firebase's strength lies in its comprehensive ecosystem, Google support, and maturity.
+Both Appwrite and Firebase are powerful platforms that simplify backend development and help teams focus on building great products rather than managing infrastructure. They share many similarities but take different approaches to solving the same challenges.
+
+Firebase offers a mature, battle-tested ecosystem that’s deeply integrated with Google Cloud. It’s a good choice for teams looking for a managed, ready-to-use solution that scales seamlessly with minimal setup.
+
+Appwrite, meanwhile, brings the benefits of open source to modern development. It provides a unified platform where you can manage authentication, databases, storage, messaging, and even hosting—all in one place. You can self-host Appwrite for full control or use Appwrite Cloud for a managed experience. This flexibility, combined with transparent pricing and a growing developer community, makes Appwrite a strong alternative for teams that want ownership and customization.
+
+Ultimately, the right choice depends on your priorities. If you want a managed, plug-and-play ecosystem with deep Google Cloud integrations, Firebase fits the bill. If you value openness, flexibility, and an all-in-one development experience that you can run anywhere, Appwrite is built for you.
 
 Here’s a table that compares both Appwrite and Firebase:
 
 | Feature                                                                                                                                    | Appwrite                                                                                                                                   | Firebase                                                                                                                                   |
 | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
 | Deployment                                                                                                                                 | Self-hosted or cloud-hosted                                                                                                                | Cloud-hosted only                                                                                                                          |
 | Free plan                                                                                                                                  | Yes, Free plan                                                                                                                             | Yes, Spark plan                                                                                                                            |
-| Paid plan                                                                                                                                  | Yes, Pro plan - $15 per month per member and addons                                                                                        | Yes, Blaze plan - Pay-as-you-go                                                                                                            |
+| Paid plan                                                                                                                                  | Yes, Pro plan - $25 per month                                                                                                              | Yes, Blaze plan - Pay-as-you-go                                                                                                            |
 | Open source                                                                                                                                | Yes                                                                                                                                        | No                                                                                                                                         |
 | Support                                                                                                                                    | Community and email                                                                                                                        | Community, Support Portal, and help center                                                                                                 |
 | Functions marketplace                                                                                                                      | Has a marketplace featuring a variety of function templates and integrations such as Discord bots, payments with Stripe, ChatGPT API, etc. | Has an extensions hub featuring pre-built functions ready to deploy.                                                                       |