Launch HN: Massdriver (YC W22) – Self-serve cloud infra without the red tape

* You want to simplify infrastructure, but there's a new learning curve here. Why did you decide to go with diagramming as a solution? What other methods did you evaluate and discard?

* How does an organization with existing infrastructure implement Massdriver?

* How do you handle edge cases, custom configurations, complex logic, etc.? For example, workflows that use custom scripts or some other form of band-aid.

* The visual approach could make it too easy to piece together infrastructure without understanding the implications. How do you prevent developers from creating poorly architected systems just because you make it simple to connect components?

* When things go wrong, how do developers debug issues at the infrastructure level? Do they reach out to ops?

What does a seat entail? You talk about self serve (I love it!), but would the users that self-serve take up a seat? Or are seats just for the folks creating the modules?

For larger teams we do buckets of seats with price reductions per-seat as the team size goes up.

We don't rate limit deploys - as that would make you less agile, we don't charge based on resources because that penalizes teams with stable infrastructure.

We know ops budgets can be tight, we're ops engineers, so we try our best to make the pricing work well for those budgets.