5 ms·

Thanks for this feedback. Couple of points of clarification. The infrastructure interpretation happens at build/deploy time, not at execution time, so there isn

Thanks for this feedback. Couple of points of clarification. The infrastructure interpretation happens at build/deploy time, not at execution time, so there isn't any additional tax. The deployment engine isn't open source, but we are evaluating ways to have optional eject paths. In terms of deployment across cloud providers, the abstractions we've built (and are working on) use all those fancy AWS managed services like DynamoDB. Our abstractions focus on use cases, not primitives, so when we eventually deploy to Azure, we'll be able to replicate the service using native services like Cosmos DB.

tedmiston 5y ago
> The infrastructure interpretation happens at build/deploy time, not at execution time, so there isn't any additional tax. The service has a pricing page [1] that's non-free after the preview period with specific tiered included limits around execution minutes etc. For example, "$20/user/month for 5,000 minutes of execution time" and some amount of storage. Is there something I'm missing about that pricing model? What about metered pricing beyond the limits listed? I didn't see that addressed in the FAQ, but perhaps I overlooked it. [1]: https://www.serverless.com/cloud-faq https://www.serverless.com/cloud-faq
- jeremy_daly 5y ago
  Looks like the mobile version of the pricing page hides the rest of the table (sorry about that). Extra execution time will be $0.003/minute and billed by the millisecond. There are no request charges or data transfer charges in our model, which we hope will simplify billing for the average users. For users that need more capacity and execution time, we will customize pricing for them.