Making durable execution a building block for every application

Restate is on a mission to make durable execution a building block for every AI agent or backend - efficient, fast, and highly scalable.

Why we're building Restate

Our motivation

We started Restate over our frustration about how hard it is to build any non-trivial piece of backend logic. Control planes, workflows, API orchestration. We were solving the same problems in the application logic again and again - retries, concurrency, carefully ordered updates - only to find the next person accidentally breaking the sensitive assumptions in the application.

When we built Apache Flink, one of the core ideas was to make stateful stream transformations a building block from which you could compose a wide range of streaming applications. We wanted something similar for the asynchronous, event-driven, long-running work that increasingly makes up our backends.

Our vision

For durable execution to become part of how backends are built, it cannot stay an expensive tool you bring in for a few complicated workflows. It needs to be efficient enough to use everywhere, fast enough for latency-sensitive paths, simple enough to deploy wherever your applications run, and flexible enough to model more than workflows.

That is what we are building: the runtime underneath agents, workflows, and distributed applications, where durability, state, communication, and coordination feel like normal programming primitives.

Durable Execution is the starting point,
not the destination.