Notion-style editing meets infra-debugging tools
Hi HN, TL;DR: Collaborative notebooks for debugging your infrastructure I’m mies, founder, and CEO of Fiberplane, and I’m excited to show you what we’ve built; a real-time collaboration tool for SRE and DevOps engineers. As of today, Fiberplane is in public beta. Before Fiberplane, you’d need to cobble together information from teammates and alert tools like PagerDuty in Slack, switch to dashboard Nr. X to look at the data, screenshot it, switch back to Slack, paste, and then rinse and repeat, all while critical services were down. Then you’d do this dance all over again but now pasting…
In plain words
Fiberplane is a collaborative notebook tool designed for SRE and DevOps engineers to debug infrastructure incidents in real time. It consolidates information from multiple sources and alert tools into a single workspace where teams can query data, communicate, assign tasks, and document investigations simultaneously. Rather than switching between dashboards, Slack, and documents during outages, engineers use Fiberplane to streamline incident response and post-mortem documentation in one place.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Hi HN, TL;DR: Collaborative notebooks for debugging your infrastructure I’m mies, founder, and CEO of Fiberplane, and I’m excited to show you what we’ve built; a real-time collaboration tool for SRE and DevOps engineers. As of today, Fiberplane is in public beta. Before Fiberplane, you’d need to cobble together information from teammates and alert tools like PagerDuty in Slack, switch to dashboard Nr. X to look at the data, screenshot it, switch back to Slack, paste, and then rinse and repeat, all while critical services were down. Then you’d do this dance all over again but now pasting screenshots into a Google Doc. With Fiberplane, when you have an incident, the team can all get together in one Notebook, query and show data, tag teammates and assign actions, resolve it, and then write a post-mortem directly from the investigation Notebook. We’ve used Fiberplane internally ourselves a few times already to debug some failed data migrations. Once the issue was detected, we’d create a Notebook, share logs from our api and use it as a live document while we were debugging the issue. When we’ve resolved the issue - the post-mortem was already there. We just had to edit it, make it actionable, so that when we reran the migration later – we had internalized all the lessons from the first run. Here’s what we’ve built: 1. Integrations with some of the most popular open-source observability tools: Prometheus, Elasticsearch, Loki, and more integrations with other tools are on the way. 2. A WASM-based plugin system for integrations (which, in the future, will allow for 3rd-party integrations to be built and run securely) along with an open-source bindings generation framework https://github.com/fiberplane/fp-bindgen 3. An advanced block-based editor: You can run PromQL, LogQL, and Lucene queries, and display Prometheus charts and Elasticsearch or Loki log tables alongside the rest of your content. Filter your metrics, and logs, highlight important records, and collaborate on your infrastructure data. 4. Templates are written in Jsonnet language and allow you to programmatically create notebooks and automate your Fiberplane workflows. They can have Webhook URLs attached to them allowing you to connect Fiberplane with your alert tools (or really anything that can send a Webhook request) making them a powerful tool for incident runbooks and post-mortems. 5. A CLI that allows you to share your terminal debugging output with your team with a simple command. 6. Our backend is all in Rust, using the Axum web framework. It also includes some fun parts like a custom Operation Transformation library that’s used directly from the backend and compiled to WASM for the frontend. Fiberplane was created out of our own experience of running large distributed systems. There was too much context switching when working with monitoring and observability tools. Over the past two years, we’ve been working hard on the first real-time collaboration notebook for the observability space to make infrastructure debugging faster and easier. We’re launching into public availability and looking to create the best debugging and incident resolution workflow tool for developers, Site Reliability, and DevOps engineers. We would love your feedback.
More work this month
the category →
The app store for voice native apps that lives in your notch
Work · 28d ago · voiceos.com
The New Calendly▲211Handle all of the work before, during, and after meetings
Work · 17d ago · calendly.com
Launched alongside, November 2022
the whole month →
- TC
I made a thing! In 2014, I was holding a stack of iPhones and thought to myself: "Hey, if I had each phone display a playing card, I could click a button and they'd shuffle themselves" I pared that idea all the way down to this: trading cards made of e-ink displays. Right now, each card costs me about $20 each, but with only a bit more scale, I think I can get that down to $10. In doing this project, I learned how to design electronics and circuit boards. I learned Rust and wrote my first driver, I upped my CAD skills, 3D printed, and did my first resin casting. I generated the images on the…
Dev tools · 2022 · wyldcard.io
