Profiting from Open Source Software 149
Secret Santa writes "Alex Salkever has written an inspiring and Linux-friendly piece about Martin Roesch -- how he went from writing open-source software to building a multimillion dollar company. Excerpt: 'Sourcefire is one of a growing number of small software players that have built new businesses around open-source code. Their business models contain various mixes of proprietary and open-source software components and span the software gamut, from other security companies such as Tripwire to database outfits such as MySQL and desktop-computing offerings like Xandros. Most are still small, with revenues well under $50 million.'"
Nothing New (Score:1)
Re:Nothing New (Score:2)
Re:Nothing New (Score:2)
I too was hoping to hear more such stories. Anyone have some to share ?
Or (Score:4, Funny)
At last! (Score:3, Funny)
Re:Looks like SCO figured this one out... (Score:2)
Open Source Business (Score:5, Interesting)
My first product worked so much better than the alternatives, and cost so much less to implement, that I have no problem making good money this way.
Re:Open Source Business (Score:3, Insightful)
Re:Open Source Business (Score:5, Insightful)
Ehhh, there's also the matter of different levels of resource allocation. If doing a given thing for a single platform takes x effort, then for a one-programmer shop, doing it for n platforms takes damn near nx effort. If GP poster is happy working only on Linux, and the services he provides have a wide enough market, there's probably enough room for expansion without him having to target other platforms. Now, if he were running a larger consulting firm, I'd agree with you that he's foolishly limiting himself, but it doesn't sound like that's the situation here.
No... (Score:2)
If you aren't part of the solution, there's good money to be made prolonging the problem.
http://www.despair.com/consulting.html [despair.com]
Re:Open Source Business (Score:1)
So, in other words, you're saying not to use Windows.
Re:Open Source Business (Score:3, Insightful)
So he only accepts jobs where Linux is the right tool. Problem solved.
Re:Open Source Business (Score:2)
There seems to be an assumption on your part that the linux market is going to dry up, a shaky point of view, to say the least.
I consult on the side, and I also turn down the non-linux work, since there's already more linux work coming at me than I can currently accept, and let's face it, life is too short for the kind of grief that comes from a blue screened windows server at 3 am, or struggling to build and configure something like postfix, amavis, clamd, spamassasin, apache+ph
Re:Open Source Business (Score:2)
MSCE's are a dime a dozen. Specialization is not a waste of time and certainly does not guarantee failure. Sure, you can't shoe-horn solutions, but you can identify a
Re:Open Source Business (Score:2)
Yes, it means that there are jobs you will have to say no to, because they are not within your particular expertice. But for the jobs that lies within your field of expertise, you will be the best.
Both specialists and generalists are needed, which one you choose to be should depend on where your talents lie: In getting a broad overview, or in diving deep into a particular aspect.
Nerds tend to be specialists.
Re:Open Source Business (Score:1, Informative)
Re:Open Source Business (Score:2)
Re:Open Source Business (Score:2)
Re:Open Source Business (Score:2)
Re:Open Source Business (Score:1)
Re:Open Source Business (Score:2)
My point is that this is not the kind of model that pays for dinner, let alone the rent/mortgage, daycare, healthcare, gas.
Sourcefire reseller reporting. (Score:5, Interesting)
Re:Sourcefire reseller reporting. (Score:5, Interesting)
I read an article a few days ago by Ted Turner of all people. He openly deplored the oligopoly that's strangling America's business while discouraging competition and innovation.
The companies which seem to have made it big in the past year or so (like google [google.com] have done so probably in large part because they didn't turn into a big wad of shellac like Yahoo - that is, because they're not evil. It's funny that the business innovation which is turning out to be strong enough to trounce the big boys even in this environment is Good. You see it in other places too, like In & Out Burger, where the workers are fast, happy, efficient, and very well compensated (general managers make like $80k+, so I'm told). Sheesh, this almost makes a man optimistic.
That said, beating Yahoo isn't as big as beating IBM. Yahoo only had a couple of years to get established, IBM's been pushing out tills since before World War II. And because I know there are trolls out there, I don't think even the USPO would let somebody patent Good.
Money in OSS? (Score:4, Informative)
This must be wrong. Bill Gates told me there isn't any money in open source software. The guy probably stole the money from SCO.
But seriously, there's not much meat to the article. Basically, what it says is:
Re:Money in OSS? (Score:2)
Look. I said that there is no money from Open source software. I did not say there was not money from owning it and suing everyone on the planet who did not pay SCO.
Sco has made alot of money owning free software. Get with the program.
Re:Money in OSS? (Score:1, Insightful)
RTFA again. The Snort guy also says that there's no money in open-source software, which is why he came up with this mixed model.
Oh, and every time Gates is right and you're wrong, you have to give him 500 million dollars. Sorry about that.
Re:Money in OSS? (Score:5, Informative)
He's behind Sourcefire, not Sourceforge. Though his open source software is stored in the Sourceforge repository.
Though it is probably superfluous to point it out here at
Re:Money in OSS? (Score:1)
http://www.vasoftware.com/sourceforge/difs.php [vasoftware.com]
And VA Software is "the guy" behind it.
Re:Money in OSS? (Score:5, Interesting)
Besides, open source keeps you honest. If developers see shitty coding practices it will out and/or be cleaned up, rather than swept under the rug.
Also good for software enhancement as it's more democratic this way. Pretty much anything I've ever come up with, on my time, I've released with the code. Though I doubt much of it has made it's way to sourceforge. I'd only care if someone slapped their name on it and claimed it as their's, particularly if they were selling the product commercially.
Profiting from Open Source Software 101:
Re:Money in OSS? (Score:2)
Better idea: hire people to do installation, training, and technical support for your software. Hire somebody else to manage these people. Use the profit from this enterprise to let you develop the software itself full time. A million and one F/OSS developers will tell you "but I don't want to do tech support." And I don't blame them. There are better options. Coders shouldn't be wasting their time doing support for the c
flamebait? (Score:1)
I'm all for open source, but expecting to profit from software you release under an open license will lead to disappointment.
Personally, I think I'm going to go the crippleware route. And sell the source to commercial users so I never have to spend my nights/wknds supporting it again.
Re:Money in OSS? (Score:3, Interesting)
Unfortunately, most of "us" don't know how to read a financial statement, and wouldn't know that Red Hat still isn't very financially stable, and their "profitability" comes from accounting tricks. For me, I was impressed by the article. It seems like they have a somewhat solid footing, which is very very rare for a company prod
Re:Money in OSS? (Score:2)
Timesys [timesys.com]. MontaVista Software [mvista.com]. Trolltech [trolltech.com]. SuSE [www.suse.de]. IBM's Linux ventures [ibm.com].
My current employer uses and contributes to open source software, although we're a proprietary software company -- using OSS tools for infrastructure functions saves us money, and contributing back reduces our software maintenance costs. My last employer is a member of the above list. They survived the bust, and I've heard rumors that they've starte
Re:Money in OSS? (Score:2)
Sometimes, articles aren't news, and aren't meant to be in-depth technical discussions. Sometimes (especially in a fluff rag like Business Week) they're just articles featuring someone or something.
As long as I can make a living... (Score:2, Interesting)
Re:As long as I can make a living... (Score:2)
Hey, if that's the job your skills deserve, you better train harder or learn to be happy with it. Neither the government, nor copyright law, was created to gaurantee you a cushy living.
Isn't that the dream? (Score:5, Insightful)
Profitable OpenSource dream? Not mine. (Score:2)
Gareth Keenan: Hmm?
David Brent: We're just doing the ultimate fantasy, we're all doing it.
Gareth Keenan: Two lesbians probably, sisters. I'm just watching.
Rowan: OK. Erm. Tim? Do you have one?
Tim Canterbury: I'd never thought I'd say this, but can I hear more from Gareth please?
The dream became a reality... (Score:3, Interesting)
Re:The dream became a reality... (Score:1)
Damn.
For a moment there, I thought you were referring to GoofyBoy's bit from "The Office."
Re:Isn't that the dream? (Score:2, Interesting)
That's not always a good idea. Just look at the guy who created TOra. For those not in the know, it's one of the most advanced OSS tools for Oracle developers; it runs on Windows and on Linux, it's Qt-based. The big package for windows was always TOAD, by Quest software. So, what did Quest do? Offer Hendrik Johansson a job, claiming that he could move from Sweden to the USA, and be paid to work at TOra. Guess what? When he accepted and had moved, they h
Re:Isn't that the dream? (Score:1)
Re:Isn't that the dream? (Score:2)
The key is to develop the software from day one with users in mind. It has to be a good solution to a clear problem. You can't just write software that you think people might possibly want and expect it to magically take off. F/OSS requires just as much market analysis as proprietary software. Obviously that analysis includes a thorough understanding of the technical challenge at hand.. and this is where many traditional companies go wrong.
opensource potential (Score:1, Interesting)
The effects of patents (Score:5, Interesting)
I haven't seen anyone doing this lately; at least, not outside of Open Sourced efforts. It seems like if you go the closed source, proprietary route these days, you'd better have a good deal of cash to fight the Patent Wars against the freeloading lawyers who come along. I can think of several examples. Yet no one seems to target the Open Source Companies and try to shut them down. So it seems like this is the only way the little guy can hope to win, without having to bend over for the VCs.
So, my question to the community is this: Are they any modern examples out there where an individual can successfully go it alone these days (all the way to IPO)? And if not (or if these are the exceptions), to what degree is this due to Software Patents?
My suspicion is that there aren't any, or at least many, modern examples these days of people being successful without the money to create one's own patent portfolio and defend themselves, legally. And if this is indeed the case, it's a superb example of how software patents have hurt the industry, rather than helped it.
A bigger probem, companies can't save money (Score:2)
A bigger problem is the lack of tax-sheltered savings for small companies. You cannot "save-up" money very efficiently, because at the end the year the tax man takes so much of your savings.
So you are forced to go begging for any capital you might need to expand. And small companies are forced to try to spend all profits by the end of the year to avoid taxation.
What we really need is something like an IRA for small companies, to save money tax-deferred, until there is a big enough pile to make the inv
Re:A bigger probem, companies can't save money (Score:2)
Re:The effects of patents (Score:2)
While patents are abused, the issue isn't patents at all. Years ago, there were few building blocks to make software. Each part had to be put together from scratch. For example...
20 years ago, if someone came out with a debugger the
Re:The effects of patents (Score:2)
Re:The effects of patents (Score:1, Interesting)
It's a heck of a lot easier (and cheaper) to publish something under an Open Source license, than it is to get a patent for it.
Which seems to imply that, as more people come to understand and appreciate Open Source, they will tend to provide more innovation under it. The only other way to go is with lots of funding, which takes time and effort away from innovation.
It would be ironic if the only way to do actual innovation w
Selling GPL'ed Software (Score:2, Informative)
You are correct (Score:2, Insightful)
Re:You are correct (Score:1)
Re:You are correct (Score:2)
Re:You are correct (Score:1)
Re:Making money from OSS (Score:1)
In it he explains the difference between 'sale value' which is usually realized by selling proprietary bits, and 'use value'. Also why even though it is theoretically possible to derive 'sale value' from OSS, it is practically never done. The fact is that the real value in S/W (not just OSS) is in the 'use value', and that value is mostly derived from support, upgrades, training etc. etc. The software business is really a
Re:You are correct (Score:2)
It depends. (Score:2)
Seems to me... (Score:3, Interesting)
2) What it seems to suggest is that hybrid models combining some open-source goods and a general use of the "open-source culture" with some proprietary products is the way to go, especially for a product where you can't expect to create a lucrative consulting business.
3) I suspect 2) works a lot better when you market to businesses than if you tried to sell to individual users who are allergic to paying for software and have a sense of "You owe it to The Community!" entitlement that corporate users lack.
Re:Seems to me... (Score:2)
I agree. Fact is, anybody could have written a 3rd party proprietary interface to Snort. (Just like there is 3rd party software that tries to make Windows more tolerable) This is not a case of directly profiting from OSS. The success of Snort and the proprietary products are closely linked, but you really have to separate them. And what happens when the various open source interfaces to Snort improve to the po
How... (Score:3, Interesting)
Anyways, there you have it folks. Free engineering from a large community. Thats what the buisnesspeople want out of open source. And the profit comes from making the interface.
But... is it possible for Interface design profit to sustain code design in the long run? Once open source interfaces catch up, will this niche remain?
No UI folks in OSS? It's a cultural thing. (Score:5, Insightful)
>
>Anyways, there you have it folks. Free engineering from a large community. Thats what the buisnesspeople want out of open source. And the profit comes from making the interface.
Great developers seldom make great user interface designers. The skillsets are wildly different.
Great developers solve problems and scratch itches. They're not so great on making it usable, because they don't need usability to scratch that itch.
How many times have people whined about, say, how hard it is to set up video capture on Linux, only to be shot down with an arrogant or condescending "Hey, luser, I didn't write this for you, if you don't like it, code your own!"
"Well, fine, but I can't!", screams the UI dude. Because great UI designers aren't only "not great developers", many "aren't developers at all!". Some UI folks work on a project from genesis to release without ever seeing a line of code; they just talk to humans, mock up UI designs on storyboards in Photoshop (sorry GIMP fans :), take prototypes to humans, watch the humans use the prototypes, talk to the humans some more, and then come back with long lists of changes for the developers to make.
Does that sound like "fun" for anybody here? Let's face it - UI design, prototyping, and testing is a time-consuming job, and there are very few "fun" things about it (when compared to, say, coding on a problem you think is really interesting).
Corollary 1: Due to the nature of the work, most UI designers tend to want to get paid for it. ...and therefore, spend most of their time in commercial shops, where they don't have much contact with OSS developers, even if OSS developers wanted their contributions in the first place (which, as a browse of any Linux-PVR thread will reveal, they don't :)
Corollary 2:
> But... is it possible for Interface design profit to sustain code design in the long run? Once open source interfaces catch up, will this niche remain?
Bottom line: You cannot assume that open source interfaces will ever "catch up" with their commercial equivalents, because the gap between UI designer and "open source coder" is cultural, not merely technical.
OSS is a magnet for developers. The community holds no similar attraction for UI designers.
Re:How... (Score:2)
wow, you mis-read that article bad.
Free engineering from a large community. Thats what the buisnesspeople want out of open source
It's the same guy that made Snort to begin with, and he's still contributing/leading the development of the software.
And the profit comes from making the interface.
Umm well, where to begin, lets start right over here [sourcefire.com] where we see it's not just a front end, but hardware to run the application as well. Oh and look, they have other things that don't use snort, or other OSS proj
Re:How... (Score:1)
Re:How... (Score:1)
This is a very valuable service- to articulate to Mr Customer why an OSS program on a piece of comodity hardware is worth thousands of dollars... More power to them. We're going to see a whole lot more companies just like them
Marty has it coming (Score:2)
They work pretty hard on Snort. It works really well. I can make it work really, really well for my net. Thanks! It sounds like you resent that they incorporate users' patches and such. That's the point of Open Source. If you don't like it, fork it. It's cool that they can make this great tool available to us, do some value-added work and profit. They aren't shipping Snort as cripple ware, a teaser, or
R & D vs. Maintenance and Support (Score:5, Insightful)
Some here mention RH "making money off OSS" - they are because others are debugging and developing for them (they do have their own contributors, true) but for less popular OSS apps if you have to develop and debug by yourself and you collect maintenance and support money only, how do you do research and development within the same budget? You can't innovate significantly on a shitty budget - you can only GPL-code what has been done by someone else.
Those who charge for maintenance and support alone can't by definition be much more cost-efficient from closed source competitors who do the same (perhaps the OSS guys wouldn't spend on ads and lawyers, but apart from that, I just don't see why would OSS be more cost effective - at least not to the 99% of corporate customers that aren't interested in the code itself).
And RH-like companies' ability to make money off OSS is proportional to the lock-in effect they can create with their distribution or application. If transparency and portability between different versions of Linux becomes 100%, then price becomes the only remaining differentiation which pushes the distros in deadly price competition.
Just imagine how easy it would be to ask RH for a discount if you could migrate your Oracle on RH to Oracle on Debian in an hour, or move from one OSS firewall to another by simply loading the exported settings into another tool...
It's the services - stupid (Score:2)
"Lock-in" is exactly what customers should seek to avoid. Customers will continue to use your services if you prove to be skilled and conscientious at using the software in question. Our own experience is that we are more attractive to customers by the very fact that they feel they can up anchor and shift to alternative support / suppliers if necessary.
So where'
Same Points, Opposite Views (Score:3, Insightful)
Nope, OSS will be cheaper. There are various reasons for this.
First off, retail price being the same, OSS is cheaper. If you want new features, bugfixes, or other changes, you can do it yourself or go with the lowest bidder. With proprietary software, you would have to pay whatever the copyright holder charges you.
Secondly, OSS is prone to fewer risks than propr
More examples (Score:2)
Open Source Business (Score:2, Interesting)
Source "fire" (Score:2)
SourceFire = okay, not great (Score:5, Interesting)
Even though the under-the-hood technology is k3wl and using Snort sigs is l33t, the admin and management tools are frankly not up to par compared to other offerings out there. I mean, it's not as bad as ManHunt, but it still takes waaay too many mouse clicks and unnecessary repetition by a human to get simple admin tasks done. I've seen gigs of sensor data lost to DB corruption (thankfully nothing critical) and have gone through the whole oh-crap we'll-get-that-critical-bug-fixed-next-release trip with them more than once. Support is a mixed bag, sometimes excellent, sometimes okay, sometimes really slow and annoying.
Bottom line is, companies are companies, there's nothing magical about open-source ones that make their products inherently better or more desirable for any other reason than to boost one's ego and to say that You Were There Back When. If I were recommending an IDS product line to a customer (which I probably wouldn't do anyway), I would encourage them to do some careful research before settling on SF.
Re:SourceFire = okay, not great (Score:2)
You are bashing them because they are just like any other company. I find that odd. Let me put it this way.
I am sure you use many products by many companies in your workplace. Of all those companies how many sent their CEO to meet you?
Michael Tiemann has it right... (Score:3, Interesting)
Go watch it and if you're curious, read on. If not...that's good too as I'm only going to ramble a bit;
What I take from it is that the developer should reject the impulse to build everything from scratch and build just the core tool kit for others to use. After all, you can't know what other people are thinking or what they want...even if they tell you.
Along those lines, I look for projects like Plone that build on the work that preceeded it (Python to Zope to Plone) and make it easy to design extentions (Plone Products) that interoperate with the lower levels. I avoid monolythic projects that don't seem to be flexable enough to incorporate other toolkits. This is not pre-made integration, though. Quite the opposite.
Having the lower levels available and modifiable (Python source of Zope and Plone) means that you're not locked into one and only one way of doing things if you need to make changes. The vendor or core developer(s) don't dictate what you do or how you do it. Yet, along the chain each part works well with the levels above and below it.
Additional link; Erik Von Hippel. [harvard.edu]
Re:Michael Tiemann has it right... (Score:2)
Redhat used to be the hands-down champ. 7.3 is still a solid product for older machines, honestly. But the transition to Fedoa, in my eyes(while smart theoretically) has hurt them a lot. With Fedora for a long while I got the slow bloated feeling. Too many options for initial install, too much overlap, etc.
I think as Fedora finally becomes fully democratic(as it has always been planned, but slow to actually come about) these issues will
I thought Darl already figured it out... (Score:2)
Small Companies... (Score:1)
If only my small company was making well under $50 million...
OSS not that different from other businesses (Score:3, Insightful)
Re:OSS not that different from other businesses (Score:2)
You don't pay the guy because you can't figure it out, you pay him so you don't get dirty.
Profit from open source is evident from statistics (Score:1)
Would it be ethical for someonelse to do that 2? (Score:1)
I am pleased for Mr. Roesch. But what if someone else sees this article and thinks, "Hey, I can do this too." Goes and starts up a company that also sells Snort and a different GUI. Would that be ethical.
Disclaimer: I am not said person. I don't do development; I don't even program. That's right, I am not ev
but how do i make money? (Score:1)
I've been looking for a way to start an open source project that can pay my rent for years. Still haven't found a way short of witting something everyone needs that doesn't yet exist and then sell it with the source being open. I'd love to rewrite the gimp's ui code to make it usable, if I knew I was going to be able to at least pay for a sixer of beer because of it.
How does a poor starving geek turn his oss hobby into a rent paying busine
Re:As a grate man once said... (Score:2)
Re:As a grate man once said... (Score:3, Funny)
Re:As a grate man once said... (Score:3, Funny)
um, ever hear of source code?
If someone writes a compiler that changes behaviour based on colours or fonts, I will personally bury my foot deep/in/their/ass.
ColorForth (Score:1)
A dialect of Forth that uses color to replace punctuation:
http://www.colorforth.com/ [colorforth.com]
Re:As a grate man once said... (Score:1)
> 1. Open Orifice.org (hello? Ha it even reached 1.0 yet?)
Eh, It's OpenOffice.org (OpenOrifice, incidentally, is what's used to root your weak Windows security -- don't look at me that way, you mentioned it, bub. Oh, and "great" is spelled G-R-E-A-T, by the way. See, you used "grate" as in "to grate on one's sensibilities" -- I know, your Microsoft Word spell-checker didn't catch it, so
Re:As a grate man once said... (Score:1)
This is what I love about the 'net. Endless entertainment. I'm really sad I can't respond to all of your brilliant points, lacking the time to do so, but some of these are too golden to pass on:
> "If u want a battle of witz, then uve picked the wrong guy pal."
No, you see, if I wanted a battle of wits, I'd pick on someone who actually had some to spare.
> "FACT 2: Great or grate both mean the same exact thing."
[*sigh*] OK, let me help you: http://w [m-w.com]
Re:"Proprietary" (Score:4, Insightful)
Re:"Proprietary" (Score:3, Insightful)
Truth be told, services and support cannot always pay for the bills, especially when you're a small company with a relatively small number of customers. Sadly, people like Stallman would rather get caught up in the political melodrama of the idea that "commercial software is
Re:"Proprietary" (Score:1, Informative)
Sadly, people such as yourself are dishonest scumbags.
Stallman and the FSF don't have anything against commercial software. In fact, you can buy software from the FSF [fsf.org] if you wish (though I suspect that you're the one that doesn't want to pay for software).
In case you're actually not a dishonest scumbag but simply ignorant, here are some clues for you:
Free
Re:"Proprietary" (Score:2)
Re:"Proprietary" (Score:2, Insightful)
Re:"Proprietary" (Score:3, Interesting)
That depends on if you're a realist, or a moony pie-in-the-sky idealist. The fact is that having the open stuff wrapped in a proprietary interface is good for everyone. The company is motivated to fix bugs, the software gains more acceptance, and the community is motivated to make a new interface. Everyone wins.
Re:"Proprietary" (Score:2)
If you don't like it, don't use GPL code. Contact the author(s) and pay them for a different license, the author can do this but you may not. Being the inovator has its perks after all. But don't link to GPL code in your closed-soruce project. You are viloating the letter an
Re:"Proprietary" (Score:1)
Re:Breaking news (Score:3, Funny)
Re:an emerging trend (Score:2, Insightful)
If you can't make a living as a programmer, you'll have several types of programmers:
1. Those that do it because they love it and can afford to not get paid. (the best case)
2. Those who do it when they can but still love it. They just have to fit it in with another job to make a living. (You wanted that patch fast?)
3. Those who wouldn't make money at it anyway.
The vast majority with be #2s. Basically, you'll have someone who ha