Restate is hiring across two distinct but equally exciting spaces. Hi friends! We are looking to fill two quite different positions, in the Cloud and core Runtime teams. Plenty of Rust, distributed systems, AWS, proprietary magic, and a side of RocksDB. Sound interesting?

Not every workflow step depends on the one before it. To save time, you can run tasks in parallel. But that's not easy. You need to manage concurrency, handle retries, and build persistence to remember which tasks already succeeded after restarts. Restate has this built-in. 👇

Restate + Vercel AI SDK = enterprise-grade durability for your AI agents with just a few lines of code. Survive crashes, timeouts, and restarts - even for multi-turn conversations, human approval and long-running research agents. @vercel @aisdk

Building multi-regional systems is hard, evolving existing systems even more so. Restate replicates your application state across regions - not just for DR failover, continuous active replication and automated reconfiguration - with no code changes required.

If yesterday's AWS outage made you rethink your infrastructure, this blog post shows exactly how to build apps that stay up when the cloud goes down. 📖 Full story + technical details:

Building geo-replicated apps traditionally means * Wrestling with state consistency * Implementing custom replication * Handling split brains * Rewriting your application With Restate, it's just a config setting. No application code changes. Your business logic stays the same💪

AWS's recent us-east-1 outage took down ChatGPT, Snapchat, and Perplexity. The same thing happened in 2021—Netflix, Disney+, and Robinhood all went dark. The culprit? Lack of geo-replication. With @restatedev you can build applications that keep running even if AWS is down. 🧵

We ran a Restate app deployed in multiple regions, then killed an entire region. Result: ✅ Zero downtime ✅ Auto-failover in <60s ✅ No data loss ✅ All requests processed

With Restate, geo-replication is a deployment detail, not an application concern. Write normal business logic. Deploy across regions with one config line: 'default-replication = "{region: 2, node: 3}"'

If yesterday's AWS outage made you rethink your infrastructure, this blog post shows exactly how to build apps that stay up when the cloud goes down. 📖 Full blog post:

AWS’s us-east-1 outage took down ChatGPT, Snapchat & Perplexity. The same happened in 2021: Netflix, Disney+, and Robinhood all went dark. The reason? Often a lack of true geo-replication. Here's how you can run apps with zero downtime during a region failure using Restate 🧵

How do you turn your agent code into something reliable and scalable to run millions of executions? We tried building a cloud coding agent with @restatedev for workflows, @modal for sandboxes, @vercel for compute, and GPT-5 / Claude as the LLM. Think a mini version of cursor

Webhooks that just work with @restatedev ✅ Event persistance - let Restate acknowledge and persist the event ✅ Reliable processing - leverage Durable Execution to run until completion ✅ Idempotency - use Idempotency-Key to deduplicate Check it out! https://t.co/uhr0zU4ojV

Restate Cloud is now publicly available! @PavelTcholakov takes you through everything you need to know to get started smoothly: https://t.co/dGUnx02lA6

Weekend read: 𝗔𝗴𝗲𝗻𝘁𝘀 𝘀𝗵𝗼𝘂𝗹𝗱 𝗯𝗲 𝗦𝗲𝗿𝘃𝗲𝗿𝗹𝗲𝘀𝘀 (𝗮𝗻𝗱 𝗗𝘂𝗿𝗮𝗯𝗹𝗲) Serverless platforms are amazing for many AI agents, especially if they do a lot of bursty work (chat sessions with long inactivity) or react to events (approvals). Two things are needed

Combine your favorite AI SDK with a serverless platform and Restate for durable, resilient agents that: ✅ Survive crashes & timeouts ✅ Scale to zero while waiting for approvals ✅ Run 10K+ concurrent agents ✅ Live execution timelines ✅ Safe versioning https://t.co/7ZaWlqAIWH

We just published a new post on building production-grade serverless AI agents. Serverless is perfect for bursty agentic workloads, but you quickly hit limits for long-running, stateful tasks, like human approvals. Here’s how we fixed that 👇

Yesterday we made Restate Cloud public, today is about 𝗥𝗲𝘀𝘁𝗮𝘁𝗲 𝟭.𝟱. The biggest changes are improving 𝗼𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆 (timelines and histories) and managing durable executions. One of my favorite new features is 𝗿𝗲𝘀𝘁𝗮𝗿𝘁𝗶𝗻𝗴 invocations. If you ever

👉 Discover all the new features in this blog post:

🚀 Yesterday, we announced that 𝗥𝗲𝘀𝘁𝗮𝘁𝗲 𝗖𝗹𝗼𝘂𝗱  is now publicly available. Today, we’re announcing 𝗥𝗲𝘀𝘁𝗮𝘁𝗲 𝟭.𝟱! This release brings key features for building, controlling and observing your durable agents and workflows.