Hi, this is Dylan, a co-founder. It's a great question. Having built many applications on Lambda this is something I think about a lot :) .

We've found that for integrations or common automations, building on a cloud platform is too low-level. Frequently you're working with more than just a Lambda. You've got to manage a number of services that aren't core to your use case (e.g. API Gateway, IAM, Cloudwatch Logs, etc.). There's a lot of boilerplate config, and many of these services are tangential to the core logic of your app.

We operate at a higher level and just give you an execution environment to run Node.js code or stitch together pre-built actions, similar to integration platforms like Zapier. We manage the HTTP endpoint, function config, and give you built-in observability. We also provide higher-level services, like built-in app integrations and OAuth / API key-based authorization. Building this yourself on AWS can take time.

This kind of abstraction isn't great for every application, but we think it shines when you're building integrations between services.

I'd love if you had time to sign up and see how this works! It's free to use and we'd love the feedback.

Let me know if that answers your questions, or if you have any more!

Your comment has me imagine a more visual, GUI-based editor on top of AWS Lambda (i.e. hooking up all sorts or internal/external events, tying workflows or multiple Lambdas together, still including a small editor for writing JavaScript, etc.)

I mean, you can write code in-line with AWS Lambda but to have an application help setup multiple Lambdas and/or integrate outside APIs would be pretty neat.