Embrace has expanded its product suite beyond mobile with the introduction of Real User Monitoring (RUM) for Web.
Built on OpenTelemetry and informed by Embrace's foundational Mobile RUM product, the launch reinforces the company's dedication to reliability from the perspective of end-users, regardless of screen.
The expansion is supported by Embrace's existing investors NEA, Greycroft, AV8 (Allianz), and Eniac who back the company's Web RUM initiative and vision to scale the only user-focused observability platform based on the OpenTelemetry standard.
Embrace provides out-of-the-box solutions to help engineers make sense of site performance data and its impact on users. Teams can connect telemetry to what users are actually experiencing, offering clarity on what's broken, why it matters, and how to fix it. From web performance regressions to mobile crashes affecting high-value users, Embrace helps prioritize the issues that impact people and revenue.
"Our customers wanted to see our product approach applied to the web, where we record individual end-user play-by-plays and use those to detect the types of regressions and issues that impact user engagement," said Andrew Tunall, President and Chief Product Officer at Embrace. "With the addition of Web RUM to our premier mobile product, we're empowering teams to understand reliability and performance exactly as their users experience it, on any device."
Embrace's platform brings performance details, user context, and business-critical insight to the surface so frontend engineers and reliability teams can prioritize their work rather than wade through technical noise.
With Web RUM by Embrace, teams get:
- Full session timelines for deep insights into the user experience
- Core Web Vitals connected to the full technical details in each session
- Exceptions and error reporting with advanced troubleshooting tools
- Custom metrics and alerting around key flows and events
- OpenTelemetry-native ecosystem with semantic conventions for cross-system analysis and data portability
Now, engineers can improve the reliability of user experiences by connecting mobile, web, and backend systems with shared context, standards for instrumentation and conventions, and powerful cross-team workflows.
The Latest
As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...
For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...
I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...
Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...
80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...
40% of organizations deploying AI will implement dedicated AI observability tools by 2028 to monitor model performance, bias and outputs, according to Gartner ...
Until AI-powered engineering tools have live visibility of how code behaves at runtime, they cannot be trusted to autonomously ensure reliable systems, according to the State of AI-Powered Engineering Report 2026 report from Lightrun. The report reveals that a major volume of manual work is required when AI-generated code is deployed: 43% of AI-generated code requires manual debugging in production, even after passing QA or staging tests. Furthermore, an average of three manual redeploy cycles are required to verify a single AI-suggested code fix in production ...
Many organizations describe AI as strategic, but they do not manage it strategically. When AI plans are disconnected from strategy, detached from organizational learning, and protected from serious assumptions testing, the problem is no longer technical immaturity; it is a failure of management discipline ... Executives too often tell organizations to "use AI" before they define what AI is supposed to change. The problem deepens in organizations where strategy isn't well articulated in the first place ...
Across the enterprise technology landscape, a quiet crisis is playing out. Organizations have run hundreds, sometimes thousands, of generative AI pilots. Leadership has celebrated the proof of concept (POCs) ... Industry experience points to a sobering reality: only 5-10% of AI POCs that progress to the pilot stage successfully reach scaled production. The remaining 90% fail because the enterprise environment around them was never ready to absorb them, not the AI models ...
Today's modern systems are not what they once were. Organizations now rely on distributed systems, event-driven workflows, hybrid and multi-cloud environments and continuous delivery pipelines. While each adds flexibility, it also introduces new, often invisible failures. Development speed is no longer the primary bottleneck of innovation. Reliability is ...