Logs, metrics and traces linked from the alert to the request, release and log line behind it, an AI SRE that shows its evidence, and the CO₂e of every service. Priced only by the data you send, with a monthly cap that can keep a sample instead of surprising you.
Free: 10 GB of ingest a month and 7-day retention. No card to start.
One pane of glass
Logs, metrics and traces from the browser down to the database land in one place, get linked to each other, and reach an AI SRE that shows its evidence and asks before it acts.
Illustrative visualisation with example values, not live data.
Correlation
A log line opens the request that wrote it. Errors carry a sample trace. Releases sit on the same charts as latency and 5xx rate, so you follow one story from the browser down to the database instead of five tabs.
Signals that belong to the same request stay connected, so opening an alert shows the related logs, traces and release without a hunt.
When an incident opens, the AI SRE starts from the assembled picture, not an isolated alert, and lists its evidence and what it ruled out.
Illustrative visualisation with example values. Hover, focus or tap a layer to see what it covers.
The platform
Pick an area to see how it works. Each animation is an illustration with example values.
Search log lines, see volume by level, and open the trace behind any line. Logs, traces and metrics stay linked.
Explore Logs →Traffic, errors and latency for every back-end service, with traces that show where the time went.
Explore Traces & APM →Start from built-in templates, import JSON, and keep the charts you check every day in one place.
Explore Metrics & dashboards →Rules are checked every minute, with state and a timeline of every notification sent.
Explore Alerts →Declare an incident, follow its timeline, and keep the ticket in Jira or ServiceNow linked to the evidence.
Explore Incidents →Set a service-level objective and get burn-rate alerts while there is still error budget left.
Explore SLOs →Synthetic checks for availability, latency and TLS expiry, on the same alert channels.
Explore Uptime →Core Web Vitals, JavaScript errors and fetch spans that link to server traces (browser SDK in beta).
Explore Front end →Cluster inventory with pod-level drill-down, OOMKills and rollout status from a minimal Helm agent (beta).
Explore Kubernetes →See which machines and data stores are healthy, and how they talk to each other.
Explore Infrastructure →See posture findings for your clusters next to the same traces, logs and metrics.
Explore Security →Calls, tokens, latency and reported cost per model from OpenTelemetry gen_ai spans. Prompt and completion text are not read or shown.
Explore LLM observability →The AI SRE lists what it found and what it ruled out. Proposed actions wait for your approval.
Explore AI SRE →Teammates read alerts, compare traces and draft analyses. Anything that changes a system waits for your approval.
Explore AI teammates →Node.js and NestJS have a first-class SDK. Java, Python, Go, Ruby and others send standard OpenTelemetry to your ingest URL.
Explore Runtimes →Energy and emissions on the same telemetry, every figure labelled measured or estimated, with its uncertainty.
Explore Carbon →Escalation policies and shift handoff, so an alert reaches someone who can act on it.
Explore On-call →Why Owlpane
One OpenTelemetry-native product where signals link to each other — with limits stated plainly on every comparison page.
Priced by GB ingested, not per host, per seat or per indexed event. Starter includes 100 GB; a spend cap samples instead of surprising you at month end.
Cost calculator →A log line opens the request that wrote it. Errors carry a sample trace. Releases sit on the same charts as latency and 5xx rate — so you follow one story, not five tabs.
See it working →OTLP and Prometheus remote write. Send a copy beside Datadog, Grafana or your self-hosted stack, and keep your data portable.
Integrations →Cluster inventory with pod-level drill-down, burn-rate SLO alerts, and CO₂e per service and job — measured or estimated, always labelled.
Owlpane Carbon →Compare honestly: Grafana stack · Bronto · Logz.io · Datadog · Checkly
Documentation
Quickstart, OpenTelemetry ingest, Node.js and Kubernetes agent install — the same paths linked from the console setup wizard.
Browse documentation →OpenTelemetry, Node.js, NestJS, Kubernetes, PostgreSQL, Redis, Prometheus, Grafana, Slack, PagerDuty, Opsgenie, Jira, and ServiceNow each have a documented connect path. See all integrations →
See it working
Every screen below is a screenshot of the Owlpane console. Watch what each one tells you, or click a step to jump to it.
Traffic, errors and latency for every back-end service, the map of who calls whom, and the errors grouped by what went wrong.



