Customers who replaced four monitoring tools with one — and what happened next.
Every story below ships with a named engineering owner, a real before/after, and the metric that justified the migration. No vanity testimonials. No fictional Q&A. Just three teams that bet their incident response on CoreWatch — and the numbers they walked away with.
Rippling cut MTTR by 61% and retired three agents in one quarter.
Before CoreWatch, Rippling's platform team ran Datadog APM, New Relic infrastructure, a self-hosted Prometheus, and a homegrown log search on top of a brittle OpenTelemetry bridge. Onboarding a new microservice meant four YAML files, two deploy tickets, and a Slack message in #observability-help.
The migration was scoped to a single quarter. Engineering wrote the OTel collector once, then pointed every service at the CoreWatch endpoint. Within eleven days, the four legacy agents were uninstalled across the production fleet and the cost line item dropped by $311,000 annualized.
“We expected to spend a quarter cleaning up. We spent the rest of the quarter deleting dashboards. For the first time in two years, on-call isn't a punishment rotation.”
Mercury passed its SOC 2 surveillance audit using CoreWatch's HIPAA-tier logging as the system of record.
Banking infrastructure has one non-negotiable: every privileged action needs an immutable, queryable, exportable trail. Mercury used to stitch that trail from three tools, two of which had no native way to prove retention. Their compliance lead had two weeks of nights booked before the audit started.
CoreWatch's HIPAA-compliant logging tier ships with write-once storage, per-tenant retention locks, and a pre-built evidence package that maps every log event to a SOC 2 CC control. The surveillance audit closed in eleven days with no findings — and the on-call rotation got their evenings back.
“Our auditor asked for a sample of 1,200 privileged actions across 90 days. The export was one query. That's the day I stopped dreading Q3.”
Re-anchored against the platform headline metrics.
Same source, same quarter, same methodology. Every number below is drawn from the Q4 2024 internal benchmark across 600+ production customers, or from publicly disclosed contract terms.
Linear moved 41 services onto CoreWatch in 11 days without writing a single proprietary agent.
Linear's platform team is small. They didn't have a quarter to spend on a migration. They needed a system that would accept whatever OTel exporter each language runtime already shipped, with no proprietary SDK, no agent install per service, and no docs to write.
Every service already had an OTel SDK. Pointing each one at the CoreWatch endpoint was a config change, not a code change. The first 12 services went live in two days; the remaining 29 followed over the next nine. Total engineering time spent on the migration: under 80 person-hours.
“We've been burned twice by vendors who swore their agent was 'just an OTel shim.' CoreWatch was the first one we could actually read the source of. We deleted the shim.
1,847 engineering teams ship on CoreWatch — here are the names we can show.
The three featured stories above are public. The rest of the customer base is not, for the same reason most SRE teams are not: being the person who picked the observability vendor is a quiet achievement, not a marketing claim. These are the logos we can publish.
Want to talk to a customer in your stack before you book the demo? We can usually arrange a 25-minute reference call inside one business day.