Skip to content
TrustList
Funding news

Restate raises $20 million Series A for durable execution of workflows and AI agents

Editorial

By TrustList Editorial

Restate, a durable-execution infrastructure company reported by Tech.eu as Berlin-based, announced a $20 million Series A on 30 September 2026, led by Singular with Redpoint Ventures and Capital One Ventures. Replit is among its named customers.

About Restate raises $20 million Series A for durable execution of workflows and AI agents

Restate raises $20 million Series A for durable execution of workflows and AI agents

30 September 2026 — Restate announced on 30 September 2026 that it has raised $20 million in a Series A round. The company's own post does not state its headquarters; Tech.eu describes it as Berlin-based.

The round

  • Amount and stage: $20 million, Series A, from Restate's announcement.
  • Lead investor: Singular.
  • Other investors named: Redpoint Ventures and Capital One Ventures.
  • Use of the money: the post gives no itemised split; its roadmap covers taking durable execution beyond workflows, lowering cost and latency, and simpler operation.

What the company does

Restate makes infrastructure for what developers call durable execution: code that keeps its progress when a server crashes, a network call fails or a process restarts, and picks up where it left off without duplicating work. Developers use it to build payment flows, order processing, background jobs and, increasingly, AI agents, which run long chains of steps that call models and outside services. The company names Replit among its customers.

Why it matters for buyers

AI agents fail in the middle of tasks far more often than ordinary request-response code, and a failure halfway through can mean a duplicated payment or a lost order. Durable execution engines address this, and the category now has several funded vendors. TechCrunch tied the round to that demand from AI agents.

What to check

  • Engineering teams should compare deployment models (self-hosted open source or managed cloud), supported languages, and how state is stored and replicated.
  • Teams already using a workflow engine or message queue should weigh whether durable execution replaces part of that stack or adds to it.
  • Architects should test behaviour under failure: replays, timeouts, versioning of long-running workflows when code changes, and observability.
  • Procurement should review the open-source licence and what is reserved for the paid service.

Sources

Categories & features