ClickStack screenshot thumbnail

ClickStack

ClickStack is an open-source observability platform that unifies logs, metrics, traces, session replays, and errors in one searchable interface, so engineers can move from an alert to the exact request that broke in minutes. Search uses an intuitive full-text and property syntax (for example level:err), with SQL available when a question needs full analytical power. Live tail streams fresh logs and traces as they arrive, and event deltas surface anomalies by comparing current behavior against earlier windows. Dashboards chart high-cardinality events without a complex query language, and alerts can be created in a few clicks from any search or chart. Session replays connect a user's browser experience to the backend traces and database queries behind it, giving full-stack visibility from click to query. Native JSON string querying handles nested payloads, and the schema-agnostic design works on top of an existing ClickHouse schema instead of forcing a new one. OpenTelemetry is supported out of the box, with SDKs and collectors for Kubernetes, JavaScript, Python, Java, Go, Ruby, PHP, .NET, Elixir, and Rust. The all-in-one Docker image bundles the interface, ClickHouse, the OpenTelemetry Collector, and supporting services on port 8080, and a terminal CLI serves engineers who prefer the shell. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Deploy
SigNoz screenshot thumbnail

SigNoz

With over 31,000 GitHub stars and native OpenTelemetry support that eliminates vendor lock-in from day one, SigNoz delivers full-stack observability covering metrics, traces, and logs in a single pane of glass without the per-host pricing model of commercial APM platforms. The platform ingests telemetry data through the OpenTelemetry Collector, supporting auto-instrumentation for Java, Python, Node.js, Go, Ruby, PHP, and .NET applications with zero code changes required for basic tracing. ClickHouse serves as the columnar storage backend, providing fast aggregation queries over billions of spans and log lines with configurable retention policies and tiered storage. The distributed tracing view renders flame graphs and Gantt charts showing request flow across microservices with latency breakdowns, error rates, and p99 percentile calculations. Custom dashboards support PromQL and ClickHouse SQL queries with time-series charts, bar graphs, tables, and value widgets. The log management pipeline supports structured and unstructured logs with full-text search, log pipelines for parsing and enrichment, and correlation with traces via trace IDs. Alert rules can be configured on any metric or log query with notification channels including Slack, PagerDuty, OpsGenie, webhooks, and email. The exceptions monitoring module automatically groups and tracks application errors with stack traces, occurrence counts, and first-seen timestamps. Service maps visualize inter-service dependencies with real-time latency and error rate overlays. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed with an enterprise edition available.

Deploy
Monoscope screenshot thumbnail

Monoscope

Across logs, traces, and metrics, Monoscope gives engineering teams one self-hosted workspace for finding what broke, asking questions in plain English, and hearing about problems before users do. Start in the Explorer: search events with KQL or an Ask AI prompt, flip between log rows, bar and line charts, log patterns, and sessions, and narrow results with facets for service, level, and HTTP status. Open any span to read its attributes, then follow the full trace across services in a waterfall, timeline, or map view. Live Tail streams new events as they arrive, and the Service Map draws every dependency with its error rate, latency, and requests per second. Build dashboards from widgets with copyable KQL and SQL, then set scheduled monitors with warn and alert thresholds, cron monitors, and uptime checks. An Issues inbox gathers API changes, errors, and log patterns so each one can be acknowledged, archived, or marked as spam, while Reports send scheduled summaries by email. Telemetry arrives over OTLP gRPC on port 4317 from OpenTelemetry SDKs and collectors. The monoscope CLI emits JSON for scripts, and an MCP server at /api/v1/mcp lets Claude, Cursor, and Cline search events and triage issues. Natural-language search uses the OpenAI-compatible model you configure. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Deploy
Quickwit screenshot thumbnail

Quickwit

With over 11,000 GitHub stars and now backed by Datadog while remaining fully Apache 2.0 licensed, Quickwit delivers the search performance Elasticsearch users expect at a fraction of the infrastructure cost by moving the index to object storage instead of expensive local SSDs. The Rust-based engine, built on the Tantivy search library with SIMD-accelerated vectorized processing and zero garbage collection overhead, achieves sub-second search latency directly against Amazon S3, Azure Blob Storage, Google Cloud Storage, or any S3-compatible backend like MinIO and Ceph. The Elasticsearch-compatible REST API covers ingest, search, query DSL, and aggregations, enabling existing log shippers including Vector, Fluent Bit, and Syslog to migrate without rewriting configurations. Native OpenTelemetry Protocol endpoints accept logs and traces via gRPC, while Jaeger integration provides a drop-in distributed tracing backend. Ingestion from Apache Kafka, Amazon Kinesis, and Apache Pulsar supports streaming pipelines with multi-index partitioning, and the schemaless JSON indexing mode eliminates the need for upfront schema definitions. Stateless searchers and indexers scale horizontally on Kubernetes or bare metal, with a control plane that distributes indexing tasks and a janitor that manages retention policies and GDPR-compliant deletions. The built-in web UI displays search results and cluster state, while the official Grafana data source enables log exploration dashboards. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Deploy
Jaeger screenshot thumbnail

