# Resonate Documentation

> Resonate — durable execution, dead simple. Build agents, workflows, pipelines,
> and services without thinking about retries or recovery.

## Docs Pages

- [Errors](https://docs.resonatehq.io/debug/errors): Error codes and what they mean.
- [Debug a Resonate application](https://docs.resonatehq.io/debug): Diagnose and fix issues in Resonate applications.
- [Troubleshooting](https://docs.resonatehq.io/debug/troubleshooting): Common problems and how to fix them.
- [Availability](https://docs.resonatehq.io/deploy/availability): High availability strategies for Resonate deployments.
- [Deployment patterns](https://docs.resonatehq.io/deploy/deployment-patterns): Deploy Resonate to different environments - Docker, Kubernetes, serverless, and more.
- [Deploy a Resonate application](https://docs.resonatehq.io/deploy): Deploy Resonate from development to production.
- [Kafka integration](https://docs.resonatehq.io/deploy/kafka): How to integrate Resonate with Kafka today (the worker pattern) and what to expect when native Kafka transport ships.
- [Logging](https://docs.resonatehq.io/deploy/logging): Server and SDK logs for observing application behavior.
- [Message transports](https://docs.resonatehq.io/deploy/message-transports): Configure message transport plugins for communication between workers and server.
- [Metrics](https://docs.resonatehq.io/deploy/metrics): Prometheus metrics exposed by the Resonate server.
- [Production readiness](https://docs.resonatehq.io/deploy/production-readiness): Recommended deployment shape, server constraints, and operational checklist for running the Resonate server in production.
- [Server providers](https://docs.resonatehq.io/deploy/providers): Run the Resonate protocol on infrastructure you already operate — the core server, or a provider implementation built for a specific platform.
- [Resonate on NATS](https://docs.resonatehq.io/deploy/providers/nats): Run the Resonate protocol on NATS JetStream — setup, partitioning, the SDK client, and what to know before production.
- [Resonate on ScyllaDB](https://docs.resonatehq.io/deploy/providers/scylladb): Run the Resonate server protocol against a ScyllaDB cluster — setup, configuration, and what to know before production.
- [Deploy to Railway](https://docs.resonatehq.io/deploy/railway): Run the Resonate server on Railway with a managed Postgres database.
- [Run a server](https://docs.resonatehq.io/deploy/run-server): Start the Resonate server with persistent storage.
- [Scaling](https://docs.resonatehq.io/deploy/scaling): Scale Resonate workers horizontally to handle increased load.
- [Security](https://docs.resonatehq.io/deploy/security): Authentication and production security.
- [Serverless workers](https://docs.resonatehq.io/deploy/serverless-workers): Deploy workers to serverless platforms (Lambda, Cloud Functions, etc).
- [Tracing](https://docs.resonatehq.io/deploy/tracing): OpenTelemetry tracing for Resonate applications.
- [Upgrade server](https://docs.resonatehq.io/deploy/upgrade-server): Upgrade the Resonate server to a new version.
- [Constraints and gotchas](https://docs.resonatehq.io/develop/constraints): Understanding the rules and limitations when building with Resonate.
- [Go SDK skills](https://docs.resonatehq.io/develop/go): APIs that stay simple, even when your use cases aren't
- [Develop with Resonate](https://docs.resonatehq.io/develop): Build distributed applications without the distributed systems complexity.
- [Java SDK skills](https://docs.resonatehq.io/develop/java): APIs that stay simple, even when your use cases aren't
- [Python SDK skills](https://docs.resonatehq.io/develop/python): APIs that stay simple, even when your use cases aren't
- [Rust SDK skills](https://docs.resonatehq.io/develop/rust): APIs that stay simple, even when your use cases aren't
- [TypeScript SDK skills](https://docs.resonatehq.io/develop/typescript): APIs that stay simple, even when your use cases aren’t
- [BYODE](https://docs.resonatehq.io/evaluate/coming-from/byode): Compare Resonate with building your own durable execution stack.
- [DBOS vs Resonate](https://docs.resonatehq.io/evaluate/coming-from/dbos): Side-by-side comparison of DBOS and Resonate — programming model, deployment, and dependencies — to help you evaluate Resonate as a DBOS alternative.
- [Coming from](https://docs.resonatehq.io/evaluate/coming-from): Compare Resonate with other durable execution platforms and approaches.
- [Restate vs Resonate](https://docs.resonatehq.io/evaluate/coming-from/restate): Side-by-side comparison of Restate and Resonate — programming model, deployment, and guarantees — to help you evaluate Resonate as a Restate alternative.
- [Temporal vs Resonate](https://docs.resonatehq.io/evaluate/coming-from/temporal): Side-by-side comparison of Temporal and Resonate — programming model, deployment, and guarantees — to help you evaluate Resonate as a Temporal alternative.
- [How it works](https://docs.resonatehq.io/evaluate/how-it-works): Architecture overview of checkpoints, replay, and message flow in Resonate.
- [How Resonate is tested](https://docs.resonatehq.io/evaluate/how-resonate-is-tested): How Resonate uses deterministic simulation testing (DST) to find concurrency and failure bugs conventional tests miss — server, every SDK, and a Lean 4 spec.
- [Evaluate Resonate](https://docs.resonatehq.io/evaluate): Get started with Resonate by evaluating its features and capabilities.
- [Why Resonate](https://docs.resonatehq.io/evaluate/why-resonate): Resonate is the durable execution engine that agents build with, deploy on, and operate — at a fraction of the cost of anything else.
- [Durable bash](https://docs.resonatehq.io/get-started/claude-code): Wire Claude Code to a local Resonate server so your coding agent can run durable, asynchronous shell scripts — locally, in Docker, or in a remote sandbox.
- [Resonate CLI](https://docs.resonatehq.io/get-started/cli-guide): Learn how to use the Resonate command-line interface effectively.
- [Async agent tools](https://docs.resonatehq.io/get-started/examples/async-agent-tools): Convert synchronous MCP tool calls into durable async jobs an LLM can fire-and-forget then poll for results.
- [Async HTTP APIs](https://docs.resonatehq.io/get-started/examples/async-http-api-endpoints): Turn long-running HTTP requests into durable workflows. Clients fire-and-forget, then poll for completion.
- [Async RPC](https://docs.resonatehq.io/get-started/examples/async-rpc): Functions in different processes call each other through Resonate. Each call is durable; chains survive crashes anywhere along the path.
- [Deep research agent](https://docs.resonatehq.io/get-started/examples/deep-research-agent): An LLM agent that decomposes a topic, spawns parallel subagents, and joins their results — every call durable and recoverable.
- [Cloud Run workers](https://docs.resonatehq.io/get-started/examples/durable-serverless-cloud-run-workers): A Resonate workflow running on Cloud Functions Gen 2 — every sleep checkpoints, every restart resumes.
- [Lambda workers](https://docs.resonatehq.io/get-started/examples/durable-serverless-lambda-workers): Lambda receives the request, returns 202, and fires a durable Resonate workflow that can run for hours — past Lambda's timeout ceiling.
- [Durable sleep](https://docs.resonatehq.io/get-started/examples/durable-sleep): A workflow that sleeps for seconds, days, or months — without holding a process open or rolling your own scheduler.
- [Fan-out / fan-in](https://docs.resonatehq.io/get-started/examples/fan-out-fan-in): Spawn N tasks in parallel, collect their results — every spawn and every result is a durable promise.
- [Hello world](https://docs.resonatehq.io/get-started/examples/hello-world): A minimal workflow that orchestrates two leaf functions, registered and invoked through Resonate.
- [Human-in-the-loop](https://docs.resonatehq.io/get-started/examples/human-in-the-loop): Pause a Resonate workflow until a human responds — and resume it from any process — using durable promises.
- [Examples](https://docs.resonatehq.io/get-started/examples): Runnable example projects, one per pattern.
- [Kafka worker](https://docs.resonatehq.io/get-started/examples/kafka-worker): A worker that consumes Kafka, dispatches durable workflows for each message, and resumes cleanly after crashes — Redpanda is a drop-in replacement.
- [Load balancing](https://docs.resonatehq.io/get-started/examples/load-balancing): Run multiple workers in a group; Resonate dispatches work to whichever is available, recovers it when one dies.
- [Money transfer](https://docs.resonatehq.io/get-started/examples/money-transfer): A two-step transfer (debit source, credit target) where each step is a durable checkpoint and the same transfer ID deduplicates retries.
- [Multi-agent orchestration](https://docs.resonatehq.io/get-started/examples/multi-agent-orchestration): An orchestrator chains three specialist agents — researcher, writer, reviewer — with each handoff checkpointed.
- [Recursive factorial](https://docs.resonatehq.io/get-started/examples/recursive-factorial): A workflow that calls itself with `ctx.rpc` — recursion is automatically distributed and durable.
- [Schedule](https://docs.resonatehq.io/get-started/examples/schedule): Register a function to run on a cron schedule. Each invocation is a durable workflow with crash recovery built in.
- [Webhook handler](https://docs.resonatehq.io/get-started/examples/webhook-handler): A Stripe-style webhook handler where the event ID is the workflow ID — duplicate deliveries dedupe, partial failures resume, the customer gets charged once.
- [Get started with Resonate](https://docs.resonatehq.io/get-started): Quickstart, examples, and migration guides.
- [Quickstart](https://docs.resonatehq.io/get-started/quickstart): Install the server and SDK and run your first Resonate workflow.
- [Durable Execution Docs](https://docs.resonatehq.io/index): Resonate — agent-native durable execution. Generated, optimized, cost-efficient by design.
- [CLI reference](https://docs.resonatehq.io/reference/cli): Canonical reference for every Resonate CLI command — server, promise, task, schedule, invoke, tree, MCP — with usage scenarios and worked examples.
- [Defaults reference](https://docs.resonatehq.io/reference/defaults): Canonical reference for default values across the Resonate server and SDKs (TypeScript, Python, Rust).
- [Reference](https://docs.resonatehq.io/reference): Canonical, source-cited reference for Resonate defaults, the resonate CLI, and schedule/cron behavior.
- [Schedules & cron reference](https://docs.resonatehq.io/reference/schedules): Canonical reference for Resonate schedules — cron expression format, day-of-week convention, UTC timezone, the resonate:target requirement, promise-ID templates, and the tags the server injects at fire time.

## External References

- [Distributed Async Await Specification](https://www.distributed-async-await.io/spec): The formal, language-agnostic protocol specification that Resonate implements.