Launching @RivetKit_org v0.9, a complete re-architecture of ActorCore:
A lightweight actor library that integrates in 1 line of code & runs anywhere.
→ Any router (Hono/Elysia/tRPC)
→ Any platform (Rivet/CF/Redis)
→ Any client (JS/Bun/React/Rust)
→ 2.5 mo of work & 111 PR
For @RivetKit_org v0.9 (formerly ActorCore) we're doubling down on building a lightweight library that runs anywhere
The goal: bring Durable Objects benefits to any cloud provider. Just a library, no SaaS.
Here's how it runs on memory, Redis, Postgres, Rivet, and Cloudflare ⬇️
👉👈 Say hello to @Linear Coding Agent
Built with @ActorCore_org Agents × @Vercel AI SDK
I couldn't wait for this launch, so I hacked together a little something in an evening. I honestly don't believe I could've ship it this fast without Actors.
Source code below ⬇️
You can access a REPL for Durable Objects right now with @ActorCore_org and the Studio:
studio (dot) rivet (dot) gg
What debugging tools would you like to see for Durable Objects & Rivet Actors?
I'll do you one better: 📧 @Resend ⨯ @ActorCore_org (open-source Cloudflare Durable Objects & Agents)
This combo makes complicated email patterns dead simple. Examples include streaks, customer engagement, agentic workflows, and monitoring.
Streaks example code & documentation below ⬇️
Announcing: 🎨 Rivet Studio v1.0
A powerful development environment for @rivet_gg Actors & @CloudflareDev Durable Objects for realtime apps.
🧠 View/edit actor state
📞 Test RPCs like Postman
🔍 Explore live connections
🔥 Hot reload everything
→ studio (dot) rivet (dot) gg
🧪 Just dropped @ActorCore_org v0.7.6 with @vitest_dev integration for unit testing.
Easily test complicated stateful, realtime backends with just `setupTest(app)`.
Docs and changelog below 🧵
🎭 @ActorCore_org 0.7.5 is the first update shipped with purely external contributors
Now supports accessing platform-specific context (thanks @Zephraph) and fixes a series of docs/example fixes (thanks @ConnorAds)
Changelog below 🧵
📝 Ask and ye shall receive 5,041 words
This proposal may be a bit of a reach, leaning in to a simpler Web Workers- & PartyKit-esque pattern rather than the DO- & Rivet-esque fetch pattern. Would love thoughts, and please clarify anything I missed.
Link below ⬇️
One of the biggest Durable Objects misconceptions: Durable Objects ≠ Durable Properties
When your DO restarts/sleeps, poof – your in-memory data is gone 💀
ActorCore 0.7.2 adds `vars` to make this clear:
- state = persisted
- vars = ephemeral
changelog & source code below 🧵
📝 new docs & landing page for @rivet_gg
with ActorCore's launch, we're making a clearer distinction between Rivet (infra) and ActorCore (framework).
would love your thoughts!