Since I haven't shared much about Nimbus lately, I wanted to give an update. But for some context: before starting Nimbus, I was a staff engineer focused on core marketplace systems for a metals marketplace, with previous experience working at startups on things like SOAR, legaltech, etc.
I started Nimbus in late 2023, when the AI landscape was still extremely frothy (still is, I suppose). Product engineers were working on things usually reserverd for ML/AI roles, and we initially thought they'd need better tools to bridge that gap. But as we spoke with more teams, we uncovered a different challenge: engineers were struggling to understand their existing systems and make changes confidently.
We started by focusing on auto-updating technical documentation, thinking we could solve the eternal problem of stale docs. But we learned something important – even perfect documentation isn't enough. Engineers need different types of information at different times, whether they're designing new features or trying to understand system implications.
That insight shifted our focus to RFC and technical design workflows, where we saw an opportunity to help teams better understand their systems. We've built tools to help visualize system architecture, integrate with existing tools like Figma and Miro, and manage the feedback process. Our goal is to help teams see the potential impacts of their changes and find relevant information without constant context switching - essentially making system understanding more accessible, even when you're not working with all components daily.
Our first case study with a Series B startup has shown promising results. They're using a modern stack (Serverless Framework, AWS Lambda, TypeScript, Postgres+Prisma) in a microservices architecture, and have seen improvements in productivity and reliability, with fewer bugs making it to production. (Expecting to publish that in the next week!)
We're now expanding our platform capabilities and looking at Kubernetes integration for our next phase, along with some AI-powered features to help teams anticipate downstream impacts of changes, get recommendations about what might be important to review, and more easily connect technical decisions to business data - all while keeping context-switching to a minimum. I suppose we should also update our website to reflect this new focus, as well!
If you're interested in seeing a demo, joining our mailing list, or participating in our beta program, reach out to me at matt.kindy@nimbusai.dev. And you can follow us here on LinkedIn at https://lnkd.in/geFmB893
