What Everr is
Collect your traces, logs, and metrics as OpenTelemetry and query them with plain SQL, from your laptop, CI, and production.
Most observability tools are complex, built for organizations that can afford dedicated telemetry engineers and the time to wire everything up.
Everr is an observability platform for teams that need to ship fast: deep insight into your systems without losing days to setup or standing up a team to run it.
- Local-first. A desktop app runs on your machine and shows your telemetry with no cloud account needed.
- Configured as code. Dashboards, alerts, and runbooks are files in your repo, queried in SQL. See Observability as code.
- Open. It is all OpenTelemetry underneath, so nothing you set up is locked to Everr. See What's OpenTelemetry.
- For agents too. Your coding agent uses the same telemetry you do. See the MCP server.
Two places telemetry lives
Your code emits OpenTelemetry over OTLP, and it lands in one of two stores that share the same query model:
- The Collector is a service the desktop app runs on your machine. It holds your local telemetry for a fast feedback loop while you write and debug code.
- The Cloud is Everr's hosted backend. It holds CI and production telemetry in a shared, per-organization workspace.
A query you write against local traces reads the same against production ones.
Where telemetry comes from
- Local. Your app, tests, and wrapped commands send OTLP to the Collector on your machine. See Instrument your app.
- Production. Your services send OTLP to the Cloud, authenticated with an API key. See Send production telemetry.
- CI. The Everr GitHub App ingests your GitHub Actions runs. A run becomes a trace, its steps become spans, and verbose test output becomes a span per test. See CI insights.
Get started
Follow Install Everr and go from your first trace to your first alert.