When we reach for it
Spiky, event-driven and scheduled work: webhooks, image processing, the nightly job. Where load is irregular, paying nothing between events is the honest architecture.
Serverless functions
Compute that exists only while it is handling a request, billed by use and scaled by the platform rather than by anyone on your team.
When we would argue against it
A steady, predictable workload is usually cheaper and simpler on a container that stays up. Cold starts, execution limits and local development friction are real, and a distributed system made of a hundred functions is harder to reason about than a service.
What it looks like in delivery
Used for the edges of a system rather than its middle, with the same observability as everything else — a function without tracing is a part of the architecture nobody can see.
Where this appears on the site
Nothing on this site names it yet
We work in Serverless functions, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Also in cloud and infrastructure
Working in Serverless functions?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.