Posted on 02-26-2013
The BaaS space is heating up with lots of discussion about whether you should charge developers by active user, features, storage or API call--with each provider being pretty vocal about where they stand. Quickblox is approach similar to StackMob, who refuses to charge based upon API call, atributing it to a sucess tax. But Quickblox is somewhat different, as they still charge for hard costs like bandwidth and storage--Stackmob only charges by feature.
I'm trying to understand all the approaches to BaaS pricing, which was also a panel discussion last week at API Strategy & Practice between Parse, Stackmob, Kinvey, Kii, Cloudmine and Firebase. I don't think there is a one size fits all strategy here, but I predict the conversation around BaaS pricing will continue to heat up in 2013 as the market continues to define itself.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Is Your API More Than Just A Footnote On Your Website?
- There Are Four API Design Editors To Choose From Now
- Sales, Onboarding And Support In A Self-Service API World
- An API For Developers To Access Their API Account Information
- My Continued Support As Signer Of Oracle v Google Amicus Brief From EFF
- Join Me Tomorrow For A Panel Discussion On API Ecosystems At SF MusicTech
- I Will Review Your API On API Evangelist if You Add An APIs.json File Plus A Machine Readable API Definition
- Hey, Why Isn't This (API) Free
- Resource Base API Monetization vs. Experience Based API Monetization
- Tracking On The Red Flags For API Monetization