3 ms·

Hey, I just wanted to say that I checked out your company, and I think you have a very compelling product. Unfortunately, I'm not in a position to buy it (junio

by bglazer 11y ago

Hey, I just wanted to say that I checked out your company, and I think you have a very compelling product. Unfortunately, I'm not in a position to buy it (junior engineer at a massive corp). Instead I just wanted to wish you luck!

beat 11y ago
I have a very compelling idea, and a very compelling problem. And a product that is not yet sales-ready yet. But we're getting there. It's been in a fundamental rewrite mode since August (what I thought was the beta was actually the alpha), and I've since added two co-founders so I'm not doing it alone anymore - deeply experienced enterprise engineers like me who have felt the pain that we're trying to solve viscerally. But yes, thanks for the confidence! :) The best part of it is when I talk to the target users about it and their eyes light up and they get so excited. The problem is huge, and the current solutions are terrible. If we can't make money at this, it's an execution problem, not a market problem.
- pm 11y ago
  Had a look, and yes, that's not an easy problem to solve. Good luck with it.
- paulmd 11y ago
  How is your product different from etckeeper + flyway + source control?
  - beat 11y ago
    First and foremost, it monitors the real world, not the version control system. It sees things as they are, not as they're supposed to be. It detects manual, unversioned changes. It detects changes from automation, or from intrusion. It detects things that can't be versioned, like reboots or cert expirations. Second, it is minimally invasive. You don't have to change your process in order to use it. Third, it shows relationships between systems. An application isn't just source code. It's compiled binaries, OS patches, user security, databases, firewalls, message queues, apis, and more. Here's a common failure pattern - System A changes, System B breaks. System A might actually be perfectly fine and correct, and B as well, but the relationship between A and B is broken. Change the database schema, and the app can no longer read it. Change the dns, and the UI can no longer find the API. For any decently complex application, the potential sources of failure are in the thousands, and potential interactions effectively infinite. Now scale this up to the enterprise, to organizations so large that your app can be broken by departments you didn't know existed...
    - subway 11y ago
      Does it detect when you have a busted marketing site? https://congruence.io https://congruence.io
      - beat 11y ago
        Thanks. It's a known problem... we're currently in product work and haven't been dealing with marketing at all. It's just a cert problem - http://congruence.io http://congruence.io still works. And yes, once it's working, it will be able to detect such issues.
      - beat 11y ago
        And the certificate is now fixed. Try it, https://congruence.io https://congruence.io is working again!

by bglazer 11y ago

beat 11y ago

I have a very compelling idea, and a very compelling problem. And a product that is not yet sales-ready yet. But we're getting there. It's been in a fundamental rewrite mode since August (what I thought was the beta was actually the alpha), and I've since added two co-founders so I'm not doing it alone anymore - deeply experienced enterprise engineers like me who have felt the pain that we're trying to solve viscerally. But yes, thanks for the confidence! :) The best part of it is when I talk to the target users about it and their eyes light up and they get so excited. The problem is huge, and the current solutions are terrible. If we can't make money at this, it's an execution problem, not a market problem.

pm 11y ago
Had a look, and yes, that's not an easy problem to solve. Good luck with it.
paulmd 11y ago
How is your product different from etckeeper + flyway + source control?
- beat 11y ago
  First and foremost, it monitors the real world, not the version control system. It sees things as they are, not as they're supposed to be. It detects manual, unversioned changes. It detects changes from automation, or from intrusion. It detects things that can't be versioned, like reboots or cert expirations. Second, it is minimally invasive. You don't have to change your process in order to use it. Third, it shows relationships between systems. An application isn't just source code. It's compiled binaries, OS patches, user security, databases, firewalls, message queues, apis, and more. Here's a common failure pattern - System A changes, System B breaks. System A might actually be perfectly fine and correct, and B as well, but the relationship between A and B is broken. Change the database schema, and the app can no longer read it. Change the dns, and the UI can no longer find the API. For any decently complex application, the potential sources of failure are in the thousands, and potential interactions effectively infinite. Now scale this up to the enterprise, to organizations so large that your app can be broken by departments you didn't know existed...
  - subway 11y ago
    Does it detect when you have a busted marketing site? https://congruence.io https://congruence.io
    - beat 11y ago
      Thanks. It's a known problem... we're currently in product work and haven't been dealing with marketing at all. It's just a cert problem - http://congruence.io http://congruence.io still works. And yes, once it's working, it will be able to detect such issues.
    - beat 11y ago
      And the certificate is now fixed. Try it, https://congruence.io https://congruence.io is working again!