If you found this page, you probably used Baselime to debug AWS Lambda and are wondering what to move to. Here's the honest situation and where LogStitch fits — including where it doesn't.
What happened to Baselime
Baselime was a cloud-native, OpenTelemetry-based observability platform — logs, metrics, distributed tracing, error tracking, and high-cardinality event querying, with an AI copilot — and it was a favorite among serverless and AWS Lambda teams. In April 2024, Cloudflare acquired Baselime. Since then, Cloudflare has been folding the technology into its own platform, delivering observability features in the Cloudflare dashboard with the roadmap centered on Cloudflare Workers.
The practical upshot for AWS Lambda developers: Baselime's momentum has moved to Workers observability, not Lambda. If your workloads are staying on AWS Lambda, it's reasonable to look for a tool whose future is aligned with where your code actually runs.
Status as of July 2026, based on Cloudflare's own acquisition announcement and subsequent Workers observability roadmap. Check Cloudflare's and Baselime's current pages for the latest before making a decision.
What carries over — and what doesn't
Being straight about this matters, because Baselime and LogStitch aren't the same shape of tool.
What LogStitch doesn't replace
Baselime was a full OpenTelemetry platform: distributed traces, custom metrics, and querying across high-cardinality events from many services. LogStitch doesn't do OTel tracing or metrics, and it only looks at AWS Lambda logs in CloudWatch. If your Baselime usage leaned on cross-service traces and metrics, or you're migrating to Cloudflare Workers, LogStitch isn't the successor — Cloudflare's own observability is.
What LogStitch does cover — well
If what you actually did in Baselime day to day was read and debug your Lambda logs — find the failing invocation, follow a request across functions, spot the recurring error — that's exactly LogStitch's job, and it does it natively on your Mac without any pipeline to run.
At a glance
| For AWS Lambda | Baselime (now Cloudflare) | LogStitch |
|---|---|---|
| Status for AWS Lambda | Wound down — roadmap is Cloudflare Workers | Actively built for AWS Lambda |
| Model | OpenTelemetry SaaS platform | Native Mac log reader & debugger |
| Platform | Web app, any OS | Native macOS only (26.1+) |
| Pricing | Usage-based SaaS | One-time $49 / $99 |
| Data pipeline | OTel / SDK instrumentation | None — reads CloudWatch directly |
| Where your data lives | Baselime/Cloudflare SaaS | Your AWS account → your Mac |
| Distributed tracing & metrics | Yes — OpenTelemetry | No — logs only |
| Lambda logs by invocation | Yes | Yes |
| Stitch a request across functions | Yes — traces | Yes — log stitching (single account+region) |
| Error clustering & anomalies | Yes | Yes |
| Local MCP for Claude | No | Yes — 127.0.0.1, Keychain |
| Best for | OTel observability (esp. Cloudflare Workers) | Debugging AWS Lambda logs on a Mac |
Why LogStitch for orphaned Lambda users
1. Its future is AWS Lambda
LogStitch does one thing and isn't going to pivot to another platform: it reads and debugs AWS Lambda logs. If you're staying on Lambda, that alignment is the whole point.
2. Nothing to instrument, nothing to run
No OpenTelemetry collector, no SDK, no agent. LogStitch reads the logs Lambda already writes to CloudWatch with IAM read credentials, and groups them into invocations for you.
3. One-time price, data stays local
$49 or $99, once — no usage-based bill. Your logs stay in your AWS account and are fetched to a local SQLite database on your Mac; nothing is sent to a LogStitch server.
4. Invocation-first debugging, plus a local MCP server
Logs grouped by request ID, a request stitched across the functions it touched, structured JSON rendered as a formatted tree, errors clustered into ranked patterns, z-score anomalies — and a local Model Context Protocol server so Claude can query your logs on your machine, credentials staying in the Keychain.
Cross-function stitching works within a single AWS account and region; cross-account and cross-region correlation are not supported.
When LogStitch fits — and when it doesn't
FAQ
What happened to Baselime?
Is LogStitch a drop-in replacement for Baselime?
I'm moving to Cloudflare Workers — should I use LogStitch?
Does LogStitch need an OpenTelemetry collector or an agent?
How much does LogStitch cost compared to Baselime?
Still on Lambda? Keep debugging your logs.
Free 14-day trial. No card, no account, no pipeline. Point LogStitch at your AWS profiles and read your invocations, grouped and stitched, in under a minute.