Drop-in ingest paths
Accept Prometheus remote_write, Loki push, Elasticsearch _bulk, Syslog, and cloud drains.
Accept the protocols already connected to Loki, Elasticsearch, Prometheus, and OpenTelemetry while moving the durable data to one platform.

Compatibility endpoints let existing collectors and agents move without a flag-day instrumentation project.
Persist every signal as Parquet on the object store already used by the platform.
Keep a Prometheus-shaped metric workflow while using SQL for relational and cross-signal questions.
Begin with one process, then split roles without adopting a different product.
workflow
The safest migration keeps current collectors and validates each signal before retiring a backend.
Add molesignal beside the current backend without changing application instrumentation.
Confirm the data needed for alerts and investigations survives the path.
Use real trace IDs and service labels to verify the benefit of the shared plane.
Move alerting and dashboards only after the corresponding signal path is proven.
proof / shipped
Each advertised ingest path maps to a concrete receiver or endpoint in the current product.
Accept the protocols already connected to Loki, Elasticsearch, Prometheus, and OpenTelemetry while moving the durable data to one platform.