Roadmap

The roadmap page now covers the full repository: retrieval, APIs and SDKs, Live, Durable, Fabric, SQL/WAL, agents, browsers, applications and shipping. See platform capabilities for the implementation boundaries.

Status labelsCopy Anchor Link

• Available: the named component is implemented in the code on dev, with source and supporting tests or recorded validation. Loams 0.1.0, the first release, ships as container images and packages you run yourself. Production readiness is separate.
• In progress: component or end-to-end integration is incomplete. Existing building blocks are listed explicitly.
• Planned: future service or contract, beyond the code that exists today.

Already implementedCopy Anchor Link

Hybrid retrieval, collection storage, hot tiers, cluster routing, REST, Flight SQL, Qdrant and Elasticsearch subsets, 18 native collection/document/Search RPCs, engine authentication (API keys, OIDC, Tailscale), 13 SDK runtimes, Live on an embedded store or TiKV with function deployments, Durable on SQLite, CloudEvents, a trigger edge, the connector registry, the House front, Loams Graph on the native port, Loams SQL and its SQL gate, SQL wire reads, the Loams Postgres control plane and Neon-compatible WAL, router verification tools, plugin/agent tooling, the Electron desktop, browser providers and release packaging all have implementation evidence.

That is distinct from a complete hosted service. Live tenancy and the Live/search bridge, Graph crash recovery, provisioning Postgres computes, the Durable TiKV store, connector execution, full factory orchestration, real-server mobile identity, and production readiness have their own remaining work.

Future servicesCopy Anchor Link

Functions, Jobs, Loams Git, SystemOne, retrieval-plan GraphRAG, Iceberg, Kafka compatibility, authorization and tenancy, and the complete BYOC/GitOps control plane remain future tracks. Their designs and implemented prerequisites are public; design intent does not determine availability by itself.

The design roadmap and implementation plans explain acceptance gates. Plan headers can lag code: check handlers, build features, tests and recorded validation before labeling a whole track. Dates are planning context, not delivery promises.