[abarrettwilsdon]

I like the idea but 20% of cloud spend in perpetuity is completely ridiculous and rules out anything above personal toy projects

Even if someone did sign up for the paid tier, they are strongly incentivized to cancel and keep to code

[hn_throwaway_99]

I think the idea is very cool, but similar to the parent comment I have a lot of reservations about how the economics of this work:

1. I get that it seems like pretty much any software business isn't feasible if it doesn't involve a subscription model, but this seems like the last thing I'd be willing to pay a subscription for. I'd pay for what is essentially a good template, but after that, I'd want to own it.

2. In one of the Medium posts the author posted he mentioned that architectures can be 'ejected'. How does that work with your pricing model?

I guess a pricing model where you paid a subscription fee for additional services (some sort of monitoring, automatic upgrades, etc.), but with the option to pay a flat fee at any time to 'eject', is something I'd consider.

But yeah, 20% of cloud spend in perpetuity is steep. More importantly, I put anything that is a perpetual spend under an extremely critical lens, especially something expected to grow linearly with revenue.

[jeremylevy]

Thanks!

Pricing is something that we've thinking about for a while.

What's your opinion? How much are you willing to pay?

[jeremylevy]

It's a first alpha release. We're listening to feedback. Billing is not implemented yet.

Pricing is something that we've thinking about for a while.

What's your opinion? How much are you willing to pay?