Fiberplane, a real-time collaboration notebook specifically designed for developers and DevOps teams to debug their infrastructure, announced the public beta of their real-time collaboration tool for site reliability engineers.
Fiberplane allows users to integrate data sources from their observability stack to get to the heart of problems quickly and collaboratively.
Enterprise infrastructure over the last decade has become incredibly complex to manage, leaving developers and DevOps teams to mitigate bugs with tools that were slapped together or designed for a different time. Until now, developers have been getting by with dashboards that they set up in advance and require that they know what they're looking for. But as unknown unknowns rise, this approach no longer works. Furthermore, the rise of distributed and remote teams, which has grown substantially due to the pandemic, more aggressive recruitment and retention strategies and the distributed nature of computing, requires collaboration-first tools, which we haven't traditionally seen in the SRE/DevOps space. Modern CI/CD workflow, microservices and distributed teams and systems all require a new explorative form factor for infrastructure debugging, one that works real-time and takes into account the changing nature of teams.
Fiberplane's technology is built in Rust and WebAssembly (Wasm). To resolve conflicts when multiple people are typing at the same time in a Fiberplane notebook and adding data including graphs or tables, it uses Operational Transformation, the same algorithm used by Google Docs.
Because Fiberplane is vendor agnostic, through its WASM-based plugin system, enterprises can integrate Fiberplane with their stack and query, visualize and explore their stack with real data (using logs, metrics and traces) with ease.
Fiberplane gives users the freedom to query, visualize and control any system in their infrastructure. It allows companies to coordinate their distributed teams by sharing information on its collaborative, multi-user tool. Users can leverage Fiberplane's powerful API and CLI to automate notebook creation based on specific external events, such as monitoring alerts. Instead of individuals working with distributed information, Fiberplane enables organizations to capture best practices, create a system of record, and build actionable documentation as a team.
"Developers can finally easily collaborate with others in real-time and with full visibility of their data," said Micha Hernandez van Leuffen, founder and CEO at Fiberplane. "Whether it's editing a sophisticated notebook simultaneously, tagging others or sharing documentation with other functions, Fiberplane has the 'look and feel of a notebook' that engineers feel comfortable using."
The Latest
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...
When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...
Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...
Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...
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 ...