I find your outlined pricing to be unreasonably reasonable. Are you sure your math is right?
With regards to the other stuff...
-I don't know much about drive types. My db size is generally small enough (< 1 GB) to not matter. Except...
-Unless I'm storing images. I never moved from SuperContainer to External Containers. I don't think they can be on a separate drive right? But SC file storage can also be on the cheaper drives, though. Foxtail charges $1 per GB (per month) for SC storage which I find very reasonable. I Could you explain how bandwidth costs you? Or is it just another profit avenue (no judgement here)? I've gotten burned a couple times when uploading or downloading a set of stored files or some other unusual bandwidth activity (not with you) and I just don't understand why a 10 GB transfer costs $20.
-Not much of an opnion on Session Fees. It's not my model. I have a mix of "always on" and CWP and each CWP request would be a session, right? How would FM Go fmreauthenticate re-connects work in a session model?
-I don't see a per hour "open file" model being worthwhile. Do people close their files? I never do, intentionally.
I really like that you're exploring options. It seems a good role for a hosting company, to find the middle ground between FMI and actual users. Good luck.
The prices above are for 'client access'. Our current plans is to charge separately for 'hosting services', so drive space/ number of files/ etc would all be metered. We aggree that bandwidth is a bad way to meter FileMaker. Our experaince is that most solutions are not bandwidth heavy- it's the initial loads and the backups. Since backups are typically late at night the bandwidth honestly that expensive at the datacenter level.
Session fees seem to be a reasonable way for us to address 'quick-use' and/or sync solutions. If a user syncs twice a day and it takes 30 seconds, then there is no money in hositng. If we 'ditch' session fees, then we would have to raise hourly rates and/or we are considering 'tiered plans' so that low-volume users pay more than those who are logged on all day, everyday; however, that added complexity to the billing system and you couldn't detemine what a session costs until the end of the month- we like users being able to have a 'running total'- this concept is not so different to Amazon Cloud Services or Azure.
Opening/ Closing Files
The reason we are looking at open file pricing is that our portal would allow you to schedule your database access, so if your database supports a 9 to 5 business and is never needed after hours, then it could be scheduled to be 'shut down'. We have also found that developers like to have several versions of the file hosted at the same time- often with only one file being open at a time. If makes sense that the 'old version' that's not being used cost less than the 'real' file.
I'm not permitted to quote FBA pricing here, but we'll say that WebDirect is less than $50 per user per year. If we double that number for 'hardware resources' then that's only $100/user/year as rough cost. If we figure 20% profit margin, and a 60% utilization of licensing; then these numbers seems plausible and we feel very reasonable. We are not factoring in vmWare or Microsoft licensing costs, as those costs are already factored into the 'server hosting' and should be repeated in a 'client service'. Heavy users will end up paying more as they will likely use more hard drive space and other services.
Our goal is not to 'get rich' from any client, but instead provide good, solid hosting for a fair price. Like everyone on this site, we are trying to figure 'real costs' of this new pricing and trying to see if we can come up with pricing that makes sense. Many people are very upset with FileMaker, Inc. right now; but as factor out these numbers it appears that this prcing seems to be 'workable' and dare I say 'reasonable'.
With all the hate going around, we wanted to get other opinions.