All your telemetry.
One open platform.

Uptime, RUM, metrics, logs, traces, dashboards, alerts, SLOs and status pages — one open-source platform, OTel-native and ClickHouse-fast.

Open-source · OTLP in, answers out · Self-host in one line

p95 latency — api-common

p95:trace.http.request{env:prod} by service

api.cuesoft.io heartbeat

99.980% uptime · 90 daysp95 142 ms

Eight pillars. One query grammar.

Uptime & SyntheticsCatch downtime before your users do Website Analytics / RUMReal-user vitals & errors, cookieless MetricsExplore any metric in one grammar LogsLive-tail production in seconds APM / TracesSee where every slow request went DashboardsEvery signal, one synced grid AlertingPage on any signal, not just pings Incidents & SLOsSev workflow, honest error budgets

Point your OpenTelemetry SDK at us. Done.

Point your existing OTel SDKs at one endpoint — gRPC 4317 / HTTP 4318. Nothing proprietary in your code.

your servicesOTel SDK / collectorupstat ingest + storage

OTLP (traces · metrics · logs) + StatsD-compatible endpoint · browser SDK for RUM

How it works

Point your SDK at us

One endpoint — gRPC 4317 / HTTP 4318. No agents to babysit.

Send your first data

Scoped ingestion tokens — rotate with zero downtime.

See everything

Dashboards, traces, logs and alerts light up as data lands.

It looks like this — with your data.

availability · api-common

99.98%▲ 0.0%

p95 latency · api-common

142 ms▼ 8.0%

How teams actually use it.

Dashboards that stay in sync

11 widget types on one grid — timeseries, heatmaps, top lists, log streams, even markdown. Hover anywhere and every panel's crosshair lands on the same moment. Drag, resize, ship.

From alert to postmortem

Monitors watch any signal: metric thresholds, log patterns, trace latency, uptime. A firing alert declares an incident with sev levels and a timeline — and SLO burn rates keep paging honest.

Status pages people believe

Publish uptime and incident history to a page you control at your own slug. Subscribers get updates as your responders post them — the same timeline, no PR filter.

visitors · 24h

48.2k▲ 6.0%

p75 LCP

2.4 s▲ 18.0%

Analytics without the banner

Cookieless RUM: no cookies, no raw IPs, a daily-rotating salt. Sessions, web vitals and JS errors — with a GDPR posture you don't have to explain away.

We run on it. Publicly.

All systems operationalLast updated 31d ago

/status/upstat — our own public status page

Self-host — own your telemetry.

Telemetry is your most sensitive exhaust — queries, user paths, incident timelines. Keep all of it on infrastructure you control.

Every pillar ships: uptime, RUM, metrics, logs, traces, dashboards, alerts, SLOs, status pages
MongoDB ships in the box — one datastore, nothing else to stand up
Helm chart for Kubernetes when you outgrow compose

Self-host guide — step-by-step deploy docs →

$ git clone https://github.com/cuesoftinc/upstat$ cd upstat && docker compose up --build -d

Compose ships MongoDB; the Helm chart expects yours (MONGO_URI). All 8 pillars come up on :3000.

OTel SDK / collectoringest-gw :4317/:4318ClickHouse + Postgresweb (Next.js)

Cloud when you want it. Yours when you need it.

Feature	Upstat Cloud	Self-host
Managed OTLP ingestion
OTLP + StatsD endpoints
SSO / SAML
Own your data (compose)
Managed upgrades & backups
Community support

docker compose up -d# the whole platform, one fileSelf-host guide — step-by-step deploy docs →Query grammar — one grammar across all eight pillars →

For developers — come build it.

Go gRPC services · Next.js + React/TS · ClickHouse · OpenTelemetry

upstat is built in the open — and the interesting problems are open too:

Columnar telemetry storeQuery grammar & ASTAlert evaluation engineTrace sampling strategies

github.com/cuesoftinc/upstat — good first issues welcome CONTRIBUTING.md — local setup in one script, architecture guide included Discord — #upstat-lab on the CueLABS™ server

label: good first issue

#412  logs: brush-zoom on the histogram header
#397  slo: burn-rate sparkline in SLOCard
#385  otlp: gzip support on HTTP 4318 intake

Community

Public status — we run upstat on upstatLive uptime and incident history at upstat.cuesoft.io/status/upstat — we run upstat on upstat.View live →

Public roadmap →CueLABS™ — more open-source software from Cuesoft →

Questions, answered.

Yes. Point any OTLP exporter at ingest.upstat.cuesoft.io — gRPC 4317 or HTTP 4318. If it speaks OTel today, it works; nothing proprietary goes in your code.

OTLP in. Answers out.

Self-hosting is free forever — cloud pricing will be announced at GA.

All your telemetry.One open platform.