We've spent the last 6 months pointing an agent at real production errors. Going in, we were sure the hard problem was "can an AI write the fix." Almost everything that mattered turned out to be somewhere else. Three surprising things we learned:
1. Most errors were never worth a page
Across real traffic, ~70% of errors triage out as noise. Which means they are not actionable and no human is needed. This rate holds surprisingly consistently across tenants and services. I still remember integrating with our first design partner. First Slack notification comes in, the team is high-fiving, pure excitement. This thing actually works! Next thing we know our Slack inbox blows up and a burst of 12 notifications arrive. So we built a relevance gate to make sure notifications only happen if something truly breaks. We set out to fix bugs and discovered the bigger win was the 70% of times we give time back.
There's a lot of AI out there right now that wants to act on your behalf. Agentic solutions, that claim to automagically merge PRs and deploy the fix with little or no human needed.
We look at things differently. We take a realistic stance on the usage of AI. Recent advances in natural language processing have unlocked possibilities that once seemed out of reach, yet we recognize AI as a powerful enabler within our technology stack, not a universal solution or substitute. Here's what Bohun does when an alert fires:
-Reads the stacktrace
-Pulls the relevant source files from your GitHub/GitLab repo
-Classifies severity (critical / high / medium / low / noise)
-Correlates errors across services using trace IDs
-If required, opens a PR with a proposed fix + full context
-Pings your Slack with the incident summary and PR link It hands you all the context.
You review and decide what ships. Bohun never merges without you. When building this solution, we wanted to make sure the integration was stupidly simple and that it did not disrupt existing workflows.
We have bootstrapped OurBase with the conviction of using AI to make us breathe easier at work and to level the playing field and make agentic solutions accessible to all.
@yumi_joh Looks very interesting! I'll be putting you in touch with another friend who may need something like this.
I have a question though -- does this only need to be used by large engineering teams?
@yumi_joh @sharan_grandigae Thanks Sharan! Not at all, it's built to support engineering orgs of all sizes. We're using it ourselves and I'd consider us a rather lean engineering and product team.
I think several of my customers could use this.
Can I put them in contact with you?
Many Thanks
@gemma_diaz_arenas Music to our ears. Please have them reach out to: yumi@ourbase.ai
Congrats on the launch!
Keeping the final call with the engineer instead of auto-merging feels like the right move. And a Slack ping with the incident summary and PR link... pure gold at 3am!
@marc_sg Thanks for the kind words Marc! Keeping engineers in the loop has been a guiding principle in our core design. We've seen the most success helping eng orgs go deeper, not just faster. One way that's improved their workflow drastically is noise reduction. We're cutting pings by ~70%, so what triggers is actually worth investigating.
StackOverflowgeddon Survival Kit
That's a super cool idea with many applications for my projects. I will be a user for sure!
@cousy14 Fabulous! Sign up and activate your free trial: https://app.ourbase.ai/signup