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

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

@@ -10,6 +10,7 @@ category: product
 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.
 
@@ -162,7 +163,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 Backend-as-a-Service 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 +183,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/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 Backend-as-a-Service 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.                                                                       |

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

@@ -11,6 +11,8 @@ featured: false
 callToAction: true
 ---
 
+Updated on October 6, 2025
+
 Deploying modern web applications should be fast, flexible, and reliable. As developers, we've come to expect instant previews, custom domain support, seamless environment configuration, automatic HTTPS, and the ability to deploy everything from static pages to full server-rendered apps.
 
 Vercel has been a default choice for frontend teams building with Next.js. But with the launch of **Appwrite Sites**, you now have a new, integrated way to deploy web apps, especially when you want your front end to live alongside your backend, database, authentication, and storage.
@@ -216,6 +218,28 @@ You can get started today by heading to your Appwrite Console and creating a new
 
 If you have any questions, reach out to the Appwrite community on [Discord](https://appwrite.io/discord) or use the [contact form](https://appwrite.io/contact-us) on the website.
 
+# Frequently asked questions (FAQs)
+
+**1. Is there an open-source alternative to Vercel?**
+
+Yes. Appwrite Sites is a modern, open-source alternative to Vercel. It lets you deploy static and server-side rendered apps while managing your backend, database, auth, and storage, all in one place.
+
+The key difference is control: Vercel is fully managed and frontend-focused, while Appwrite Sites gives you the same smooth deployment experience with the flexibility to self-host or use the cloud. If you want an all-in-one, open, and developer-friendly setup, Appwrite Sites is worth considering.
+
+**2. Does Vercel support backend services?**
+
+Not directly. Vercel is built mainly for frontend hosting and serverless rendering. You can create API routes or edge functions, but they’re limited to lightweight serverless use cases, not full backend systems.
+
+If you need databases, authentication, file storage, or custom server logic, you’ll have to connect Vercel to external services.
+
+Appwrite Sites, on the other hand, combines hosting, backend, and APIs in one platform, so your front end and backend live together, reducing setup time and integration issues.
+
+**3. Does Appwrite Sites support Git deployments and custom domains?**
+
+Yes. Appwrite Sites fully supports Git-based deployments—you can connect your GitHub repo, select a branch, and automatically deploy on every commit or pull request.
+
+It also supports custom domains, with automatic HTTPS and SSL certificates included. You can connect domains via CNAME or nameserver (NS) configuration, and even create branch-specific preview URLs for testing before production.
+
 # More resources
 - [Appwrite Sites docs](/doc/products/sites)
 - [Announcing Appwrite Sites: the open-source Vercel alternative](announcing-appwrite-sites)

src/routes/blog/post/self-hosting-appwrite-with-coolify/+page.markdoc

@@ -9,6 +9,8 @@ author: chirag-aggarwal
 category: tutorial
 ---
 
+Updated on October 6, 2025
+
 Appwrite was built with self-hosting in mind, making running on your own hardware as easy as possible with minimal hassle. Self-hosting allows users to have complete control over their stored data and provides extensive customization capabilities, enabling users to modify and tailor the source code to perfectly align with their needs.
 
 This blog will discuss how to self-host Appwrite on your servers from scratch and some troubleshooting tips you might need.
@@ -141,7 +143,9 @@ Currently, Coolify will mark all the Appwrite containers as unhealthy due to a l
 
 # Appwrite Cloud vs Self-hosting with Coolify
 
-Appwrite also offers Cloud as a subscription-based Backend-As-A-Service (BaaS), eliminating the complexities of managing infrastructure so developers can focus purely on building their apps. With Appwrite Cloud, you get instant access to Appwrite's powerful features — databases, authentication, storage, and functions — without the need to self-host or worry about server maintenance.
+Appwrite also offers Cloud, a subscription-based all-in-one cloud platform that eliminates the complexities of managing infrastructure and hosting. With Appwrite Cloud, you can build, deploy, and host your entire application, frontend and backend, from a single platform.
+
+It provides instant access to Appwrite’s complete suite of services, including authentication, databases, functions, storage, messaging, and hosting, all tightly integrated and managed for you. This means no manual server setup, no configuration headaches, and no maintenance, just a seamless integrated environment where you can go from idea to live app in minutes.
 
 Choosing between Appwrite Cloud and self-hosting with Coolify depends on your project's needs. Here’s a side-by-side comparison to help you decide:
 
@@ -158,16 +162,34 @@ Choosing between Appwrite Cloud and self-hosting with Coolify depends on your pr
 
 # Conclusion
 
-Self-hosting Appwrite with Coolify combines the strength of an end-to-end backend-as-a-service with the flexibility and autonomy of self-hosting. It enables developers to create powerful applications while retaining data sovereignty and possibly incurring lower operational expenses.
+Self-hosting Appwrite with Coolify combines the strength of an all-in-one dev platform with the flexibility and autonomy of self-hosting. It enables developers to create powerful applications while retaining data sovereignty and possibly incurring lower operational expenses.
 
 By following this guide, you've successfully deployed a production-capable Appwrite instance that you completely own. As your application grows, the union of Appwrite's robust features and Coolify's efficient management will continue to provide a solid foundation for your development requirements.
 
+# Frequently asked questions(FAQs)
+
+**1. Can I self-host Appwrite on my own server?**
+
+Yes, absolutely! Appwrite was built with self-hosting in mind. You can run it on your own hardware, a VPS, or cloud providers like DigitalOcean, AWS, or Azure.
+
+Self-hosting gives you control over your data, security, and setup. You can even modify the source code to fit your exact needs. Tools like **Coolify** make it even easier by handling the deployment for you, so you don’t have to manage containers or complex configurations manually.
+
+**2. When should I choose Appwrite Cloud over self-hosting?**
+
+If you want to move fast: launch prototypes, MVPs, or production apps without managing servers, Appwrite Cloud is ideal. It’s fully managed, so you can deploy and host your entire stack (frontend + backend).
+
+It’s also great for teams that want predictable costs and built-in scalability. The platform automatically handles updates, scaling, and backups, letting you focus on building, not maintaining infrastructure.
+
+**3. Can I start with Appwrite Cloud and move to self-hosting later?**
+
+Yes, absolutely. That’s one of the biggest advantages of Appwrite being open-source and cloud-compatible. You can start on Appwrite Cloud to build and test your product quickly, and later migrate to a self-hosted setup with Coolify if you want to.
+
+The APIs and developer experience stay consistent between both environments, so switching later in the future should not be a huge deal.
+
 # More resources
 
 To learn more about self-hosting Appwrite on Coolify, you can check out the following resources:
 
 - [Self Hosting Docs - Appwrite](https://appwrite.io/docs/advanced/self-hosting)
 - [Coolify Docs for Appwrite](https://coolify.io/docs/services/appwrite)
 - [Self Host Appwrite on Coolify by Self-Host Everything](https://www.youtube.com/watch?v=9plbBKZNuvY)
-
-