Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The new model is better for you if you want the company to make enough money to be able to support the product and put out new releases to fix bugs and vulnerabilities.


Why did the old model suddenly become unprofitable? If it's team bloat I'm not really sympathetic.


> "Today, over 95% of our revenues are coming from subscribers"

https://blog.agilebits.com/2017/07/13/why-we-love-1password-...


That doesn't explain why the old model became or didn't become unprofitable...


The parent comment was a loaded question that there was some sudden change. If the old model did good / better, they wouldn't have switched to a more profitable model. I believe it's well established in our industry that SaaS models are more profitable than one-time software sales. The analogy is equivalent to why Adobe switched Photoshop to a SaaS model and why Microsoft did the same for Office. Recurring revenue is king in the long run.


Maybe, then they should say so, indirectly better for me.

But bugs and vulnerabilities? On a years old, widely tested and used "static" (or almost "static" ) product?

How many possible ones they are introducing by completely changing the tool to be on the "cloud"?


1Password had vulnerabilities disclosed by Tavis Ormandy within the last year regarding the communication between the application and the browser extension. Those vulnerabilities were part of the so-called "static" product, and were not related to the new cloud functionality.

[0] https://bugs.chromium.org/p/project-zero/issues/detail?id=88...


Yes, I wasn't saying that the one had not bugs, all software may have some of them, I was only saying that the risks of introducing more, new ones when changing completely a software (or rewriting it) are bigger.


It's not a static product even if the feature set is relatively static. Take a look at their Mac app changelog for instance.

https://app-updates.agilebits.com/product_history/OPM4




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: