Rootprint – Self-hosted log search built with Svelte, Hono and Quickwit
Quickwit-powered S3 search, but Grafana Loki and SigNoz already own this space.
A very minimal standalone log ingestion and querying platform with builtin client library for instrumentation.
Honest learning project in a solved category — Grafana Loki and Datadog already dominate.
Backend developers, DevOps engineers learning distributed systems
Grafana Loki · Datadog · Splunk
It’s a small Go-based system where logs come in over gRPC, land in memory first, then flush into local storage and optionally S3-compatible object storage. I also added a simple query language plus a small UI to inspect log occurrences over time. This wasn’t built because I think the world needed “another logging system” or because I’m an expert here. I mostly wanted to learn by building something end to end: ingestion paths, storage layering, querying, retention, auth/TLS, and some UI work.
Repo: https://github.com/Saumya40-codes/LogsGO
I’d genuinely appreciate feedback, including “this design is wrong for X reason” type feedback. If parts of it feel overengineered / naive / badly thought through, that’s useful for me too.
Quickwit-powered S3 search, but Grafana Loki and SigNoz already own this space.
gRPC from SQL via server reflection—no proto files or codegen needed.
Time-travel SQL on append-only storage, but PostgreSQL temporal tables already exist.
Sits between logs and Datadog—eliminates retry noise, saves 60–90% ingestion volume.
PostHog alternative with Apache Iggy, Delta Lake, and 3-tier query architecture—handles scale differently.
Fills the kubectl logs gap—queries pods across namespaces when aggregation fails.