Scrubbe

Engineering organizations have become incredibly good at collecting operational data. The next challenge isn’t collecting more information—it’s making better operational decisions from it. This post explores why the concept of an Intelligent Control Plane is becoming increasingly important as systems grow in complexity, and why coordination, governance, and operational context may become just as critical as observability itself. I’d be interested to hear how others see this evolving. Please read below; linkedin.com/pulse/why-engi… #IncidentManagement #PlatformEngineering #SRE #DevOps #EngineeringLeadership #OperationalExcellence

@garrytan @ycombinator Median is never good enough.

Don’t be a mid startup It’s true

Our founder Paschal Ifediora at @CockroachDB conference meeting with industry leaders, innovators and engineers spanning from @IBM , takara.ai, @DeutscheBank and @IspirerSystems. Great scenes to behold. #scrubbe #aiincident #cloud #devops

Over the last few weeks chinka uchenna, who’s a senior software engineer at scrubbe have figured out how to make our system a better governed autonomous incident response platform. He built operational rules into scrubbe; Scrubbe operational rules provide the mechanism for organizations to encode their operating model, risk appetite, compliance requirements, and incident governance directly into the platform. Operational Rules allow organizations to codify how incidents should be managed under specific conditions, from escalation paths and team assignments to war room creation, playbook execution, notifications, and governance controls. For engineering teams that require greater flexibility, Scrubbe also supports Rules-as-Code, enabling operational rules to be defined programmatically using JSON templates. This allows teams to version, review, test, and manage operational policies using the same engineering practices they apply to infrastructure and software delivery. The result is a more consistent, auditable, and scalable approach to incident management—where operational knowledge becomes operational behavior. #IncidentManagement #OperationalExcellence #PlatformEngineering #SRE #DevOps #EngineeringLeadership #CloudNative #EnterpriseTechnology #Scrubbe

@elonmusk Elon just created 4000 millionaires, this is simply humanity.

Thank you! 🚀🚀🚀

@franksdonald Mary, queen of mercy and queen of holy Saturday- pray for us. Amen 🙏🏼

@JacobJacksonVC Hi Julian, scrubbe will be happy to join the family.

Get your startup funded quickly, by getting in front of all of the best deeptech VCs in the world, at the same time. Close your round fast and get back to work. We're excited to see what your building!

A short note on something we’re working on at Scrubbe. Most conversations around Model Context Protocol (MCP) focus on giving AI systems access to tools. We think the bigger opportunity is giving them access to operational memory. Consider a simple question: “We’re planning a database migration next quarter. What operational risks should we expect?” Today, answering that often requires searching through years of incidents, postmortems, handovers, runbooks, deployment records, lessons learned, chat threads, and institutional knowledge scattered across multiple systems. The answer usually exists somewhere. The challenge is finding it before the migration begins. We’re exploring a different approach. What if an engineer, architect, or AI assistant could ask Scrubbe a question like: “Have we performed a migration like this before?” or “What incidents were caused by previous Kubernetes upgrades?” or “Which remediation plans proved most effective during our last on-premise to cloud migration?” And instead of returning documents, Scrubbe could reconstruct an answer from the organization’s operational corpus: • Similar incidents and their outcomes • Previous remediation actions • Relevant playbooks and workbenches • Postmortem findings and lessons learned • Handover risks identified by previous teams • Dependency and service impact patterns • Historical approval and execution decisions The same idea applies to major upgrades, cloud migrations, platform modernisation programmes, architecture changes, disaster recovery exercises, and large-scale operational transformations. The goal is not another chatbot. The goal is operational intelligence. An engineer should be able to ask: “Have we seen this before?” A platform team should be able to ask: “What is most likely to break during this migration?” A CTO should be able to ask: “What patterns exist across every P0 incident related to infrastructure changes?” And receive answers grounded in operational evidence rather than isolated documents. We believe the next generation of reliability systems will not be defined by how much telemetry they collect. They will be defined by how effectively they transform years of operational history into actionable intelligence. That’s one of the areas we’re thinking deeply about as we continue building Scrubbe. #scrubbe #incidentmanagement #aiops

I’ve come to realize that Scrubbe is more than a company to me. It’s a fellowship. A fellowship of engineers, operators, builders, thinkers, and believers who share a conviction that incident management can be fundamentally better than it is today. Every major incident exposes the same challenges: fragmented knowledge, disconnected tools, delayed decisions, and immense pressure on the people responsible for restoring service. For decades, we’ve accepted many of these challenges as inevitable. We’re building because we don’t think they are. The journey of building Scrubbe has connected me with incredible people who care deeply about reliability, resilience, operational excellence, and the future of engineering operations. Building a company is difficult. Building a new category is even harder. Neither is possible alone. I’m grateful to everyone who has contributed ideas, challenged assumptions, shared feedback, and joined us on this mission. The road ahead is long, but that’s what fellowships are for. #Scrubbe #StartupJourney #EngineeringLeadership #IncidentManagement #SRE #DevOps #PlatformEngineering #OperationalExcellence

@samthekorean Hi Sam, let’s have a chat about scrubbe

starting today, i’m writing $25k–$50k checks to founders :) leave a comment on what you’re building and lets have a chat!

Most engineering organizations have spent years improving observability, yet one of the major bottlenecks during major incident remains: knowledge transfer. Read the article below 👇🏽 linkedin.com/posts/paschio_…

@garrytan I can

The best pitch test: can you tell this at a bar to a friend? Not the market size, not the TAM, not the deck. Just the story. Why you built it. What you saw that nobody else saw. What happened. If you can't tell it naturally over drinks (or it would feel weird to your friend and they would think "this isn't you"), your idea or pitch or endeavor needs to bake some more. The 9pm-at-a-bar test for your startup idea is a defining authenticity test. And without that, nobody will buy your product, let alone come work for you or invest.

How scrubbe resolves the most dangerous production incidents. Please read the article 👇🏽 linkedin.com/posts/paschio_…

Instead of helping humans manage incidents better, we are building AI agents that investigate failures across #codes, #pipelines, #infrastructure, #production #systems, determine probable #rootcause, verify the safest #remediation, and execute resolution #autonomously. #scrubbe

@RKRigney @speedrun Hi Ryan, I would be grateful if you provide me with this opportunity. Thanks

If you're interested in @speedrun and want to speak with a partner at the firm, I'm opening up my calendar tomorrow. Hit me in the replies with a blurb about what you're working on and I'll DM the calendly link to book a slot.

Most systems today stop at detection or, at best, provide dashboards and suggestions. But the real bottleneck isn’t awareness. It’s resolution. What we’re building at #Scrubbe is a shift in that direction. #SRE #Scrubbe

MTTR is one of the most misleading metrics in engineering. It measures how fast you recovered. Not: whether you understood the issue whether it will happen again whether the fix was actually safe You can have great MTTR and still be repeating the same incidents. #scrubbe