Jaeger

Created by Uber Technologies and graduated as the seventh CNCF top-level project in October 2019 with over 23,000 GitHub stars, Jaeger has become one of the most widely deployed open-source distributed tracing platforms, processing billions of spans per day in production environments at organizations including Uber, Red Hat, and Shopify. Version 2 rebuilt the platform on the OpenTelemetry Collector framework, inheriting its extensible pipeline architecture while implementing Jaeger-specific features as extensions and components, enabling seamless integration with the OpenTelemetry ecosystem through native OTLP protocol support. The platform stores traces in Cassandra 4.0+, Elasticsearch 7.x/8.x, OpenSearch 1.0+, ClickHouse, or the embedded Badger database for development setups. Three sampling strategies control trace volume: head-based sampling with constant, probabilistic, and rate-limiting modes, tail-based sampling using the OpenTelemetry Collector processor that evaluates complete traces before storage decisions, and adaptive sampling that dynamically adjusts probabilities based on observed traffic patterns. Service Performance Monitoring computes RED metrics directly from spans, displaying request rates, error rates, and latency percentiles in the Monitor tab with drill-down from aggregate service views to individual traces. The web UI provides trace search with multi-field filtering, trace detail views with span timeline visualization, trace comparison across services, and dependency graphs mapping service relationships from actual traffic. Deployment options range from a single all-in-one binary for development to distributed collector-ingester-query configurations with Kafka intermediate buffering for production scale. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Deploy
Apache SkyWalking screenshot thumbnail

Apache SkyWalking

An open-source application performance monitoring platform for microservices, Kubernetes, and service meshes, Apache SkyWalking draws the live service map and ties slow requests to their traces, logs, and metrics. Agents cover Java, .NET Core, PHP, Node.js, Go, Lua, Rust, C++, browser JavaScript, and Python, and OpenTelemetry, Zipkin, Prometheus, Zabbix, and Telegraf data can be ingested too. Start at the service topology map, follow a request through the trace waterfall, then drill into the instance and its API dependencies. When the cause is inside the code, trace profiling, async-profiler, Go pprof, eBPF, and network profiling render flame graphs and process graphs in the same console. The Rover eBPF agent profiles Kubernetes workloads for CPU and network problems, and Istio and Envoy service meshes, including Istio Ambient, report into the same dashboards. Alarm rules target a service, deployment, or API, and alarms and telemetry can be forwarded to third-party systems. Metric and log analysis rules hot-update at runtime without a restart, and a live debugger shows what each rule stage receives and produces. An AI assistant answers plain-language questions with charts, topology, and traces from live data, using an OpenAI-compatible or Amazon Bedrock model you configure, and an MCP connection serves your own AI client. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Pinpoint screenshot thumbnail

Pinpoint

When checkout slows to a crawl somewhere across forty services, Pinpoint draws you the map of what is actually talking to what and where the time went. The ServerMap renders your whole topology live: services, databases, message queues, and external APIs as nodes whose edges carry transaction counts and error rates, so the unhealthy dependency announces itself visually. Click a node and the scatter chart plots every request against its response time; drag across the suspicious cluster and the CallStack opens those exact transactions at code level, method by method, SQL statement by SQL statement, until the bottleneck has nowhere to hide. The Inspector watches each application's CPU, memory, garbage collection, TPS, and JVM arguments, while realtime active-thread charts show stuck work as it happens. Agents attach to Java, PHP, and Python applications without changing a line of code, and applications already instrumented with OpenTelemetry send their traces straight in over OTLP. Group applications into services so each team sees its own Service Map, then arm alarm templates for slow counts, error rates, and thread saturation before users notice. Error Analysis gathers exceptions and error logs grouped by route, and URI metrics rank your hottest endpoints by cost. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy
Rootprint screenshot thumbnail

Rootprint

A year of searchable logs and traces no longer needs a metered logging service, because Rootprint keeps the whole index in a storage bucket you already own. A search matches any word on any line, since every log is indexed in full and no service name, stream, or label is needed first. A frequency histogram, one-click field filters, and saved views narrow the results, a fold mode collapses repeated lines, and exports arrive as NDJSON, CSV, or plain text, or as a share link. Open a trace from the log that emitted it, or paste a trace ID, and a waterfall shows per-span timing, attributes, events, and database calls grouped by query, with each span linking back to its logs. The trace explorer charts span volume, error rate, and p50, p95, and p99 latency, ranks the busiest operations, and filters spans by service, duration, and status. Every service gets its own page with request rate, error rate, operations, dependencies, and errors. Data arrives over OpenTelemetry from the Collector, Vector, or Fluent Bit, through a plain HTTP gateway, or by pulling from Kafka, Kinesis, or SQS, with guided setup for nine integrations. Indexes can live in S3, Google Cloud Storage, R2, MinIO, or Azure Blob. Teammates sign in with Google, GitHub, or any OpenID Connect provider, and scoped API keys serve scripts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy