Announcing DocumentsDB: Documents that evolve with your product_
Store flexible JSON documents, query them with the Appwrite SDKs, and let your data model evolve with your product instead of ahead of it.
Most application data does not arrive with a fixed shape. Early products change weekly, integrations return payloads you do not control, and user-generated content rarely fits the columns you designed three months ago. Forcing all of that through a rigid schema turns every product change into a migration.
That is why we are announcing DocumentsDB, an Appwrite database built for schemaless documents.
Create your first database
In your project, go to Databases, click Create database, and choose DocumentsDB as the type. Pick a compute specification, and the database is ready to hold collections in minutes.
Schemaless collections
A DocumentsDB collection holds documents as JSON. There are no columns to define and no schema to migrate. Two documents in the same collection can have different fields, and adding a new field is as simple as writing it.
You still get the full capabilities of an Appwrite database: document-level permissions, queries, ordering, and pagination, through the same SDK patterns as the rest of Appwrite Databases.
Platform capabilities included
DocumentsDB is a first-class member of Appwrite Databases, so the capabilities that make application data manageable come built in:
- Transactions group writes so related changes succeed or fail together.
- Bulk operations create, update, or delete many documents in one request.
- Atomic numeric operations increment and decrement counters safely on the server, with no read-modify-write races.
- JSON imports and exports move existing data in and out without custom scripts.
- Backups protect your data with scheduled and manual snapshots.
Because permissions are enforced at the document level, you can serve data directly to client applications without building an API layer in between.
Compute specifications
When you create a DocumentsDB database, you select a compute specification that fits your workload, and the database is provisioned for your project with its own resources. As usage grows, backups and scaling are handled from the same place you manage the rest of your Appwrite project. The available tiers and their prices are listed on the pricing page.
When to use DocumentsDB
DocumentsDB fits workloads where the shape of the data is the moving part:
- Product catalogs where every category carries different attributes
- Event and activity payloads from third-party integrations
- User-generated content with optional and evolving fields
- Prototypes that need persistence before the data model settles
If your data is structured and consistent, TablesDB with its typed columns and indexes remains the right choice. The two share the same platform, so mixing them within one project is normal.
Get started
DocumentsDB is available on Appwrite Cloud today. Create a database, choose DocumentsDB as the type, and you can write your first document within minutes.
