What you'd build if you had time. Without the Datadog bill.
$ self-hosted · OpenTelemetry-native · logs + metrics + traces
Three signals. One trace_id. Five seconds.
A trace, its logs, and the host metric for the same minute — natively correlated at the data plane, not stitched in a dashboard.
abc123· 4 spans · 280msSame trace_id=abc123 across all three. No copy-paste between tools.
vs the two paths everyone else takes
Commercial SaaS is correlated but expensive. OSS stacks are free but fragmented. molesignal is correlated and self-hosted.
- Commercial SaaS
- ~$2k+/mo · grows linearly
- OSS stack
- infra only
- molesignal
- infra only
Whether logs, metrics, traces share one storage layer.
- Commercial SaaS
- ✓ (their cloud)
- OSS stack
- 3 stores, 3 query langs
- molesignal
- Parquet + DataFusion
Jump from a trace to its logs to the host metric — without copy/paste.
- Commercial SaaS
- ✓ (paid)
- OSS stack
- manual trace_id copy-paste
- molesignal
- native (/web/correlation/*)
- Commercial SaaS
- their cloud
- OSS stack
- self-hosted
- molesignal
- self-hosted
One storage. One engine. One bill.
Parquet on object storage + DataFusion + Arrow. Three signals share the data plane.
Five minutes to your first query
One command. Postgres, MinIO, and molesignal standalone.
Building in the open
Every commit lands publicly. Every issue is searchable. Pre-1.0, every voice still moves the roadmap.
Be the first contributor — open an issue or PR.
Show support and stay in the loop. The repo is the project's source of truth and the fastest way to file an issue.
A small space for design partners and contributors to chat. Drop your email at /design-partner and we'll send an invite.
Be early. Be heard.
We're recruiting 5–15 mid-size teams to help shape v1. Weekly founders chat. Real influence on the product. Free.