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
- ReliefWeb Is Tackling The Worlds Biggest Problems Using APIs
- Turning Forms Into APIs: Crap In, Crap Out
- The Private Internal Tier Of My API Service Composition
- API Virtual Stack Composition Like The Absolut Drinks Data API
- An Operational Harness For My Screen Capture API
- Two Things I Learned On Traffic And Weather Today
- Keep Your API Developer Area Blog Up To Date
- Interesting Example of Social Page Over At Cisco
- External API Deployments Using Sync One Possible Future Of Government API Deployments
- What Are Some Good Examples of Hypermedia APIs?