Product / features
Capabilities, without the brochure language.
Use this as a concise capability map. “Documented”, “tested”, and “version-sensitive” are deliberate labels; follow the docs before depending on a feature in production.
Document API
documentedCollections, familiar query operators, updates, pagination, and aggregation for application data.
- — MongoDB-style document model
- — JavaScript and TypeScript SDK
- — Collections and indexes
Storage engine
implemented / pre-alphaA Rust-based engine with WAL and checkpoint paths exposed as part of the V2 architecture direction.
- — Rust engine
- — WAL and checkpoints
- — Persistent local storage
Search and indexing
available in test pathsSecondary and text indexing are available in documented V2 test paths; workload-specific behavior matters.
- — Secondary indexes
- — Text index
- — Compaction and recovery paths
Operations
documentedRun locally with Docker, connect through the dashboard, or review managed deployment options.
- — Docker quickstart
- — CLI package
- — Managed provisioning
Transport
version-sensitiveThe official docs describe JavaScript and TypeScript SDK, gRPC, and REST access paths. Verify endpoint details against the docs for your version.
- — JavaScript / TypeScript SDK
- — gRPC endpoint
- — REST endpoint
Recovery
tested / pre-alphaWAL replay and recovery are part of the documented V2 test surface; durability semantics depend on the configured path.
- — WAL replay
- — Crash-recovery test artifacts
- — Checkpoint lifecycle
Next step
Match the capability to the workload.
The developer hub covers the local path. The architecture page explains boundaries. The docs remain authoritative for API and version details.