Expanding OEM opportunities
        with WSO2
Contents

• What  is the WSO2 stack?
• How have other companies OEM'ed WSO2?
• What are the benefits of WSO2 as an OEM
  partner?
• How does OEM work with Open Source?
• What are the normal commercial approaches
  that WSO2 and OEM partners take together?
About WSO2
•   Proven Technology
    • Founded in 2005 by acknowledged leaders in XML,
      web services technologies, standards and open source
    • 4th generation of products
• 130+ paying customers
• 56 new customers in 2011
• 25 new customers by end of March 2012.
• Global presence :
    • 160+ employees in USA, Europe and Sri Lanka
    • Growing set of partners
•   Active Member of OASIS, Cloud Security Alliance,
    OSGi Alliance and W3C.
150+ Active Customers
What is the WSO2 Stack?

•A   full middleware runtime:
 •   Application Server, ESB, Identity Access
     Management, Governance, Business Process,
     Gateway, Business Activity Monitoring, …
• Modular – reconfigurable and extensible
• Cloud-native
 • Deployable as a Cloud Solution/PaaS
 • Enabling for SaaS
• Open Source under the Apache License
• Supported 24x7 with aggressive SLAs
WSO2 Carbon Enterprise Middleware
Platform




                                    *
Developer Studio
Develop Once - Deploy Everywhere

  Stratos                              StratosLive
  Private                                 Public
   PaaS                                   PaaS

            Or, any combination of these.

             (Same programming model
            across all deployment choices)

                     Carbon
                    On-Premise
How do OEMs use WSO2?
•   Vertical solutions that require an SOA basis:
    •   e.g. A distributed application platform
    •   Migration from WebSphere, JBoss, etc to something more
        lean, cloud-ready and modular
•   Vertical versions of an SOA middleware:
    •   SOA middleware customized and specialized to a particular
        domain (e.g. Financial, Healthcare, Defense)
•   Co-opetition
    •   Other vendors who require a point solution as part of their
        stack
    •   e.g. Registry, Identity Management, API Management
•   SIs or ISVs looking to build SaaS apps or multi-tenant
    solutions
Understanding WSO2’s approach to
Open Source
•   All WSO2 products are available under the Apache License (or
    Apache-compatible licenses for third-party dependencies)
    •   We provide a full list of all components, their licenses and origins
•   We do not make patches or service packs available under the
    Open Source License
    •   Customers or ISVs must either license those or wait until the next
        release comes out and upgrade
•   We provide 24x7 support with SLAs, patches, and Service
    Packs to our supported customers and to OEM partners
Why work with WSO2 if its Open Source?

•   Can you just use our software without involving WSO2?
    •   Yes
•   So why should I involve WSO2?
    •   We support you so you be productive and support your customers
        effectively
    •   Confidential relationship under NDA
    •   Middleware is complex - this is our business and our expertise: we
        solve problems faster, advise on design, and help ensure that your
        customers get a fully supported system
    •   It leaves you free to focus on your business
    •   You get the benefit of patches and service packs to ensure problems
        are solved before your customers find them
Why do OEMs use WSO2?
•   Excellent technology
    •   Many of our existing OEMs have done very detailed multi-vendor
        evaluations and found us to be the best
•   Modularity
    • Allows you to remove or add components to get “just the right
      runtime”
    • Allows extensions to be treated as first class

•   Cloud-native
    •   The same apps can be run on-premise, in public cloud or in private
        PaaS
•   Open Source
    • Guarantees an open ecosystem
    • Makes your developers more effective
WSO2 Engagement Model
QuickStart
•   Objective: From zero to working proof of concept or
    thin slice in one or two weeks
•   Training
    •   On-site training on any combination of WSO2 products
•   Consulting
    •   Help with designing customer's SOA solutions
    •   Help with designing deployment architecture
    •   Develop prototype code for customer scenarios
    •   Assess and prepare project for production deployment
•   Follow up with 1 month Development Support
Development Support
•   Access to on-line support system for:
    •   Assisting customers with answering questions on any
        WSO2 product or technology:
        -   Confidential forum
        -   Guaranteed responses, 24-hour max SLA
    • Assistance with product tuning for performance, security
      and other needs
    • Developing samples or proof-of-concept implementations
    • Access to selected pre-production patches


•   3/6/12 month packages with maximum hourly caps
Consulting/Development Services
•   Consulting
    •   Achieve a pre-defined objective: architectural design
        and advice, training, development assistance, custom
        development, deployment advice and assistance, etc.
    •   On-site/off-site
    •   Executive/Architect/Senior Engineer/Engineer
    •   Daily/weekly rates

•   Development Services
    •   Augment customer team for critical parts of a project
    •   On-site/off-site
    •   Monthly rates
Production Support
•   Issue resolution on production systems
    •   24 x 7 x 365 support
    •   Unlimited
    •   Aggressive response/resolution times based on severity

•   Creation & delivery of patches against production version
•   Service packs applicable to the production version
•   Per runtime pricing
    •   Warm instances, test instances, etc. all no charge
Business Models

• For   low volume or initial engagements
 •   You can simply resell our support to your
     customers
• Many OEMs prefer to negotiate a more
 integrated deal
 • In this model we typically agree a “value” of the
   WSO2 contribution to the OEMs product
 • Use this as a starting point to agree a %age of
   revenue
Technical Summary

• Component-based modular approach
• Complete end-to-end platform
• Cloud Native:
    •   multi-tenant, elastic, metered, billed, self-service
• Interoperable: SOAP, REST, AMQP, XML, JSON
• Innovative: the only complete and integrated
  Platform-as-a-Service
• Available on-premise, in cloud, as-a-Service
• A single cohesive codebase
Business Summary

