1 / 39

Apache License as a Business Model: Challenges and Opportunities

Apache License as a Business Model: Challenges and Opportunities. Paul Fremantle, CTO, WSO2 pzf@apache.org (with a LOT of help from Sanjiva Weerawarana, CEO, WSO2). Why am I talking to you about this?. Apache Member Been contributing to Apache since 2000 VP, Apache Synapse

carson
Télécharger la présentation

Apache License as a Business Model: Challenges and Opportunities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Apache License as a Business Model:Challenges and Opportunities Paul Fremantle, CTO, WSO2 pzf@apache.org (with a LOT of help from Sanjiva Weerawarana, CEO, WSO2)

  2. Why am I talking to you about this? Apache Member Been contributing to Apache since 2000 VP, Apache Synapse Incubator, HTTPComponents, WebServices, QPid, etc Co-Founder of a company based around the Apache License WSO2 Founded in 2005 Selling software licensed under ASL2.0

  3. Business Model How do you get people to pay you money when all your software is available under the Apache license? Consistently A good chunk of people who use my stuff pay me Frequently Hopefully every year and not just once Scalably The more you use my stuff or the more of my stuff you use, the more you pay me

  4. Apache and Apache License

  5. Two options Company X Building software that has no relationship to Apache Other than the License Company Y Building software AROUND Apache Projects and code Also under ASL2.0

  6. Of course there are other options!

  7. Bait and Switch

  8. How to bait and switch Release some software under ASL But keep the good bits back: Clustering Management Performance Put some code under GPL And offer a commercial EULA license for that

  9. Opportunities

  10. Challenges

  11. Apache License – challenges Challenges Getting Started Persuading investors Establishment Brand management Converting free to pay Ongoing Protecting against leeches

  12. Investor concerns Who has “made it” with an Apache License? What assets and IP do you own? If you are based on Apache projects how do you associate yourself with Apache?

  13. Who has made it? No-one (YET!) Gluecode was not a real business when it sold Covalent goes both ways Every major IPO or sell has used GPL/LGPL JBoss, MySQL, Redhat

  14. Libraries vs Servers vs User apps

  15. How do you respond? Mission Critical apps need real support Offer more value than just code Support, consultancy, expertise Brand Leadership, Expertise, Successful projects Technology Partner

  16. Assets If the code is available under the ASL where is the IP? People – committers Brand Customers

  17. Presence You can’t abuse Apache Or the Apache Ninja’s will get you Techniques Certified distributions E.g. FuseSource Value-added products (still ASL) E.g. WSO2 Marketing E.g. A booth at ApacheCon

  18. Brand Management You still can’t abuse Apache Apache owns the Apache brands Contribute a lot But you still need to leave enough room for a community

  19. Create another brand

  20. Getting users to pay

  21. If you want that use the GPL!

  22. Volume Game Be the first OSS provider in a given space Huge numbers of downloads Get a small proportion of users to pay MySQL, JBoss, Redhat

  23. Those days are over

  24. FOSS 1.0 is over Every technical area has multiple OSS projects Just look at Apache projects 0.1% conversion rates are no longer going to win Proprietary vendors often have “bait and switch” style OSS offerings

  25. FOSS 2.0 Show real business value to customers

  26. Showing value Go beyond low-end support End-to-end relationship Training, Consultancy, Full Enterprise Support Become a mentor not just an implementor

  27. One further value Very few open source projects offer backports of fixes Trunk and latest build or nothing Even fewer (if any) offer patches In proprietary software customers pay to upgrade In OSS, customers pay not to upgrade

  28. Leeches Companies offer to support “any” project No committers No involvement in the project No contribution

  29. Leeches are bad for Open Source Open Source businesses need to make enough money to improve the projects Per incident support and leeching are harmful to the projects Particularly harmful in Public Sector Many customers MUST take the lowest bid

  30. What about the opportunities?!

  31. Benefits of Apache License Business Friendly There are companies that will not touch other licenses Great for OEMs No nasty tricks No timebombs

  32. The problem with Bait and Switch Customer installs OSS to try it out Builds their application or proof-of-concept Now you want them to pay AND re-install! Maybe even re-code for the enterprise version

  33. Summary Contrary to the beliefs on Sand Hill Road, you can build a business on ASL Need careful brand management Customers might even pay you!

  34. Questions?

More Related