To Be (Open) or Not to Be (Open) – Dilemma of Pentaho Analyzer


First off – congratulations to our friends at Pentaho on making a great strategic acquisition of LucidEra’s ClearView product and embedding it in Pentaho Enterprise Edition. With this, Pentaho will completely replace JPivot as the web UI to view and report OLAP data. Many of us (including OpenI) have lamented about JPivot UI at one point or another, about not providing the desired eye candy effect, so for Pentaho to finally be able to pull this off is a great accomplishment, and hats off to them.

There is, however, one catch — this new UI replacement will NOT be available in the open source version. You have to buy the Enterprise Edition license to get this new UI.

Huh? I hear you say. Well-known BI columnist Seth Grimes questions “Is Pentaho, founded as a “commercial open source” BI vendor, still defined by open source? Pentaho itself seems unsure.” On the other hand, Julian Hyde, a well-respected BI technologist and the project lead of Mondrian, has a compelling rationale for Pentaho to keep this closed source. He says:

If you release a piece of software open source out of sheer, ‘I love the world!’ altruism, you won’t necessarily see much benefit. Pentaho is a for-profit business, and they are savvy about leveraging the benefits of open source software. And let’s not kid ourselves, there are considerable downsides to releasing something open source. Your competitors can pick up the software and incorporate your hard work into their suite. And your customers may decide that the free version is so good that they aren’t going to give you any of their money.

So given this, is it wrong for Pentaho to call itself a “commercial open source” company? In fact, does Pentaho platform even qualify as an open source platform anymore since a major component is only available in the closed source enterprise edition?

The answers, IMHO, are not straightforward.

The key issue is that the origin of open source was not based on making money, but rather based on sharing and leveraging what’s now called the “wisdom of the crowds”. Linus Torvalds uploaded his build of Linux including the source code not so much to charge fees for commercial license and support, but rather so that other like minded engineers will take the code apart, provide feedback, and better yet, improve and add new parts that make it better. And you can say the same about Apache, Mozilla browser, and many other similar well-known open source projects.

But then came people like us — we loved the open source model of developing and distributing software, AND we also wanted to make a living out of it. Initially, it was getting consulting gigs to integrate or customize your open source software, but that doesn’t scale as well. Enter “commercial open source” — first pioneered by the likes of Red Hat, SuSe, etc. to provide commercial license and support of Linux, this intrigued a lot of other open source projects. So soon you had Compiere for ERP, SugarCRM for salesforce automation, etc. etc. and in BI sector, enter Pentaho and Jaspersoft.

And when you are a commercial business, you have to continuously grow (especially if you have taken institutional investments) — so you look for all possible new ways to create new lines of products and services. For closed source commercial enterprise software, this usually resulted in feature and code bloat. And now for commercial open source companies like us, this means creating new “Freemium” models — i.e. what else can we build around the open source software that we can get paid for.

So, as a business — Pentaho has all the valid reasons to justify not open sourcing the new ClearView based UI for OLAP reporting. It developed (acquired) the technology all on its own, it has resources to continually test/improve it (i.e. doesn’t really need community contribution to succeed), plus there is a reasonable market demand — so, why not charge for it and create a sustainable commercial infrastructure?

The argument then is mostly philosophical of whether Pentaho still qualifies as an “open source software”. Some are calling it “Open Core”, probably more aptly.  The only drawback is that is someone, for example us guys at OpenI, want to collaborate/experiment building on Pentaho platform leveraging the ClearView UI features, we can’t do that in an open source model. We will have to become a Pentaho partner, get a restricted license to the code, and whatever we build on top of it, we can’t redistribute it as open source. How much that affects Pentaho, only time will tell.

There was recently a much publicized debate on a similar topic when Chris Anderson’s book “Free” (first published as a Wired column) came out making a strong case for future belonging to products that are built around a free version, and Malcom Gladwell had a reasonable disagreement where he said:

…Anderson is forced to admit that one of his main case studies, YouTube, “has so far failed to make any money for Google.” Why is that? Because of the very principles of Free that Anderson so energetically celebrates. When you let people upload and download as many videos as they want, lots of them will take you up on the offer. That’s the magic of Free psychology: an estimated seventy-five billion videos will be served up by YouTube this year. Although the magic of Free technology means that the cost of serving up each video is “close enough to free to round down,” “close enough to free” multiplied by seventy-five billion is still a very large number.

