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
CRM
Contacts, companies, deals, activity timelines, audit history, automation, and pipeline reporting in one database.
Open blueprint →Available nowCustomer support
Tickets, conversations, help-center search, SLA automation, live queues, and support reporting without a second search service.
Open blueprint →Available nowE-commerce catalog
Products, variants, categories, typo-tolerant search, recommendations, inventory, carts, orders, and order events in one store.
Open blueprint →Available nowInternal tools
Admin panels, approval queues, audit history, durable jobs, live dashboards, and reporting for teams.
Open blueprint →Available nowMulti-region operations
One primary, local read replicas, a hot standby, and clients that read locally while routing writes to the current primary.
Open blueprint →Available nowSaaS multi-tenant
Shared tenant_id, database-per-tenant isolation, scoped auth, vault keys, usage events, and per-tenant restores.
Open blueprint →Have a workflow in mind?