|
|
|
|
|
by andr111
2623 days ago
|
|
Thanks for the interest! The questions you are asking are very valid. Let me address them one by one: 1. We are evaluating an open source strategy, but currently don't have plans to open source it. There are couple ways we're addressing this. First, in an event of a closure of the platform we commit to open sourcing it, just like Parse did. Second, which is a more immediate one, is that we will be adding features that make 8base fit well into developer workflows as a tool rather than a platform. That way developers don't have to commit to building on 8base right away and can use it as an integration layer that accelerates access to business data and workflows. By focusing on enterprise use cases we believe we can achieve a good value proposition without forcing people to build entire application on 8base. Also, as serverless architecture becomes more pervasive porting business logic comprised of cloud functions should become easier than before (this is a somewhat weaker point). 2. We're still working on the pricing and gathering feedback. If you don't mind, could you share which aspects of pricing concern you specifically? Indeed a SaaS, especially one in the enterprise space, is definitely our target. As a matter of fact, we already have an enterprise SaaS built on 8base that's launching in a few months. |
|
As far as pricing if I'm comparing against, say, Firebase your pricing seems higher for less infrastructure but I understand that Firebase wouldn't be an apples-to-apples comparison given your enterprise-data-integrations value-adds.
I guess it's just hard to swallow the idea of building an entire app with your platform then potential having high cost of scaling- but again, I understand why some may not see it that way and be happy with that pricing.
If you had lower monthly base plans and then pay-as-you-go for each functionality like the serverless functions, no. of end-users, etc. then it'd seem more attractive.
Anyway I'm sure your guys have put a lot of thought into the pricing so this is just from a web dev's perspective!