A cluster you can read in five seconds: what is running, what needs attention and what is failing, worst first.

Kubernetes, databases, data stores, messaging, hosts, network devices and cloud in one overview, with what is and is not monitored stated plainly.

Operational energy and gCO₂e with uncertainty bands, ranked services, and regression markers — from the same OpenTelemetry data you already collect.

Search what your services logged, see volume by level, and jump from any line to the request it belongs to.

Page loads, JavaScript errors and Core Web Vitals from real sessions, not a synthetic test from one region.

Rules checked every minute against live telemetry, with one message when something fires and one when it resolves, plus SLOs that warn while there is still budget to save.


Named sets of charts for a wall display or a weekly review, each chart one click from the requests behind it.

Calls, tokens, latency and reported cost per model, from standard OpenTelemetry gen_ai spans. Prompt and completion text are not read or shown.

The problem
"What just broke, and why?" shouldn't take five browser tabs and a Slack thread to answer.
APM here, log search there, uptime somewhere else, on-call in another tab. Nothing shares a trace ID.
Per-host and per-seat bills that go up exactly when your product is finally getting traction.
You know what Kubernetes costs. You don't know why a pod OOMKilled at 2am until a customer tells you.
Too noisy to page on, too quiet to catch the thing that mattered. So everyone mutes the channel.
Products
Start with one product and add the rest when you need them — same ingest key, same bill.
Applications
Traces, service map, errors grouped by release, database queries, cron jobs and queues.
Learn more →Infrastructure
Cluster explorer, node and pod detail, network dependency map, security posture and safe restart/scale. Agent in beta.
Learn more →Infrastructure
Hosts, PostgreSQL / MySQL / MongoDB, Redis-compatible caches, Kafka and RabbitMQ, SNMP network devices, cloud.
Learn more →Telemetry
Log search correlated with traces, attribute search across spans and logs, redaction when shown or exported.
Learn more →Front end
Web Vitals, JS errors, session replay and synthetic uptime checks. Browser SDK in beta.
Learn more →Reliability
Alert rules, SLOs with burn-rate alerts, channels, and incidents in Jira or ServiceNow.
Learn more →Telemetry
Dashboards, a metrics explorer, templates, and Grafana-compatible reads.
Learn more →Intelligence
Ask search, investigations, LLM usage and cost, coding-agent activity, read-only MCP.
Learn more →Impact
CO₂e per service, endpoint and job, with waste separated from useful work. On every plan.
Learn more →Solutions
Each use case is built from features that ship today — and says where Owlpane is narrower.
From the alert to the request, release and log line behind it
Learn more →Know within minutes whether the last deploy made things worse
Learn more →Real-user performance, uptime checks and the backend behind each click
Learn more →Cluster inventory, pod health, network paths and safe restarts
Learn more →Cron jobs and queue workers as runs you can see and alert on
Learn more →Calls, tokens, latency and cost of the models your product uses
Learn more →Traces, logs, metrics, uptime and alerts on one bill you can forecast
Learn more →Developers, SRE and platform, engineering leaders — and honest comparisons for Datadog, Grafana, Bronto, Logz.io, Checkly and more.
All solutions →Investigate
A deploy, a latency jump, an error spike, a slow query and a backed-up queue are one story. In Owlpane each of them already links to the exact requests, errors and logs behind it.
PreviewIllustrative incident. Each signal exists in the product today on its own page, linked to the requests behind it; the Incident timeline page puts deploys, alerts, uptime results and markers on one axis.
Setup
One call, before your app boots. It does nothing until you point it at an ingest URL — so it's safe to leave in code that hasn't gone live yet.
@Cron and BullMQ jobs with one install line, and any other job through owlpane.job()owlpane.setUser()), for per-customer debuggingimport { owlpane } from "@owlpane/node";
owlpane.start({
service: "payments-api",
release: process.env.GIT_SHA,
});
// that's it — every request, query,
// and outgoing call is now traced.
# any language with an OpenTelemetry SDK
OTEL_SERVICE_NAME=payments-api
OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.example.com
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20<ingest key>
# open standard, portable by default
helm install owlpane oci://ghcr.io/owlpane/owlpane-agent --version 0.3.7 -n owlpane \
--set endpoint=https://ingest.example.com \
--set cluster.name=production-eu
# read-only cluster access; setup guide in the console
Ask, don't hunt
Plain-language search, saved investigations and a read-only MCP server for your own assistants. They answer and link to the evidence; they never change anything in your systems.
The charts under each answer are the same aggregates as the rest of the console, so you can check the answer instead of trusting it.
Save notes, console links and search URLs for an incident or a root-cause write-up, in one board your team can reopen.
Let a coding assistant query topology, flows, incidents and carbon. Read-only by design: there is no auto-remediation.
Calls, tokens, latency and cost from OpenTelemetry gen_ai spans. Prompt and completion text are not read or shown.
How it works
Spans, logs and metrics over standard OTLP.
Key resolves the tenant. Secrets are redacted when telemetry is shown or exported.
Per-tenant rules enforced in the database. Designed for an EU region; the live cell is not confirmed yet.
Drill from any chart to the requests behind it.
Drop in the SDK, or point any existing OpenTelemetry exporter at Owlpane's ingest URL. Works with the OpenTelemetry you already run.
Telemetry lands in a tenant-isolated cell. Tokens and secrets are redacted when telemetry is shown or exported.
Dashboards, traces, and alerts are there immediately — no query language to learn, no dashboard to build first.
The carbon layer joins the same telemetry with node energy and hourly grid intensity to attribute CO₂e per service, endpoint and job.
A free workspace and an ingest key from Setup. Then either @owlpane/node, any OpenTelemetry SDK or Collector, or the Kubernetes agent.
Auth headers, cookies, query strings, emails, bearer tokens, card-like numbers and password or token values are redacted when telemetry is shown or exported. This site does not claim they are removed before storage. The Kubernetes agent has no permission to read Secrets, and the console shows ConfigMap key names only.
Free pauses new ingest above 10 GB a month until you upgrade to Starter. Starter and Business honor the spend cap you set by sampling, so the bill can't jump.
Designed for an EU region, isolated per tenant in the database. The query window is 7 days on Free, and 30 days for traces and logs and 90 days for metrics on Starter and Business. Those figures are not physical deletion unless the lake retention sweep is turned on. Standard OTLP out if you ever leave.
Owlpane Carbon · on every plan
Monitoring shows latency, errors and cost. Nothing tells a developer that this endpoint or this job made the software use more energy. Owlpane Carbon adds exactly that — on the telemetry you already send.
Illustration with example values. In the console every figure shows whether it was measured or estimated, with its uncertainty.
CO₂e per request and per run, following the ISO-standardised Software Carbon Intensity method (ISO/IEC 21031:2024). Version 1 is duration-weighted — the bias is stated on the figure, not hidden.
Each service is compared with the previous equal window. When its energy or CO₂e rises past your threshold (20% by default) an alert fires, like an error regression. A window comparison, not a per-deploy attribution.
Reserved-but-idle capacity reported as its own figure, with the workloads responsible — energy you pay for that does no work.
Hardware counters where they exist, published factors where they don't. Mode, factor-set version and uncertainty band on every number.
Grid intensity by hour (hourly for EU zones where ENTSO-E data is available) shows when the grid is cleaner. Hints only — Owlpane does not schedule your workloads.
How much telemetry you keep and the storage energy it implies — monitoring's own footprint, as an order-of-magnitude estimate rather than a measurement.
The method: SCI = (E × I + M) per R — energy times grid intensity, plus embodied hardware, per request. Grid intensity from hourly ENTSO-E when configured, with a versioned static factor table as fallback. The methodology is published and linked from the console Factors view.
Available on every plan, Free included, in the product console (/observability/carbon). Metered hardware validation on your own cluster is recommended before operational targets — see the published methodology. The Carbon product page →
Switching
Because ingest is standard OpenTelemetry, you can send a copy of your telemetry to Owlpane without touching your current tool. Here is what that looks like, including what you would give up.
Any OpenTelemetry instrumentation you already have. Your Datadog agent and account can stay in place while you compare.
One bill priced by data, with a cap that samples instead of surprising you. No per-host or per-module line items.
Breadth. Datadog has a much larger integration catalogue, plus network and security products we do not offer. Apps on the proprietary tracer need OpenTelemetry first.
Sentry for what it does best, if you like. Send your backend traces and logs to Owlpane next to it.
Errors grouped by the release that introduced them, with a sample trace, beside your database calls, jobs, Kubernetes state and uptime checks.
Depth on the front end. Session replay and mobile crash reporting are thinner here, and in beta.
Prometheus remote write works today, and Grafana can read Owlpane metrics through a Prometheus-compatible endpoint.
One managed product instead of four to operate, with logs, traces and metrics that link to each other.
Ecosystem. PromQL support is a read endpoint, not full parity, and there is no library of community dashboards.
Datadog, New Relic, Grafana, Grafana Cloud, Loki, Tempo, Dash0, Better Stack, Bronto, Logz.io, Amazon CloudWatch, AWS, Sentry, Dynatrace, Kubeshark, Checkly, PagerDuty, SigNoz, Kubernetes, OpenTelemetry, Prometheus and other names are trademarks of their respective owners. Owlpane is not affiliated with or endorsed by them. Comparisons reflect publicly available information as of September 2026 and our own product today, and may change.
Add one exporter to your OpenTelemetry Collector. Your current tool keeps working, and Owlpane receives the same data.
Start with one service or ten percent of traffic, compare the answers you get during a real incident, then decide.
exporters:
otlphttp/owlpane:
endpoint: https://ingest.example.com
headers:
Authorization: "Bearer ${env:OWLPANE_INGEST_KEY}"
service:
pipelines:
traces:
exporters: [your_current_exporter, otlphttp/owlpane]
Pricing
Unlimited users, projects, hosts, clusters and alert channels on every plan — shared platform, EU data region. You pay for data, and nothing else.
Prices exclude VAT and other taxes. Billed in the currency you choose.
Free is Lake storage only — realtime modes start at Starter.
Get started free$290 billed yearly — you save $58
$880 billed yearly — you save $176
Lake keeps 30 days. Realtime keeps 7 days: the plan base plus an access fee of $20/mo, including 100 GB, then $0.22/GB ($0.16 past 1 TB). Lake+Realtime is both of those bills. A 14-day window doubles the realtime charge. Realtime does not keep history past the hot window.
Free is up to 10 GB a month. Starter is $29/mo including 100 GB, then $0.35/GB ($0.25 past 1 TB). Business is that same 100 GB plus $59/mo for SSO, SCIM and audit ($88/mo). The storage mode follows the selector above.
You are billed for what the ingest gateway keeps, not for what is stored afterwards, so later retention does not change the meter. Past 2 TB kept in a month, ingest is sampled and only the kept share is billed; at 4 TB kept, new ingest stops until the month resets.
Questions
@owlpane/browser SDK sends Core Web Vitals, errors and fetch spans that link to server traces when you propagate trace headers.@owlpane/node), with tracing for NestJS @Cron and BullMQ jobs and an owlpane.job() wrapper for other background work. A browser SDK (@owlpane/browser) is in beta. For Java, Go, Python, Ruby and anything else, use the standard OpenTelemetry SDK pointed at your ingest URL — it works with Owlpane right now; thin Owlpane wrappers for Python, Go, Java and Ruby are still in progress.Ready when you are
Create a free workspace in minutes. Need Business, Enterprise, yearly billing or help onboarding Carbon on a large fleet? Email hello@owlpane.com and tell us about your stack.
Trust
What we build for, what is true today, and what is still in progress.
This page is a plain summary, not a contract. The security summary is a plain summary, not a contract. A draft data processing agreement (not in force, not a contract) is at /dpa. The sub-processor list is a draft.
Security reports: see security.txt. Anything else: hello@owlpane.com.
Status
No incidents recorded. When something breaks, it is posted here first.
The API row is a real request made from your browser just now. Everything else on this page is updated by hand during an incident, so it can lag reality by a few minutes. To hear about incidents by email, write to hello@owlpane.com from your account address.
OperationalAll systems operationalAPI answered a live health check just now. DegradedSome systems are degradedThe API answered, but reported a problem with a dependency. Could not checkLive check unavailableYour browser could not reach the API. If you rely on Owlpane, check the incidents below or contact us.