Ultimately, “Free”, whether it’s OpenI or Pentaho or Gillette razor, can only succeed if the people making the “Free” have a way to get paid, and a way to scale the business profitably. In the absence of that, the people making the “Free” will not survive, and when they are gone, the “Free” product goes away as well. That is also our rationale for providing commercial support and integration for OpenI — we need to generate revenue in order to continue supporting OpenI, and contrary to popular belief, majority of the open source projects can’t succeed on volunteer contributions alone. So, as much as I’d have wanted Pentaho to open source their ClearView UI, I have to admit that making it a part of paid version will benefit the health of their company, and thus increase the chances of them being around to continue supporting the “Free” model. And these things aren’t set in stone? What’s “Closed” today, can become “Open” tomorrow  — as long as there are other new “Freemiums” to offset the switch.

3 thoughts on “To Be (Open) or Not to Be (Open) – Dilemma of Pentaho Analyzer”

  1. Sandeep,

    Thanks for the kind words. I know you just raised the questions and are not making any accusations but I’d like to add my 2 cents:

    “this new UI replacement will NOT be available in the open source version”
    – One consideration that you fail to address is whether Pentaho can legally open source the code it acquired. I think that would be an important part of the discussion.

    “… does Pentaho platform even qualify as an open source platform anymore since a major component is only available in the closed source enterprise edition?”
    – The functionality of this “major component” does exist, as you point out, and has existed in the Community Edition, via JPivot. We think ClearView has a better presentation and is easier to use, but it is functionally similar to JPivot. There are even some techie things that JPivot does that ClearView doesn’t. I fail to see how we could qualify as an open source platform last month and somehow become less open source because we provided an alternative interface to existing functionality. That seems silly to me.

    “…is it wrong for Pentaho to call itself a “commercial open source” company?”
    – I’ll reiterate what I said on Nick Goodman’s blog: What do we do at Pentaho? We write business intelligence software that is open source and we write a lot of it. We also write proprietary software and have bought proprietary software to extend our open source software and we sell it. Selling a proprietary product does not negate what we do in open source.

    I’m sure that even Linus Torvalds has some software that he hasn’t uploaded as open source. In fact, it is very likely that he has even written code for an employer or customer since his first upload of Linux that was not open source. I hardly think that that would strip him of his open source developer status. Some may disagree but, I think we have earned the right to say that we are an “open source business intelligence company” regardless of whether we also write and sell proprietary software.

    Finally, the term “Open Core” *is* more technically descriptive of our product strategy and is not a name we disagree with. In fact it is the criteria we use when making the decision to have a proprietary feature, a decision that we do not take lightly. I don’t think using it over “commercial open source” adds much value or differentiation for people interested in buying a BI solution. Maybe in the future when it is as well known and commonly used as “commercial open source” – that opinion will change. At this point, I think it’s just a fun little distraction for us (the people close to open source) to talk about.

    Doug Moran
    Pentaho Community Guy

    1. Hi Doug:

      Thanks for your 2 cents.

      I think ultimately this decision from Pentaho compels us all to question what does it mean for a company to be “open source”. To that end, some observations about your feedback:

      • I had no knowledge of any legal restrictions on your part to open source ClearView code. I simply assumed that if you own something, you do have a choice to open source it — and I thought that the decision not to open source it and include it in the enterprise edition was more driven by business/revenue rather than legal restriction. Still, you bring up a valid point that I hadn’t considered
      • As far as does Pentaho qualify to call itself “open source”, etc. I don’t think it really matters in the market either way. As you pointed out, it’s probably a more fun little distraction for open source practitioners to talk about. Your customers want value, feature, and good support – and whether or not the code is open source is probably not their #1 concern when they evaluate your software.

      However, not open sourcing ClearView code does make it difficult for someone outside Pentaho to “tinker around” and make contributions to that specific component. Now, that may not matter to you because you already have adequate resources to support/improve that component, but it does close the door to applying an open source development model to ClearView code (unless they become an OEM partner). Ultimately, ClearView component raises the bar for what the community edition and other open source alternatives like OpenI — which is a good thing.

      And above all, I still commend you all for making a brilliant acquisition, and wish Pentaho continued success.



  2. Sandeep,

    I almost forgot, since this hasn’t been mentioned anywhere in all the discussions, I thought I’d mention it here…

    The last proprietary software we purchased *was* put into open source. The original Report Designer: In this case it made perfect sense to put it into the open since it filled a major hole in the suite and would really benefit from the open source development model to add missing features.

    “However, not open sourcing ClearView code does make it difficult for someone outside Pentaho to “tinker around” and make contributions to that specific component.”
    – This is a very true statement and it also puts a lot of pressure on us internally to test. QA is tremendous value we get from the non developer community. The trade off between engineering cost and the perceived business value is very hard to quantify and I assure you it is hotly debated internally every time it comes up.

    I agree that it raises the bar and I believe that competition is good. The community is currently working on it’s own alternative to JPivot – The PAT project: I am sure that they would greatly benefit from your expertise and tinkering.


Leave a Reply to Doug Moran Cancel reply

Your email address will not be published. Required fields are marked *