The product is a way to answer the simple yet awful question, "What changed?" Configuration change is the primary cause of failure in complex software systems. But the part that breaks isn't necessarily the part that changes. For example, a database schema change can break apps that rely on the database. But in large organizations, where the database is administrated by an entirely different team from app development and developers may not even be allowed to look at the production environment, it's a huge pain point.
Detecting configuration change and finding the relationships and impact is a really difficult and challenging problem. The biggest takeaway from the alpha for me was that "noise shaping" is a hard problem. For example, Wordpress alters the schema of its MySQL database several times a day. It's a tiny thing (an autoincrement value on a single column), but it makes sorting important changes like upgrades that only happen weekly or monthly or yearly from unimportant changes that happen daily.
The trick now is to get a product out of it good enough to make money, so I can afford to quit dayjobbing and live off my own creation, rather than sitting at someone else's desk and counting the number of times a day I wish I had my own product here to help solve the problems I deal with over and over, every damned day.
It would do in software what a really good reliability engineer with years of knowledge can do "Foo has broken" "Nah foo is fine, someone changed Bar again without reading the wiki" stuff.
But this is a HARD problem. Man, abstracting change in an actionable, readable, efficient way has been difficult. Not to mention the security issues and other headaches.
I spent 20 years building a successful career as an enterprise software engineer, bouncing around between configuration management, development, and ops. It's a secure, good paying, stable career. And I grew to resent and sometimes hate it.
Then I started building something for myself, discovered the idea of creating my own startup to solve problems I experienced doing enterprise software projects in a general way, and I love that. It makes me feel like I'm doing something that actually matters.
Right now, I'm back in the enterprise to make ends meet and building on the side, which sucks and drives me crazy - but at least I see the exit and can keep moving toward it. And I figure I can get five or ten years out of building a company before I'm done with that as well.
Once you hit a certain age and a certain level of success, the things you realize you'll never do weigh on you more than the things you haven't done yet. And the things you do look more like impediments than accomplishments. That's when you need to change.