Open core has become a nasty phrase in some circles. Perched high on the fence that separates open source and proprietary software, the open core model has caused debate ever since it first emerged. Open core companies that enter the market with the best of intentions all too often prioritize their enterprise products (or, more to the point, the financial opportunities that they create) and allowing their communities to slowly decay. The open core model has worked, though…and when it does work, it creates explosive growth for the business, the technology, and its community. With the right leaders and priorities, it is possible to consistently make product decisions that are both profitable and community-friendly. In this session, Yves de Montcheuil from Talend talks about how his company approaches the open core model, where it’s worked, where it’s been surprisingly difficult, and how to maintain community values when divisive commercial opportunities become increasingly hard to resist.

1. Making Open Core
Product Decisions
OW2con’13
Yves
de
Montcheuil
@ydemontcheuil
©
Talend
2013
1

2. Open Core and Open Source
➜
Open
Source
is
not
a
business
model…
• Open
Core
is
not
Open
Source,
and
vice
versa
➜
Open
Source
is
• A
way
of
developing
soHware
• A
way
of
providing
soHware
• A
collaboraIon
philosophy
• The
“3
(or
4)
fundamental
freedoms”
of
open
source
➜
No
such
thing
as
“Open
Source
Vendor”
©
Talend
2013
• Freedom
0:
The
freedom
to
run
the
program
for
any
purpose.
• Freedom
1:
The
freedom
to
study
how
the
program
works,
and
change
it
to
make
it
do
what
you
wish.
• Freedom
2:
The
freedom
to
redistribute
copies.
• Freedom
3:
The
freedom
to
improve
the
program,
and
release
your
improvements
(and
modified
versions
in
general).
2

3. Defining Open Core
➜
Spectrum
of
business
models
• (No
business
model
–
community
only,
foundaIons)
• Services
• Dual
licensing
• Open
core
• Core
is
GPL:
if
you
embed
the
GPL
• Proprietary
extensions
in
closed
source,
you
pay
a
fee
• (Full
proprietary)
• Technical
support
of
GPL
product
➜
The
first
Open
Core
definiIon
• JaspersoH’s
then
Director
of
Biz
Dev
Andrew
Lampi[
in
an
August
2009
post
• GPL
or
not
GPL?
That
is
the
quesIon
©
Talend
2013
may
be
offered
for
a
fee
• Annual
commercial
subscripJon
includes:
indemnity,
technical
support,
and
addiJonal
features
and/or
plaLorm
support
• Professional
services
and
training
are
for
a
fee
3

4. Benefits of Open Core for User
➜
Freely
usable
enterprise
grade
soHware
• Bells
&
whistles
• Including
“non
graIfying”
features,
such
as
UI/wizard
work
• Usability
• UI
consistency,
wizards,
online
help
• AdopIon
materials
• Tutorials,
documentaIon,
etc.
➜
Supported
and
maintained
by
vendor
• No
SLA
does
not
mean
no
commitment
➜
“Upgrade”
path
• Including
IndemnificaIon
©
Talend
2013
4

5. Benefits of Open Core for Vendor
➜
Viral
adopIon
• Freely
downloadable
soHware
• Word
of
mouth
• Blogs,
forums,
Twi[er,
etc.
➜
Community,
contribuIons
• Community-­‐centric
process
• Orchestrated
by
vendor
• Engaged
users
are
likely
to
donate
back
• Intangible
contribuIons:
help
others,
test/review
soHware,
etc.
• Tangible
contribuIons:
code,
extensions,
doc,
tutorials,
features
requests,
etc.
• A
strong
community
is
a
must-­‐have
for
any
open
source
project
©
Talend
2013
5

6. Beware of Subterfuge
➜
What
Open
Core
is
not
©
Talend
2013
6

7. Example of an Open Core Stack
TALEND PLATFORMS
➜ Bundles
of
Enterprise
products
➜ Advanced
features
Big
Data
Data
MDM
Management
Data
Services
Enterprise
IntegraIon
TALEND ENTERPRISE
➜ PlaInum
support
➜ Commercial
license
➜ SubscripIon
model
Big
Data
Data
IntegraIon
ESB
➜ Support
included
TALEND OPEN STUDIO for
➜ Open
source
license
Big
Data
©
Talend
2013
Data
Quality
MDM
Data
ESB
BPM
IntegraIon
➜ Free
of
charge
➜ OpIonal
support
7

8. Zooming Inside the Stack
Talend
SubscripIon,
Plaoorm
for
commercial
Data
Management
Talend
Enterprise
Data
IntegraIon
SubscripIon,
commercial
All
of
below,
+
• Deployment
environment
• CollaboraIve
repository
• ProducIvity
features
Talend
Open
Studio
for
Data
IntegraIon
©
Talend
2013
All
of
below,
+
• Data
quality
&
profiling
• High
availability
GPL
•
•
•
•
Development
environment
Graphical
studio
All
connectors
&
components
Metadata
management
8

9. The Trade Offs
➜
“Community”
EdiIon(s)
vs.
“SubscripIon”
EdiIon(s)
• Terms
may
vary…
need
a
way
to
express
clearly
what
is
each
➜
Careful
arbitrage
• Weigh
each
feature
• Contribute
equally
to
both
➜
Must
maintain
the
balance
• Fork
as
way
for
community
to
react
©
Talend
2013
9

10. Standing on a Narrow Ridge
➜
Permanent
balancing
act
• Add
too
much
to
Community
EdiIon/
too
li[le
to
Enterprise
EdiIon
• AdopIon
up
• Conversion
down
• Add
too
much
to
Enterprise
EdiIon/
too
much
to
Enterprise
EdiIon
• AdopIon
down
• Conversion
up
• The
key:
keep
the
balance
©
Talend
2013
10

11. Examples of Open Core Decisions
SAP
Support
Talend
Open
Studio
for
Data
IntegraJon
Talend
Enterprise
Data
IntegraJon
Connectors
included
Metadata
support
Wizards
Direct
access
to
SAP
metadata
documentaIon
©
Talend
2013
11

12. Examples of Open Core Decisions
Teamwork
CapabiliIes
Talend
Open
Studio
for
Data
IntegraJon
Talend
Enterprise
Data
IntegraJon
Single
user
environment
Export
&
import
capabiliIes
Versioning
©
Talend
2013
Shared
mulI-­‐user
repository
Lock
mechanisms
Access
rights
12

13. Examples of Open Core Decisions
Joblets
Talend
Open
Studio
for
Data
IntegraJon
Talend
Enterprise
Data
IntegraJon
Copy/paste
of
job
elements
Joblets
for
reusability
©
Talend
2013
13

14. Examples of Open Core Decisions
Event
Monitoring
in
ESB
Talend
Open
Studio
Talend
Enterprise
ESB
for
ESB
Published
database
structure
©
Talend
2013
Service
AcIvity
Monitoring
Dashboard
14

15. Thank You!
Yves
de
Montcheuil
yvesm@talend.com
@ydemontcheuil
©
Talend
2013
15