Stop Using Firebase… Try This Open-Source Alternative (Appwrite)

The speaker introduces the common pain point where Firebase becomes prohibitively expensive and restrictive as an application's traffic grows. Firebase users often realize they lack true control over their backend and data ownership, leading to a search for alternatives. Appwrite is presented as an open-source solution that retains essential features like auth and real-time databases while giving power back to the developer. It is described as 'your server, your VPS, and your rules,' emphasizing the freedom of self-hosting. This section establishes the context of why developers are increasingly migrating to this platform in 2026.

This section dives into the specific technical building blocks provided by Appwrite, including robust authentication methods like magic links and MFA. The database is explained as a hybrid of document and relational structures, providing flexibility for various data models. Additionally, the platform supports serverless functions in over 13 languages and messaging services for SMS and push notifications. The speaker highlights that despite its power, the setup process is surprisingly simple for developers of all levels. This overview demonstrates that moving to an open-source tool doesn't mean sacrificing the modern features found in proprietary clouds.

The speaker demonstrates how to spin up an Appwrite backend in just a few minutes using a single Docker Compose command. After the initial launch, the process involves creating a new project, such as a 'TodoApp', and configuring environment variables. Detailed instructions are given on setting up a database collection, which functions similarly to a table in a traditional database. The guide also covers the crucial step of setting granular permissions for 'any' user or authenticated users to manage CRUD operations. This practical walkthrough emphasizes the 'low-code' nature of managing backend logic through the Appwrite console.

This segment focuses on integrating the newly created Appwrite backend into a frontend application using project IDs and API endpoints. The speaker performs a live test by creating a user account and adding tasks to verify that data persists without errors. A key feature showcased is the real-time capability, where data updates are visible across multiple browser tabs instantaneously. By using a very small amount of code, the developer can achieve complex functionality like synced authentication and data fetching. This section proves the efficiency of the Appwrite SDK in handling real-time synchronization out of the box.

The speaker discusses the strategic reasons why developers are moving to Appwrite, focusing heavily on the lack of 'pay-per-seat' pricing and hidden fees. Ownership is a recurring theme, as being open-source allows developers to protect their data more effectively than with closed-source vendors. While Firebase and Supabase have similar features, Appwrite is positioned as a more straightforward and less fragmented option. The SDKs for React and Flutter are noted for being particularly strong, though the speaker admits open-source tools require some developer effort. This comparison helps viewers decide if the trade-off between managed services and self-hosting is right for them.

In the final section, the speaker addresses technical requirements such as the need for Docker knowledge and the absence of a built-in global CDN. Because the database is MariaDB-based rather than Postgres, it offers a different experience than Supabase, which might influence a developer's choice. Suggestions are made for integrating third-party tools like Cloudflare for edge functions or Better Stack for monitoring large-scale deployments. The video concludes by recommending Appwrite for privacy-focused startups, mobile developers, and anyone looking to slash their backend bills. The speaker encourages viewers to try the tool themselves, as it takes less than a few minutes to get started.