Show HN: Durable Actors – OSS Durable Objects with configurable compute
openA Durable Object/Actor is a tiny server that handles one request at a time and has its own SQLite database. There's exactly one of each in the world and it is addressed by name.
This is the perfect primitive for deploying multiplayer agents. Each agent can have its own Durable Actor, and each user can connect to that Actor via websocket. This is fully horizontally scalable. Your users can deploy and share agents at will without putting pressure on a central DB or websocket server.
Durable Actors are also great for coordinating agents within a system. Since only one request is handled at a time, you can protect critical data such as a CRM and allow multiple agents to run concurrently without worrying about data races.
The only alternative to this is Cloudflare's Durable Objects. However, there is extreme lock in (they pull you into D1, R2 + workers as well) and it wasn't originally built for agentic workfloads when it was released 5 years ago.
Some notable projects built on Durable Objects include RampInspect, OpenInspect as well as the multiplayer frameworks Liveblocks and PartyKit. You can now build these kinds of projects on Durable Actors.
Durable Actors is a version of DO that is built for concurrent agentic workloads. It is fully open source (MIT License) and includes a helm chart for you to easily self-host.
Some key features:
- Configurable compute: Specify CPU, RAM, data residency, idle-timeouts all in a decorator
- No outer worker: We generate a type-safe client that you can just plug into your existing tech stack.
- (coming soon, like today) Export SQLite table via CLI + MCP for exposing OLTP logs to your agent to help you debug.
And our Performance Numbers (all p95):
- Durable write: 85.6ms
- Stateful Read (data in sqlite): 2.14ms
- Actor Warm up: 334ms
Here is a little counter demo so you can see the latency yourself: https://demo.useterse.ai/
Would love your feedback!
25 comments
Perhaps emitting versioned domain events transactionally with the actor state is an option without prescribing an exact solution.
Since we are so early, we can build this the right way. I agree, I think we need something you can set up to sync to a data lake. I started really simple with exporting at certain times, but I think there is more to do here.
I really want to nail this part of the experience. I agree, it is a big sticking point
https://celld.dev/
https://tlockney.github.io/celld-book/
https://noite.now/ https://github.com/kentcdodds/kody-celld
https://celld-operator.io/ https://ewhauser.github.io/celld-operator/
Here are some of our differentiators:
- built with running in sandboxes to give users more flexible CPU and memory settings per DO
- declarative SDKs in Typescript/Python
- generated type-safe clients (no outer worker needed)
- built in debugging UI
- durability guarantee is using GCS rapid or other cloud technology for fast writes without having to manage a fleet
Happy to go more in detail as well!
Can't Durable Entities meet the same use cases?
EDIT: Of course I am not talking about the difference in OSS vs not. Rather I'm interested in the difference in use cases and capabilities. Some of the aforementioned have ways to run things locally as well, though they are designed as distributed cloud-based PaaS services.
each actor has its own sqlite DB and runs on one host at a time. Clients call it via RPC or Websocket message, changing state and actor pushes state changes back to every client. product is more similar to cf durable objects or orleans.
i took a look at durable entities, state model is similar but they don't support websocket handling.
thanks for the question verst. durable actors manages durable state, not durable execution. Azure Durable functions, temporal, aws lamda durable functions are for managing execution. each actor has its own sqlite DB and runs on one host at a time. Clients call it via RPC or Websocket message, changing state and actor pushes state changes back to every client. product is more similar to cf durable objects or orleans.
i took a look at durable entities, state model is similar but they don't support websocket handling.
Cloudflare's equivalent for that is instead called "workflows" [1] for those resumable/retryable multi-step functions for durable execution.
(naming is kinda confusing, I had to build out a redundancy system across all these providers)
1: https://www.cloudflare.com/products/workflows/
Also are you able to self-host this outside of GCP (from the docs it seems like it is locked to GCP but I'm not that familiar with it so maybe not)?
Our biggest differentiator is the configurable compute. With our helm chart, you just add a decorator and can specify how much RAM, CPU etc... an actor class has.
We are pretty opinionated on how to host these. The helm chart gets you a fully horizontally scalable deployment.
Want to make this the best product possible
I mean we have https://github.com/denoland/celld - with a known good open source history. Durable writes there are as low as 1ms.
Celld is pretty cool in that you can configure a small fleet in the same VPS and get super fast durable writes (with a weaker guarantee). We are also going to allow you to tweak the durability guarantees so you can manage that trade off yourself!
Nope. you just run it on 2 VMs in same zone and get 1ms (ack on durable disk write).
I'm surprised at your technical language. Either you're ignorant of basics of how other key durable systems works, or you're misrepresenting a unnecessary worse case. Neither inspires confidence in your work.
Do you have a reproducible set up I can try out to see this latency? We would love to offer an option to have 1ms writes
We are actually a different API. I come from writing swift for 7 years (I was at apple) and really thought they nailed the actor model so modeled ours similarly.
Also, we make it really easy to configure each actors compute with just a decorator. So if you want to do something beefy like store file directory in an actor you can increase the memory to 4GB and you are good to go!
Happy to go into more detail here as well!
Which actor models are you comparing to? What do you think of Erlang/Pekko/Pony?
I roughly understand their models but have never looked at Swift's. On the surface it looks like it borrows heavily from each of these (now that I'm looking) which sounds potentially awesome. I suppose I'm curious what you think makes Swift's model 'nailed' relative to alternatives.
It's pure curiosity. I love actor models and enjoy learning about the paradigm in general.
I love the idea of tossing a decorator and modifying the durability guarantees.
Also, swift @sendable is really sweet, also want to add that in and flag when state data is about to leave the actor.
Actors really were a life saver at Apple. Agents are like what threads were to us on iOS