![]() ![]() My service is going to have a REST API component that clients will use to manage their sites. Here’s where we get into the first strategic decision. Just pick the one that you’re the most comfortable with and has the features that best fit your needs.Īnyway, my pick is AWS. They’re all racing to the bottom with their pricing. This is one of those situations where I need to lean on my past experience and move fast so even if those hosts offer some discounts up front, the learning curve isn’t worth it to me.īottom line, there’s not any significant across-the-board pricing advantage between the major clouds. I’ve used Azure and Google in the past and they would do fine too with the features I’m looking for. I’m going with AWS because I’m really familiar with their stack. They’re all fighting for eachother’s business and they’ll give you secret discounts so it’s pretty tough to choose. There’s really only three options that are worth considering: AWS, Microsoft Azure, and Google Cloud. Here’s how I’m going to design this system so it works for me: What Cloud to use? The dynamics of this business are pretty simple: The lower I can keep our cloud hosting bill per 100 users, the quicker this becomes a self-sustaining enterprise. Still a lot of users but it might be more doable. But what if hosting costs are only $0.05 per 100 users? Seems aggressive but it means I could get to sustainability around 200k users.That seems like a lot of users to support without any full-time employees. If cloud hosting costs are $2.50 per 100 users, I’ll need to get to 500k users before I could even support a full-time employee.That means $5/mo has to pay for 100 users worth of cloud hosting costs and be profitable. I’m assuming that we’re going to have 99% free users and 1% pro users (pretty standard SaaS conversion metrics). My model is freemium with Pro plans at $5/mo & $60/year. Seeing as Wunderbucket is cloud hosting, this could get expensive quick. I can’t fund an expensive hosting bill for a hobby. ![]() As the system scales, it needs to pay for itself. My system should just scale to meet demand. If my idea connects and people start registering, I don’t want to hit bottlenecks. Scales up automatically to meet demand.If my idea sucks or it takes me longer to find users then I think, I don’t want to be paying for resources that I’m not using. I really want to build an app that’s sustainable. It’s simple static web hosting for designer / developers who can only write HTML & CSS. So I’ve got this idea called Wünderbucket. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |