While the rest of this conversations seems to be off in the weeds... I'd like to bring this back a bit:

I've been thinking, and another method that could generate some revenue, while still maintaining a low-cost tier as I've set out below, would be to incorporate a VFS plug-in layer that you can, as a for-profit company, use to introduce functionality that is not available in the Open Source variant. This would also allow others in the open-source community to produce open-source plug ins for the VFS (such as zsync intengration and such) which would be yet another feature boon for OF over all the other simple free NAS implemenations.

For-pay items that I expect would be immediately needed include modules such as an Encrypted File System module (very important to us in the legal industry), Replication, Thin-Provisioning, Comprehensive Reporting, etc.

These modules are something that most common users wouldnt' need, but most enterprises find critical, and hence, would easily segment the revenue stream towards those with the ability to pay.

As an aside, the per-hour charge of $99/hr mentioned in my message below actually unrealistic. I was being a bit to idealistic the other day :)

Either per-incident of ~$299 or per hr of ~$149 is more appropriate. I would choose one or the other but per-incident tends to have more traction in the software service industry. You could also have a premium support tier that commands $899/yr for all incidences for the year as well as pro-active notification of updates as well as problems (auto-emailed to the OF team so you guys can contact the client to address the issue. Perhaps include a client-server module that checks for each OF to check-in and if it hasn't within 36hrs, auto-generate an email inquiry to the account contact. If you guys do a good enough job of building the product to be self-sustaining, could be very lucrative ;)

If I wasn't clear before, there should be no "purchase" cost of OF at all and the OF team should rely solely on the services for revenue generation including the items I mentioned in my first message below (OF-sponsered user lists, forums, support, auto-update channel, etc.) as well as any proprietary "modules" from the above suggestion if they ever come to fruition.

Once OF2 goes stable, it will be replacing my current simple windows based storage server that has a portion of it (yes, a movie share where all media from my MediaPortal system is stored) replicated to 4 other sites over broadband in ring fashion (for disaster recovery). With a zsync VFS module, we could lower our replication times considerably. Damn that would be hot :)


-=dave

----- Original Message ----- From: "Dave Johnson" <[EMAIL PROTECTED]> To: "Les Mikesell" <[EMAIL PROTECTED]>; "Rafiu Fakunle" <[EMAIL PROTECTED]> Cc: <[email protected]>; "NADAI MAURIZIO" <[EMAIL PROTECTED]>
Sent: Monday, May 29, 2006 5:45 PM
Subject: Re: [OF-users] Re: What would you pay for Openfiler?


Actually, if the added functionality of a command line interface were added,
and a few other things fixed up (like the ability to publish a snapshot as
read-only at least) then I feel $299 is probably more appropriate unless the
ticketed email support is staffed by just one guy who gets back to you 3
days later.  When you get into $1000/yr, then you better have straight-up
"support"-support ;)

-=dave


From: Dave Johnson <[EMAIL PROTECTED]>
Date: Mon, 29 May 2006 16:57:47 -0700
To: Les Mikesell <[EMAIL PROTECTED]>, Rafiu Fakunle
<[EMAIL PROTECTED]>
Cc: <[email protected]>, NADAI MAURIZIO
<[EMAIL PROTECTED]>
Conversation: [OF-users] Re: What would you pay for Openfiler?
Subject: Re: [OF-users] Re: What would you pay for Openfiler?

I don't see how you can expect automatic free updates since these require
the bandwidth of the repository.

I think the following would be reasonable:

FREE:
-Any documentation that has been written should be free (this is a
no-brainer unless you want to kill the project. It's already tough enough as it is not having any documentation for OF2, hence most of the seemingly
"simple" questions on the "user" exploder.)
-Anon access to S.F. CVS repository.
-RPMs for all updates that are available to subscribers via auto-update
published on S.F. For download and manual install.
-3rd-party mailing list or user forums (this would be accomplished by the OF team campaigning for someone to begin a mailing list with a 3rd party such as yahoo groups, or some free forum provider, etc. and the OF team links to the site from the main OF home page for "user-supported help forum"... You
get my drift.

PAID ($10/yr) personal:
-Same services as FREE plus the following:
-Access to OF-provided auto-update repository.
-Access to project-sponsored "developer" mailing list or forum which allows access directly with project team (much like the "developer" mailing list is
now.)
-Access to project-sponsored "user" list or forum which allows access
directly with project team (much like this "user" mailing list is now.

PAID ($199/yr) corporate:
-Same services as "personal" plus the following:
-Direct ticketed-support via email with OF team.
-Emergency phone support at per-incident (billed after incident is
resolved!) rate of $99/hr or less (at OF tech discretion) with cap of $700
unless agreed to more by corporate subscriber.


I think that about covers it. Problem I see is that the corporate level of
support isn't ready yet because the corporate-level product isn't quite
ready yet but it's quickly getting there. Things missing before corporate
adoption is really feasible:
-Commandline interface (snapshot control, automated snapshot scheduling,
automated published shares creation/modification/deletion, and rudimentary
reporting.  This is really the mimimum level of functionality required in
the corporate world.  We just bought an ONStor Bobcat 2240 to manage our
storage but we could have easily used OF if it supported the above
commandline functionality.
-The resources within the "corporate" subscription tier outlined above.
-About 6 months of proven usage within the "free" and "personal"
subscription sectors above.

Hope this helps!

-=dave


From: Les Mikesell <[EMAIL PROTECTED]>
Date: Mon, 29 May 2006 11:51:24 -0500
To: Rafiu Fakunle <[EMAIL PROTECTED]>
Cc: <[email protected]>, NADAI MAURIZIO
<[EMAIL PROTECTED]>
Subject: Re: [OF-users] Re: What would you pay for Openfiler?

On Mon, 2006-05-29 at 06:13, Rafiu Fakunle wrote:
1) Automated updates
2) Documentation
3) Training
4) Developer forum access
etc

I probably wouldn't install it in production if automatic
updates aren't free along with access to the srpms of
the base install and updates.  Different levels of
optional paid support would be fine though, including
an email level. It's hard to put a blanket price on
something that might be competing with a $200 (including
hardware) consumer level network disk or a $100,000
NetApp or EMC array.

By the way, do you have a list of the functional differences
from the base Centos version?  That is, besides the install
and the web interface, what does openfiler change?

--
  Les Mikesell
   [EMAIL PROTECTED]


_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users


_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users


_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users

_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users

Reply via email to