#221
B
Rank #209
Highlight
Full-stack observability platform combining session replay, logging, error tracking, and tracing in one product. Standout trait is unifying frontend session replay with backend traces/logs for full-stack debugging context.
59.5
/ 100
⚙ Full Stack
TypeScript/Go backend ingesting telemetry into ClickHouse (traces/logs/events) and PostgreSQL (metadata), with Kafka-adjacent queuing for ingest buffering. Self-hosting means running several heavyweight data stores side by side.
📈 Scaling Analysis
ClickHouse gives genuinely strong analytical-query scale for the telemetry volumes session replay tools generate, but the combined ClickHouse+Postgres+queue stack is resource-intensive to self-host at any real scale. Reasonable for small-to-mid teams; matching the hosted SaaS's scale requires significant ClickHouse cluster tuning.
🚀 Running on Nexlayer
Requires a backend pod, ClickHouse pod, Postgres pod, and a queue/cache pod, all wired via <podName>.pod:<port> (e.g. clickhouse.pod:9000); pull base images through mirror.gcr.io where available (ClickHouse's official image is on Docker Hub, so mirroring applies). This is one of the heaviest self-host footprints in the batch — expect to dedicate meaningfully more cluster resources than a typical app pod set.