Use cases

Concrete blueprints, not generic feature lists.

Each use case maps a real product workflow to NonoDB collections, indexes, queries, background work, and operational limits. Start with the CRM blueprint — the most complete example today.

What a blueprint includes

The goal is a production blueprint. Each blueprint shows the data model, the indexes that make the main screens fast, the queries behind them, and the parts you should not force into the database.

Data model

Collections, fields, references, and when to embed versus append.

Indexes

Unique keys, compound indexes, text and fuzzy search, and TTL.

Core queries

Find, aggregate, SQL, history, and search for the main screens.

Automation

Outbox events, workers, live subscriptions, and retry-safe consumers.

Blueprints

Have a workflow in mind?

Tell us what you are building.