3 ms·
We use a subscription model at Fogbeam, but here's the twist: all our software is open source, and you're free to use it as you like, with or without a subscrip
by mindcrime 11y ago
We use a subscription model at Fogbeam, but here's the twist: all our software is open source, and you're free to use it as you like, with or without a subscription.
So why buy a subscription at all?
Because you get the kinds of things big companies care about: certification, maintenance, support, indemnification, somebody to sue if things don't work, a vendor to shift blame onto if the shit hits the fan, a discount on professional services work, perpetual upgrades, priority access to influence the roadmap and direction of the product, etc. Subscriptions are also a win for customers in that (depending on the details) they may be able to pay for a subscription out of an operational budget, rather than needing to go to some committee and get approval for a large one-time capital expenditure. And with subscriptions you are paying a portion of the cost in future, inflated, dollars instead of today's dollars.
Of course, like any vendor who does OSS, we run the risk of having a lot of people using our software and never paying, but that's just something we accept.
But here's the thing... we don't sell development tools - IDEs and the like. Our stuff is backend/middle-ware that costs in the tens of thousands of dollars and up (for companies with thousands of employees, anyway), which makes things like worrying about capital expenditures more of an issue. At the kind of price-points you are talking about for IDEs and what-not, I'm not sure the advantages of a subscription (from the customer POV) really carry much weight.
- mreiland 11y agoI would like to see the software contract that includes indemnification for the software.
- mindcrime 11y agoWe don't have the final wording all worked out for all of that stuff. We've been pretty focused on product stuff for the past while, and only recently got to a point where we have a product actually available for sell, and we're still working on contracts / licenses and all that. But what I can tell you is that our approach will probably look a lot like what Red Hat does[1]. Basically, it's a guarantee that if you get sued for using our software (patent infringement, whatever) then we protect you from any fallout from that. [1]: http://www.redhat.com/en/about/open-source-assurance http://www.redhat.com/en/about/open-source-assurance
- mreiland 11y agoSo you're not really indemnifying the software use itself, that's where the confusion came from.
- mindcrime 11y agoI'm not sure I understand the distinction you're making there. We defend the company from issues using our software, arising from a 3rd party's IP claims. We wouldn't defend them if they used our software as part of an effort to hack into the Facebook's user database and stage a massive identity theft scheme.
- mreiland 11y agosoftware use as in, problems that occur from actually using the software. As opposed to IP claims which is typically over the source code, not the software itself. For example, if you write a realtime scheduling component that Toyota ends up using in their vehicle software, and someone dies due to a problem with the realtime scheduling, you do not protect Toyota from the resulting lawsuit.