jeremy_daly

> We actually need "Just Code" tooling.

Totally agree with this, and this is what we're doing with Serverless Cloud (which I work on). Developers (generally) want to write code, but having to implement the same boilerplate or cloud infrastructure configurations over and over, or wire together cloud primitives every time to build a solved use case, is both inefficient and prone to human error. Baking most of this into a platform, and then letting developers just write business logic is a powerful abstraction.

Hey tedmiston, I think you make incredibly good points, and as the GM of this product, I appreciate your candor and scrutiny. We don't expect Serverless Cloud to be a silver bullet, lots of team out there need more control and flexibility. But we hope that for many developers and teams, we can provide the right level of productivity, performance and cost to minimize their TCO and validate their ideas faster.

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.

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.

Looking forward to seeing what people will build with this. The team tried to address as many of the serverless development pain points as possible, with the goal of enabling an entirely new class of serverless developer. There's a lot more to do, so we're excited to hear your feedback!