Posted by hadsie on September 22, 2010 at 8:40pm
I'm working with sfyn to integrate the hosting system with ubercart. More background details here:
Something that will be useful to developing the module in a generic way will be to understand other use cases besides our own. If you're planning on selling sites through Aegir in some form we'd love to know how. Just basically what you plan on charging for (i.e. single sites, bandwidth, disk space, whatever), and how you envision the workflow happening (i.e. do users get a two week free trial when they sign up for a site or pay prior to site creation, or whatever).
Thanks!
Comments
OK, I'll start. Our plan is
OK, I'll start.
Our plan is to sell packages - one, three and five site packages with varying bandwidth and diskspace quotas.
We would like people to pick a package, enter the info to create their first site, pay and have immediate access to the aegir site.
Thanks for soliciting input...
My use case is:
Hope this helps,
I couldn't have said it
I couldn't have said it better. My use-case scenario would be to provide several website 'packages' (different features and quotas), where the product is the site, not the client. I would only add the feature request already mentioned in http://drupal.org/node/920790 , which would make it (aegir) a true product launching platform.
Pop quiz - whats a narrow
Pop quiz - whats a narrow vertical website application?
I assume its narrow as in the sites purpose is specific, but I am truly stumped by the word vertical.
Other than that, great specs, it is very helpful, thank you.
Definition of vertical in this context
See the wikipedia definition of vertical market.
Hosted Applications
My primary use-case would be akin to a SaaS or ASP business model. Basically, this comes down to "one-click" sites that, in it's simplest form (from a customer stand-point) bypasses Aegir all together.
I envision an order/provision workflow something like:
Things to note:
Systematic approach?
Perhaps a more systematic approach to this would be to address various objects in (and around) Aegir, and then see how they might fit together in various use cases. Since I'm not sure of even being aware of all of them, I think enumerating them is probably a good first step:
As I've noted here, I'd like to see client types implemented (e.g., admin, tech, billing, &c.), and ideally allow for the mapping of these to roles on specific platforms/profiles. But since this (and no doubt some other worthwhile feature requests) haven't yet been implemented yet, I think it best to keep a separate list, for the moment:
So, for my use-case described above, it would involve creating a site (3) on a specific platform (2) and profile (6.3), with an optional set of features (6.4) and themes (6.2), for a fixed number of users (A.c), and where the client is assigned a specific role on the new site (C), and a different role on the support site I run (so C again).
I don't know how useful any of this would be, but it appears (to me, at least) to provide a clearer framework for discussion.
Lets keep it open
I'm fine with this, but don't feel you have to construct your answer in these terms. I will learn more about your use cases from how you describe them than from how aegir would describe them. If I need to clarify something in these terms, I will ask.
My use case is about the
My use case is about the same. Im looking at it as my barbie doll profit model.
Barbie Has several lines, the top, mid, and low end as a way to prevent competitors to undercut just by pricing. This would be fulfilled by DIY sites that customers would be able to start up quickly, have a set number of themes, features, and thats about it. Support / Custom Themes / Custom Features would be services that I could then offer as an up-sell item to those customers. Kind of my foot in the door.
For my higher end customers, it would give them access to their backups, allow them to migrate their sites to the latest stable versions that I will setup for them, and run other sorts of statistic reports. Additionally for the DIYs they will be able to purchase access to premium themes on their site via the ubercart system, which would then transfer it to their site's folder, and the same for the Premium features.
Hopefully this is still open
Hopefully this is still open to discussion.
I'm looking at a similar business model to Wordpress.com (although for a different market than blogs). Where users can get a site for free, but then when they need to:
they'll have to pay.
Most important for me is that it must be simple for the end user, my target market is not computer literate.
The list above is just a general idea of stuff the user will be able to do, not all of it will come under the purview of Ægir. This is a use case in itself though: Ægir must play well with other modules.
Thanks for putting out this request, very good of you to solicit feedback, I just hope mine isn't too late! :)
Session a Montreal camp
http://www.drupalcampmontreal.com/sessions/drushmakebusiness-models-base...
Is there anyone to record it ?
Also interested about having some Ustream of following BOF session ?
Thank you
I will make sure to poast a
I will make sure to poast a link to the slides and the video as soon as it is available.
Agree of most use case above and lets give some flesh to it
Bypass aegir and have very targeted to client need interface.
I'm agree with Javier (blurp) that we best fit with vertical.
Either by industries (NGO, Corporate, professional body etc...)
Have as an offer low price / midle / high as cmcintosh says
It mean for instance a self service intranet having :
-Drupal Commons in different flavor (working on that)
-OpenAtrium
-but also wordpress and elgg
May be have training and advice how to make it works
And higher price point with custom dev and on onsite deployement
Offer the reinsurance that you can run on your own server as for Drupal Garden.
OK so there's quite a lot of
OK so there's quite a lot of meat here:
-Drupal Commons in different flavor (working on that)
-OpenAtrium
This is pretty damn close to functional.
-but also wordpress and elgg
This is on the wishlist for Aegir, but I am not even sure it is on the table for 1.0. Provisioning non-drupal platforms is definitely in the cards.
Best for last:
-Bypass aegir and have very targeted to client need interface.
Yes, I agree, and this is where I ultimately want to get to. I see no reason why we can't start seriously working on remote storefronts soon.
However, at some point, there will always be custom dev involved in this. My goal is to provide a very flexible system to implement this as well as good doc and a working example for customization.
For those interested this is
For those interested this is pretty much possible. I will write up a formal tutorial on how to setup storefronts a bit later today, for the mean time. What I have discovered is that you can for all purposes create new sites, run tasks, etc from a remote drupal site into aegir(or for that matter any platform). Using Services API. For those that are not familiar it lets you remote control a drupal site.
With this information we need to do a couple of things to make putting together new Front-Ends easy, yet flexible. First is we need to setup a method(more likely a UberCart attribute like file download). That when purchased will in turn setup monthly payments and maintain / update the sites per the client requests. We should also look into linking the front-end store into some sort of api for the backend to track disk quota(linux / php work) and bandwidth quota(apache mod).
The other thing that I am doing specifically is setting up a method to pass variables for the install profile into the new site node, then having drush insert them into the install process. This is again handy for things like, Twitter / Facebook /etc info. It is also handy if you want to do some sort of nasty Ubercart product limit services.
Syfn: When is a good time for you and me to go over this more. I feel like I have a majority of this stuff figured out already, and just need to organize my thoughts. hit me up via email.
We need also to see why it works or don't work.
Webenabled offer the same quid of service and I don't feel they are hugley sucessfull.
THere was serious reliability problem.
They may have give to much emphasis on free account at the begining.
Not being very responsive to market differently in other langage.
And targeting mostly webbuilder and reseller.
It meand that at least we have to count them in.
Having some referal fees.
Having the posibility of free trial period.
Being able to offer other free software alternative like wordpress/Budypress joomla virtual mart/ Elgg etc...
Right now I am working on
Right now I am working on building a module that allows passing information into the install profile script from aegir via the site signup form or site creation. This will be useful goint forward with a lot of these self service solutions. Ill update more when i have it rock solid
You asked, the Dude abides:
Building a Aegir-based business model that is targeted specifically to the high-end professionals in the Film and TV industries in the US, Australia, UK, New Zealand and Canada. The commerce side of the proof of concept is much in line to where your project is heading:
A) Using Aegir LAMP. Running the whole administration/sales from one master server, clients each on their own remote nodes in the cloud under our control. That will need to be added to the bill, but we will have very limited choices on what those servers are and how they are configured. Elastic? Only a little.
C) Using 3rd party CDN/Video encoding solution as optional feature. That will need to take into account as part of the larger billing scheme. So we will need to take their billing side and integrate it into our billing side. We will not resell these services, simply pass the fees over to the client as part of their monthly totals.
D) Not targeted to the regular public, and in some instances it may be completely private or semi-private. Sort of like a B2B, expect those B's are all people rather than companies. Visitor traffic will be low but bandwidth will be high as the video quality will have to be the absolute best. In every way the opposite of YouTube. We may only get 30 visits a month, but those visits will consume the same bandwidth as 3000 visitors in YouTube.
E) Limited clients. We will not have more than to 250 accounts at any time as we have already established that part of the business. We actually have set a firm limit on this. In this model QUALITY far surpasses QUANTITY. Stability a must. These clients will be very demanding, very capricious and with little patience for error.
F) Automation of the sign up process is NOT a priority, though desirable. Flexibility and tracking of billing IS the priority: Recurring billing, ability to add/deduct fees on the fly, track CDN usage, Video encoding usage, features, etc. We definitely like to implement a "Pay-when-on, Free-when-off, always there" scheme.
G) Building our own custom platforms with features that can be added and remove at will by the client. Example: The client can add/remove a CDN + Video encoding at any time and as often as they please. All the fees that come with that will need to be added and tracked. Obviously the question we are trying to figure out now is how to implement this part: If we set pay-for-what-you-use, the whole billing system becomes a veritable cornucopia of variable fees. Maybe we go for bulk instead. So there is that part.
H) The "core" use of the site will need to be highly secure, some areas will be more public. One of our custom features will need to be so secure that it may require the client's lawyers/IT approval before they use it. This, of course, will also need to be considered in billing, though in this case is just a flat fee.
I) The clients will be either single individuals OR companies with the ability to create their own accounts for employees/clients/reps. Individuals will have one set of packages and fees, companies will have a different set. All of them will have the exact same features available to then, but company packages will allow their owners to add/remove sub-accounts on the fly. Those "sub-accounts" are still undefined to us: Could/Should they be individual platforms WITHIN a remote server? Or maybe we simply go the content way and create a "company-specific" platform that handles using some good old fashion Drupal administrative controls? Working on that concept as well.
So there it is.
Peace.
openpublic
my use case is completely different from above
there is one customer who commissions the aegir site. the customer will "resell" to other public ngos for free . uc_hosting will be used to collect who and what these ngo's do