• An open partner
• Providing world class technology and support
• With a set of existing OEMs in multiple
  business areas
Contact us:                Follow us:
http://wso2.com/contact/   http://twitter.com/#!/wso2
Thank you for attending!

Questions




                     Your feedback
                      is very much
                       appreciated

Expanding OEM Opportunities with WSO2

  • 1.
  • 2.
    Contents • What is the WSO2 stack? • How have other companies OEM'ed WSO2? • What are the benefits of WSO2 as an OEM partner? • How does OEM work with Open Source? • What are the normal commercial approaches that WSO2 and OEM partners take together?
  • 3.
    About WSO2 • Proven Technology • Founded in 2005 by acknowledged leaders in XML, web services technologies, standards and open source • 4th generation of products • 130+ paying customers • 56 new customers in 2011 • 25 new customers by end of March 2012. • Global presence : • 160+ employees in USA, Europe and Sri Lanka • Growing set of partners • Active Member of OASIS, Cloud Security Alliance, OSGi Alliance and W3C.
  • 4.
  • 5.
    What is theWSO2 Stack? •A full middleware runtime: • Application Server, ESB, Identity Access Management, Governance, Business Process, Gateway, Business Activity Monitoring, … • Modular – reconfigurable and extensible • Cloud-native • Deployable as a Cloud Solution/PaaS • Enabling for SaaS • Open Source under the Apache License • Supported 24x7 with aggressive SLAs
  • 6.
    WSO2 Carbon EnterpriseMiddleware Platform *
  • 7.
  • 8.
    Develop Once -Deploy Everywhere Stratos StratosLive Private Public PaaS PaaS Or, any combination of these. (Same programming model across all deployment choices) Carbon On-Premise
  • 9.
    How do OEMsuse WSO2? • Vertical solutions that require an SOA basis: • e.g. A distributed application platform • Migration from WebSphere, JBoss, etc to something more lean, cloud-ready and modular • Vertical versions of an SOA middleware: • SOA middleware customized and specialized to a particular domain (e.g. Financial, Healthcare, Defense) • Co-opetition • Other vendors who require a point solution as part of their stack • e.g. Registry, Identity Management, API Management • SIs or ISVs looking to build SaaS apps or multi-tenant solutions
  • 10.
    Understanding WSO2’s approachto Open Source • All WSO2 products are available under the Apache License (or Apache-compatible licenses for third-party dependencies) • We provide a full list of all components, their licenses and origins • We do not make patches or service packs available under the Open Source License • Customers or ISVs must either license those or wait until the next release comes out and upgrade • We provide 24x7 support with SLAs, patches, and Service Packs to our supported customers and to OEM partners
  • 11.
    Why work withWSO2 if its Open Source? • Can you just use our software without involving WSO2? • Yes • So why should I involve WSO2? • We support you so you be productive and support your customers effectively • Confidential relationship under NDA • Middleware is complex - this is our business and our expertise: we solve problems faster, advise on design, and help ensure that your customers get a fully supported system • It leaves you free to focus on your business • You get the benefit of patches and service packs to ensure problems are solved before your customers find them
  • 12.
    Why do OEMsuse WSO2? • Excellent technology • Many of our existing OEMs have done very detailed multi-vendor evaluations and found us to be the best • Modularity • Allows you to remove or add components to get “just the right runtime” • Allows extensions to be treated as first class • Cloud-native • The same apps can be run on-premise, in public cloud or in private PaaS • Open Source • Guarantees an open ecosystem • Makes your developers more effective
  • 13.
  • 14.
    QuickStart • Objective: From zero to working proof of concept or thin slice in one or two weeks • Training • On-site training on any combination of WSO2 products • Consulting • Help with designing customer's SOA solutions • Help with designing deployment architecture • Develop prototype code for customer scenarios • Assess and prepare project for production deployment • Follow up with 1 month Development Support
  • 15.
    Development Support • Access to on-line support system for: • Assisting customers with answering questions on any WSO2 product or technology: - Confidential forum - Guaranteed responses, 24-hour max SLA • Assistance with product tuning for performance, security and other needs • Developing samples or proof-of-concept implementations • Access to selected pre-production patches • 3/6/12 month packages with maximum hourly caps
  • 16.
    Consulting/Development Services • Consulting • Achieve a pre-defined objective: architectural design and advice, training, development assistance, custom development, deployment advice and assistance, etc. • On-site/off-site • Executive/Architect/Senior Engineer/Engineer • Daily/weekly rates • Development Services • Augment customer team for critical parts of a project • On-site/off-site • Monthly rates
  • 17.
    Production Support • Issue resolution on production systems • 24 x 7 x 365 support • Unlimited • Aggressive response/resolution times based on severity • Creation & delivery of patches against production version • Service packs applicable to the production version • Per runtime pricing • Warm instances, test instances, etc. all no charge
  • 18.
    Business Models • For low volume or initial engagements • You can simply resell our support to your customers • Many OEMs prefer to negotiate a more integrated deal • In this model we typically agree a “value” of the WSO2 contribution to the OEMs product • Use this as a starting point to agree a %age of revenue
  • 19.
    Technical Summary • Component-basedmodular approach • Complete end-to-end platform • Cloud Native: • multi-tenant, elastic, metered, billed, self-service • Interoperable: SOAP, REST, AMQP, XML, JSON • Innovative: the only complete and integrated Platform-as-a-Service • Available on-premise, in cloud, as-a-Service • A single cohesive codebase
  • 20.
    Business Summary • Anopen partner • Providing world class technology and support • With a set of existing OEMs in multiple business areas
  • 21.
    Contact us: Follow us: http://wso2.com/contact/ http://twitter.com/#!/wso2
  • 22.
    Thank you forattending! Questions Your feedback is very much appreciated