[cramforce]

That's 1 part, yes!

Part 2 is that you can also use an actual server if your workloads happens to be predictable (or is partly predictable). That gives you better cost efficiency for that part of the workload

Displaimer: CTO of Vercel here

[rpicard]

Love it! When I first learned about serverless as a vibe years ago it didn’t click, but it’s so clear to me that abstracting compute fully is a huge win as long as you can safely assume things about the way your code will run.

It’s interesting to see so many companies coming at it from different angles. Fly, Vercel, Cloudflare, Northflank, Temporal? etc.

Pretty much all the code I need for my work can run in GitHub Actions, so I’m not so much the target, but still enjoy watching the development.

If you can answer, what’s the overall initiative here for Vercel? Own all the compute, as opposed to just the front end ish things?

[cramforce]

The initiative is really focused on our current workloads like APIs, SSR, etc.

It definitely makes Vercel suitable for a broader set of workloads, though!