monoscope vs Workers Observability

Baselime is now part of Cloudflare. Here’s how monoscope compares.

Cloudflare acquired Baselime in 2024, and its features now live in Workers Observability, built for apps on Cloudflare Workers. monoscope works with any stack through OpenTelemetry, keeps every request and response, and its AI SRE opens the fix.

Side by side

What you get, and what it costs

monoscope compared with Workers Observability
monoscopeWorkers ObservabilityCloudflare, formerly Baselime
Request and response bodies, in and out Every call, unsampled on paid plans —
Breaking changes in third-party APIs Caught in the stored responses Not in public docs
AI sees the full request Yes —
AI investigates the root cause Built in, answers in Slack —
Pricing
  • $29/month for 20M events
  • then $1 per million
  • Bodies and metrics included
  • No host or indexing fees
  • Free: 200k log events a day, 3-day retention
  • Paid: 20M events a month, then $0.60/M
  • 7-day retention
  • New pricing from Dec 1, 2026
Open source and self-hosting AGPL-3.0, free to self-host —
Data in your own bucket Session replays in your S3 today, +$199/month —
Coverage Logs, traces, metrics, errors and session replay Logs and traces for Cloudflare Workers
Sources and assumptions

Checked against Workers Observability’s public pricing pages and docs in October 2026. List prices, annual billing where offered. — means we couldn’t confirm it from public docs. Spotted something out of date? Email [email protected] and we’ll fix it.

Which one fits your team

Choose monoscope if

  • Your services run on servers, containers or other clouds, not only on Workers
  • You need request and response bodies kept for 30 days or more
  • You want an AI SRE that investigates and opens pull requests

Choose Workers Observability if

  • Your whole app runs on Cloudflare Workers and you want observability in the same dashboard
  • A few days of log retention is enough for you

Already on Workers Observability?

Run monoscope next to it for a week or two, compare which errors and API changes each one catches, then move your services over. An engineer from our team can help.

Know what happened. Prove it.