Slashdot Mirror


Making Money In Open Source

Khalid writes "An interview with Sleepycat President and CEO, Michael Olson, it brings a lot of interesting information about their business model and licensing scheme. A lot of good ideas, when a lot of open source based companies are struggling for life. "

15 of 188 comments (clear)

  1. read carefully: opensource based _COMPANIES_ by jukal · · Score: 4, Insightful

    I don't think there is any magic in it.
    If it's a COMPANY it need to be run like a COMPANY. A BUSINESS.

    In my opinion the fall of many opensource based "companies" has been the fact that they never were COMPANIES - but instead a collection of enthusiastic nerds.

    Opensource is not the complete answer for a company strategy unless you are planning to eat rice for the lest of your life.

    1. Re:read carefully: opensource based _COMPANIES_ by NullAndVoid · · Score: 3, Insightful

      Most dot-coms failed because of a bad business plan. Why? Cause the management were a bunch of nerds that had no experience with business plans.

      Really? Most of the dot.coms I personally dealt with were run by MBA's who spent a great deal of time on spiffy business plans, backed with spreadsheets with hockey-stick shaped revenue projections, and glossy power point presentations.

      --


      -- Sigs are for losers
  2. A lot like TrollTech by update() · · Score: 4, Insightful
    Their plan seems to be a lot like TrollTech's -- they dual license their library under a GPL-like license and a for-money license. They reap the benefits of open source (wide distribution, many eyes, contributions back) but make money from companies that don't want to free their own products.

    Now that the megalomania, greed and excess of the Linux boom days has disappeared, it's clear that raising a mountain of money from VC's and an IPO and overthrowing Microsoft and Oracle isn't the way to succeed for a free software developer. On the other hand, growing at a reasonable rate, living off revenues and (duh) making a really good product like Qt or BerkeleyDB can make you a nice living.

  3. Making "money" vs "a living" by j-beda · · Score: 5, Insightful
    OFten it seems to me as though when people talk about "making money" in Open Source (or in other contexts) they seem to be talking about "making shitloads of money", often with the idea of not doing much work.

    Maybe we should refocus our attention on making "reasonable" or "sufficient" amounts of money. Statistically speaking, in most fields, nobody makes the bigs bucks.

    In sports there are many many minor league players just scraping by for each major league bazzillionaire. In business, most places are small mom-and-pop (more than 50% of the US ecconomy?) compared to the relatively few McDonalds out there. Maybe Open Source is a bit different in that it is virtually impossible for there to be even this many (or any?) BIG winners - but that doesn't mean that everyone is thus forced to be a "looser".

    It seems as though there are lots of opportunity for making a living with creation, support, etc. of Open Source solutions to various people's problems. And in fact there are a lot of people making decent livings providing those services.

  4. Making money is hard to do by snoozerdss · · Score: 2, Insightful

    If you look at many examples it's hard as hell to make money with open source. On the other hand it's alot easier to SAVE money with open source. For example switching over to linux servers like mentioned in that recent slashdot article. Switching applications over to open source as well. I can see people saving money with open source but making money, well thats easier said then done.

    --
    Snoozer.
  5. You are right by einhverfr · · Score: 5, Insightful

    Most OSS companies don't know how to run a business because the paradigm and rules of the game are too different. Look at Caldera, for example. There is a company which seems bent on selling Linux as if it were proprietary software, which looks like the safe choice to the novice, but really provides the worst of both worlds...

    The real problem facing OSS companies is that the rules of the game are so different than they are for proprietary software companies. You cannot make your money on licensing because if you try to do that, your competition makes a cheaper clone. OSS commoditizes the software market.

    I think that companies like Sleepycat are honestly trying to find out how to make money in a commoditized world, but I think they will have to transiton into another mode. Repeat after me: "You cannot make money selling open source software that you develop yourself." The market is simply too competitive.

    What more companies need to do is offer tailored services, utilizing open source software to produce less expensive, more competitive packages of services. Of course, then you are competing with IBM, etc. but I suspect that this is EXACTLY why IBM is starting to move more open source.

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:You are right by Z4rd0Z · · Score: 3, Insightful
      You cannot make your money on licensing because if you try to do that, your competition makes a cheaper clone.

      That is what they're doing, however. They have a dual licensing scheme that allows customers to incorporate the db software into proprietary products. They are targetting the embedded market, where companies usually do not want to release their source code. You're right, though, if someone came along and made a BSD licensed clone, that would probably kill them. However, if they make the best available product for the price, they will probably continue to make money. It sounds like they have something good going, they have made profits without any outside investors since they began and have continued to grow. They have only 13 employees. This is quite different from failed companies like Eazel that got tons of venture capital and blew it all in one shot. They're making money on their merits, not on open source hype.

      --
      You had me at "dicks fuck assholes".
  6. It's a cultural thing... by sterno · · Score: 5, Insightful

    A large number of americans have a lottery mentality that they are always looking for some way to make lots of money with little effort. All of the economic bubbles have been built on this tendancy. The dot com boom and the related boom in VC funding for open source was all about getting the big payment without doing the hard work. When the dust settled turned out a lot of those companies didn't have a clue and died.

    I think there's a lot of money to be made on open source, but that's spread out over a lot of people. Support, custom development, integration, lots of useful stuff that isn't sexy and isn't going to make anybody fabulously rich but is valuable and will provide a more than adequate living for a lot of people.

    I think if anything open source is a big bomb shell for the whole notion of making the big money. A lot of companies who got cozy making proprietary software, charging huge license fees and then selling exhorbitant support contracts on top of that are in for a big wake up call. When everybody can have access to the code you don't need to be addicted to one vendor. That breeds competition, and competition drives down prices. Those companies that can provide the best services for the best prices and can create the best brand will be the ones collecting the money in the future but because they necessarily must be efficient it won't be the really big money.

    --
    This sig has been temporarily disconnected or is no longer in service
  7. billyuns for everybuddy? I DOWt IT by Anonymous Coward · · Score: 1, Insightful
    Seeing as the VAST majority of end users/businesses are NOT in the software 'business', I doubt they could give a fud whether or knot o-s is a money-maker. They are, however, VERY interested in dependable/economical solutions to father williams' gangster liesense bugwear hostage scam, & will pay somebodies to help in that area.

    It's hard to imagine anyone paying thousands of dollars for ViWormic M$BugWear (then paying someone else to pretend to make IT work for them), when superior alternatives, are available, absolutely free, but it does show the power of deceptive marketeering. Who wants to be LIEk that? In the gnu/o-s world (dare I use the two in the same post?) there is no eternal liesense/'upgrade' path, therefore no billyuns, or stuck market FraUDs, to be perpetrated (other than the ones already being prosecuted). So, here/there we are, with the best solutions that can never be sold in some canned version. Most likely j. public will have to take IT in the .asp for a while longer, before he can see the function (or lack of) behind the ?pr? bs. EVERY person I speak with, is angry/discouraged/disgusted with father williams' garbaage, but is resigned to believing that's the way IT is.

    God willing, when j. finally does get the head extraction he's been promising himself, there'll still be some choices available. We'll still be here (increasingly busy ourselves lately). Meanwhile, don't forget to check out our web address giveaway. Includes a year's free hosting. Just in case o-s/the web/commerce, etc... continues in some form.

    Today, I heard again, the rumour that fud is NOT dead. Hard to believe, having seen the face scans, of the gottiesque felons of the kingdumb. They are the REAL .commIEs, know? Next, we're starting to work on this cite.

  8. Re:They did not say several important things: by technos · · Score: 4, Insightful

    What always seems to surprise me is the total lack of 'talking'.

    "Gee, I'd really like to use SpamFooOODBMSRTC in my project. But Alas! It is GPL and I'm stuck to BSD!"

    Why not drop the developer/company an email?
    "Hey! I've got this great FourthGenerationDiscoBobulatingDooHickey! It would work great with your SpamFooOODBMSRTC!! How can we arrange to do it? Can you grant me a different license that would work? Y'know, dual licensing? Is there some way I can add or use an exposed API and not need to redistribute your source? Can I get some old source under a different license? Mabye you can just promise, as copyright holder, not to sue my ass off?? I promise I will give you the changes I make under whatever your license is."

    --
    .sig: Now legally binding!
  9. Not Making Money In Free Software by Florian+Weimer · · Score: 4, Insightful
    If I understand the license situation correctly, Sleepycat makes money because others do not want to release there software as Free Software. This is slightly different from true Free Software companies such as Ada Core Technologies (ACT) which usually do not slap different licenses on public and customer versions of a software package.

    In fact, Sleepycat's business model stops working if the Free Software revolution has taken place because no one would need a proprietary-compatible license for Sleepycat's software. ACT's business model continues to work because their customers still need support, and still pay for enhancements to the GNAT toolchain.

    I guess Sleepycat is just an Open Source company, but not a Free Software Company. ;-)

  10. It's in the hardware by Lance+Fuckhoff · · Score: 3, Insightful

    The only way to make money in open source is hardware revenue. IBM and Apple both understand this, but apparently no one else does.

  11. Re:Software for its own sake? by seanadams.com · · Score: 3, Insightful

    If we learned anything last year, it's that you can't make money giving stuff away for free (duh). But "freeness" barely scratches the surface of what open source is all about.

    I remember that the user's manual for my first Apple computer came with a huge fold-out schematic of the entire motherboard. The design wasn't free, but it was open insofar as I didn't have to reverse engineer it just to hack on it. Do you think any more than a tiny handful of Apple's customers had the faintest clue what to do with the schematic? Or course not.

    However, when you open up your product, even if it's not to the full extent of GPLing everything, you're inviting hackers and hobbyists to develop all sorts of software and peripherals... AND THIS HELPS YOUR BUSINESS ENORMOUSLY!!! Open source developers sometimes do it because they want to give something to the world. Other times, we do it because we just want to improve the stuff we own. We share our changes because it doesn't cost us anthing to do it.

    It's not too hard to think of business models where both your customers *and* your business can benefit from open source. Make a software product and open source the hardware, or <plug>make a hardware product and open source the software</plug>. You could even make a software product and open just part of it. Neither the open source community nor your customers will demand that you give away the farm for nothing.

  12. Re:Step 1 - Choose a good name by sgups · · Score: 2, Insightful

    Well umm the guy said they dont have any outside money and they depend solely on revenues...
    Plus umm Red Hat or Mandrake arent exactly techy sounding names, if thats your criterion for investment anyways

    --
    Democratic USA - Government of the corporations, by the Corporations, for the corporations.
  13. Re:Dual licensing still sounds dodgy to me by crosbie · · Score: 2, Insightful

    Yeah, I wondered about this too.
    A GPL license still applies even to the company that issues it. Just cos you wrote it doesn't mean you're uniquely positioned to sell it under both a GPL license and a proprietary license. Sure, you can cobble a license that looks like GPL, but has this tiny little amendement that permits dual licensing...

    That's harnessing the hard labour of the Open Source developers, and saying "Thanks lads, we'll just take all your hard work on enhancements and fixing the bugs, apply it to our proprietary version, and we can then flog it off under a closed source license to the big boys, who can flog it off in their proprietary stuff, etc."

    They should come clean on this. It's a BSD license in GPL clothing!

    Nothing wrong with a BSD license of course, but at least it's upfront and honest and let's everyone know that it's free to be utilised in proprietary software.

    A true GPL license has no back doors.

    And yeah, the LGPL is a fine compromise and marks clear boundaries between GPL code and potentially proprietary code. I got no problem with companies utilising LGPL modules alongside proprietary ones.