Runnable source
Build the Rust binary, run the Docker Compose sandbox, and inspect the web and API surfaces.
The source, architecture, issues, roadmap, maturity gaps, and contribution history remain public. Run it yourself, verify the claims, and shape what reaches 1.0.
Be the first contributor — open an issue or PR.
Control comes from source access, portable protocols, owned storage, visible decisions, and a product that remains runnable without a hosted control plane.
Build the Rust binary, run the Docker Compose sandbox, and inspect the web and API surfaces.
Persist Parquet on your S3-compatible or cloud object store instead of a proprietary hosted store.
Follow issues, changes, roadmap, architecture notes, and contribution history in public.
The stewardship page explains the boundary between open-source, Enterprise support, and future Cloud work.
proof / shipped
The open-source repository is the product, not a thin agent feeding a closed backend.
Keep exploring
Logs, metrics, and traces share physical storage, time indexing, tenant enforcement, and a vectorized query engine. Profile metadata joins the same tenant and time plane while lossless pprof archives remain portable on object storage.
Both paths should lead to the same conclusion about what is shipped and what still needs production hardening.