What highly optimized durable execution looks like
Durability stops being a premium feature and starts being a default because it's so cheap there's no reason not to.
We switched from writing components directly, to doubling down on protocols and specifications.
A formal spec for the distributed async/await protocol. Language-agnostic. Transport-agnostic. Storage-agnostic.
A conformance test suite. Transition tests. Fuzz iterations.
And then we started generating the components.
Not just the SDK. Not just the workers. The server too.
When you need a Resonate server targeting Postgres + HTTP, we generate a server that is Postgres + HTTP. Not a general-purpose binary that happens to support Postgres as one of twelve backends. Every line of code exists because your stack needs it. Nothing else ships.
What does that eliminate?
Generated components don't carry abstraction layers that exist purely for flexibility:
Fewer state transitions: The promise abstraction alone reduces this to a minimum.
Fewer network calls: The protocol chatter is incredibly optimized.
No unused code: Small package sizes mean the components are easy to host, easy to install, and require little resources to run.
And… everything can be serverless.
A generated Resonate server is small and single-purpose enough to run as a serverless function. A Lambda. A Cloudflare Worker. A Supabase Edge Function.
It spins up. It processes work. It spins down.
Your agent workers — built on the Resonate SDK — do the same.
Both the server and the workers run only when there's work to do.
This is great for Agents, because they don't run 24/7. They activate, do work, and go idle. The traditional durable execution model — always-on server clusters, persistence layers, worker processes polling around the clock — means you're paying a fixed infrastructure cost regardless of how much actual work is happening.
With Resonate on serverless, idling costs nothing. And when work does arrive, each invocation does dramatically less overhead per operation because there's no abstraction tax. On pay-per-millisecond infrastructure, less overhead per invocation is directly less money.
Back of the napkin math:
Scale | Resonate. | Leading platforms |
1K executions/day | ~$0/month | ~$25/month |
1M executions/day | $170/month. | $500+/month |
Bursty workloads at extreme scale | <$100/year | ~$80,000/year |
The pattern that agentic workloads produce is intense bursts of orchestration separated by idle periods. The gap between always-on infrastructure and pay-per-use becomes enormous. Combine that with Resonate's reduced overhead per operation and you can get up to ~800x cost differences.
But it can run pretty much anywhere.
Because the protocol is transport and storage agnostic, we can generate components for whatever you're already running. No need to migrate to a whole new platform.
You're running agents on Supabase? We can generate components that run entirely as Edge Functions — durable agent orchestration with zero always-on infrastructure.
You're a larger team with everything on Kafka? We can generate Resonate components that use Kafka for message passing — durable execution on your existing infrastructure.
You need gRPC transport with DynamoDB for state? That's a generation target, not a feature request.
Durable execution has always been the right answer for complex agent orchestration. Multi-step workflows, human-in-the-loop approvals, long-running research tasks, multi-agent coordination — all of this needs crash recovery, checkpointing, and reliable retries.
But the cost of and complexity of the existing durable execution platforms has opened up as many new pains and they solved.
You don't want to have to learn a set of proprietary primitives and spin up $500+/month infrastructure just so your agents can recover from crashes.
When you bring that cost down by 100-800x, durability stops being a premium feature and starts being a default. Every agent workflow gets checkpointing. Every multi-step orchestration gets crash recovery. Every long-running task gets reliable retries. Not because you budgeted for it — because it's so cheap there's no reason not to.
If that sounds interesting — come tell us about your stack in the Resonate Discord.