Skip to content
Blog / Appwrite and MongoDB are partnering to build the future of open-source development
6 min

Appwrite and MongoDB are partnering to build the future of open-source development

Appwrite is joining forces with MongoDB, the world's best database company, to give developers a fully open-source, database-flexible backend platform they can own, grow with, and trust at every stage.

Appwrite and MongoDB are partnering to build the future of open-source development

Today, we're announcing a partnership between Appwrite and MongoDB.

More than just a technical integration, this is a long-term, strategic collaboration between two companies that share the same belief: developers deserve an open ecosystem of tools that actually work together, don't lock them in, and grow with them over time.

Why this partnership exists

Appwrite and MongoDB were both built for developers who want control. MongoDB gave the world a flexible, powerful data layer. Appwrite gave developers a complete open-source backend they could own end-to-end. Both companies grew by betting on the developer community and investing heavily in these builders.

What we're formalizing now is the natural next step: two companies committed to open source aligning around a shared vision, combining strengths, and committing to building something together that neither could build as well alone.

The goal is a backend platform that doesn't force tradeoffs. One where you can choose your database, own your infrastructure, and still get the developer experience you'd expect from a managed service, whether through open-source tools, managed platforms, or a hybrid approach.

How we're starting: MongoDB on self-hosted Appwrite

The first concrete result of this partnership is that MongoDB is now officially supported in Appwrite's self-hosted, open-source edition and Appwrite is now listed in the MongoDB Partner Ecosystem.

When you select MongoDB during setup, Appwrite spins up a MongoDB Community Edition container and manages everything alongside your other services. Your app talks to Appwrite through the same APIs and SDKs as always. Appwrite handles schema management, connections, and the full lifecycle.

Ready to get started? Our self-hosting tutorial walks you through everything you need to spin up an Appwrite instance powered by MongoDB.

How both communities benefit

For the Appwrite community, this partnership means your backend is no longer tied to a single data engine. As Appwrite expands database support, you gain real flexibility in how you architect and operate your infrastructure, without giving up the unified API, SDKs, and backend services you already rely on.

For the MongoDB community, this partnership opens a new door. Appwrite is a full-featured developer platform offering authentication, storage, serverless functions, databases, web hosting, and more. With MongoDB now supported as Appwrite's underlying data engine, MongoDB developers can adopt Appwrite as a complete backend layer that speaks their language, runs in their environments, and fits inside their existing operations.

Both communities benefit from something the open-source ecosystem rarely gets: two major platforms actively investing in making each other work better.

The larger vision

The end goal is a developer cloud where the database is never a constraint. One where you choose the data layer that fits your team, your stack, and your scale, and Appwrite works seamlessly on top of it.

Moving beyond a single database engine means giving developers a truly schema-flexible, cloud-native backend that doesn't force tradeoffs between ownership, flexibility, and experience. And it means building that future alongside the companies whose technology already powers the way developers work.

Here's what's on the roadmap:

  • MongoDB on Appwrite Cloud. MongoDB will be available in a fully managed environment. The console will adapt dynamically when running on MongoDB, and the experience will feel first-class from day one.
  • A more idiomatic NoSQL experience. We're working on an API that removes the need for rigid attribute definitions, giving developers a schema-flexible workflow that matches how people actually build with document databases.
  • Broader database flexibility across the platform. Alongside the recent introduction of TablesDB, this partnership signals the direction Appwrite is heading: a platform where you bring the database that fits your team, and Appwrite works seamlessly on top of it.

What comes next

This partnership is a beginning, not a destination. The work ahead is about making database flexibility a first-class part of what Appwrite means; not a feature, but a foundation.

We see a future where developers never have to choose between the tools they want and the platform that ties them together. Where open-source isn't a constraint but an advantage. Where the backend layer disappears into the background and teams spend their time building products, not plumbing.

Appwrite and MongoDB are building toward that future together. We'll share more as it takes shape; stay tuned for the announcements to come.

Frequently asked questions

  • What is the Appwrite and MongoDB partnership?

    Appwrite and MongoDB are partnering on a long-term collaboration around open source. The first concrete result is official MongoDB support in self-hosted Appwrite, plus a listing in the MongoDB Partner Ecosystem. Future work includes managed MongoDB on Appwrite Cloud and broader database flexibility across the platform.

  • How does MongoDB work with self-hosted Appwrite?

    When you select MongoDB during setup, Appwrite spins up a MongoDB Community Edition container and manages it alongside the rest of the stack. Your app talks to Appwrite through the same APIs and SDKs as before, and Appwrite handles schema, connections, and lifecycle.

  • Will MongoDB be available on Appwrite Cloud?

    Yes, that is on the roadmap. The plan is to offer MongoDB in a fully managed environment on Appwrite Cloud, with the Console adapting dynamically when running on MongoDB so the experience feels first-class from day one.

  • Does this replace Appwrite's existing database engine?

    No. MongoDB is an additional supported engine on self-hosted Appwrite, not a replacement. The direction is database flexibility, so you can pick the engine that fits your team, your stack, and your scale, while keeping the same Appwrite APIs and SDKs on top.

  • What does this mean for MongoDB developers?

    MongoDB developers can now adopt Appwrite as a complete backend platform that runs on top of MongoDB. They get Auth, Storage, Functions, Sites, and more, while still using the data engine they already know.

  • How do I get started with Appwrite on MongoDB?

    Follow the self-hosting tutorial for MongoDB in the Appwrite docs and blog. It walks through spinning up an Appwrite instance backed by MongoDB Community Edition end to end, so you can run the full platform on the database you already use.

Start building with Appwrite today