[bberenberg]

I think this is a great idea with the wrong pricing model. Look at all the one off payment products that involve code, they're all dead. Just charge a lower but recurring price so I can be sure that you make enough money that you keep working on it. $20/month flat price to keep the license working and source available if you shut down. If people like it and want the barebones Sentry then charge them $40 a month to provide code and host it. Wishing you the best of luck.

[kyrylo]

> Look at all the one off payment products that involve code, they're all dead.

Could you share some examples? I can’t think of any off the top of my head.

--

I really went all-in with the ONCE philosophy because it resonated with me deeply. It felt more like a passion project than cold business strategy.

[bberenberg]

I think all of the boilerplate projects you can find.

Are ONCE projects getting updates? We will find a year or two?

Your model is a subscription, we just don’t get to know when you decide to have a new major version and plan pricing / spend as a result.

[nik736]

The problem with ONCE is that software is never finished. This is why most ONCE software that is still available today is charging a one off licensing fee + update fee (e.g. charge yearly for major updates or 10% of the one off fee per year). This is sustainable, but your model isn't. You will notice down the road in 2-4 years that it's no fun to work for free for users that expect an update because it requires patching or there are breaking changes.

[csomar]

He is selling updates. You pay once for 1.x. That's a fine and okay business model that has been functioning for very long.

[viraptor]

https://www.reaper.fm/ uses that pricing and has... let's say fanatical following. You pay once for version X and X+1 just in case you miss out on an update coming in a month. Then you pay again for a big upgrade.