iiinova — where your digital self keeps evolving

resonatehq.io @resonatehqio.bsky.social · 31/08/2026

Sign-ups for Resonate Cloud open September 9. For teams running agent loops in production: a restart reads back the steps that finished instead of buying them again. www.resonatehq.cloud?utm_source=b...

000

resonatehq.io @resonatehqio.bsky.social · 29/08/2026

resonate-ui reads every promise on your Resonate server and draws the run back as the call graph it came from. Decoded payloads, five states, Apache-2.0. journal.resonatehq.io/p/a-console-...

000

resonatehq.io @resonatehqio.bsky.social · 27/08/2026

Resonate now runs on three storage substrates: SQL (the server or resonate-pg), wide-column (ScyllaDB), and a message broker (resonate-on-nats). One protocol underneath all three. www.resonatehq.io/providers?ut...

020

resonatehq.io @resonatehqio.bsky.social · 26/08/2026

All execution state lives in the database. The server coordinates work but executes nothing, which makes database availability the only ceiling you need to plan against. docs.resonatehq.io/deploy/avail...

000

resonatehq.io @resonatehqio.bsky.social · 25/08/2026

Sharding resonate-on-nats isn't application code. A JetStream subject transform hashes each origin into a partition, and every partition consumer runs at MaxAckPending 1. www.resonatehq.io/providers/na...

000

resonatehq.io @resonatehqio.bsky.social · 24/08/2026

Lambda, Cloudflare Workers, GCP Functions, Supabase Edge Functions: adapting a Resonate worker to any of them changes one import. Durability lives in the protocol. docs.resonatehq.io/deploy/serve...

010

resonatehq.io @resonatehqio.bsky.social · 23/08/2026

An approval step that waits on a person usually needs a queue, a state row, and something polling both. With a durable promise the wait is the code. journal.resonatehq.io/p/the-approv...

000

resonatehq.io @resonatehqio.bsky.social · 21/08/2026

Durable execution normally means a broker for delivery plus a database for state. resonate-on-nats uses JetStream for both: KV stores promise state, pub/sub dispatches tasks. www.resonatehq.io/providers/na...

000

resonatehq.io @resonatehqio.bsky.social · 21/08/2026

A promise tagged resonate:timer resolves when its deadline passes: the wait finished. An ordinary promise that times out is rejected: the work ran out. www.distributed-async-await.io/server/timeo...

000

resonatehq.io @resonatehqio.bsky.social · 20/08/2026

ctx.sleep isn't a timer running somewhere. It creates a promise tagged resonate:timer with a deadline and no target — nothing executes while the wait lasts. www.distributed-async-await.io/sdk/time-ret...

000

resonatehq.io @resonatehqio.bsky.social · 19/08/2026

14 examples of durable execution on NATS, in TypeScript and Python — recovery, saga, human-in-the-loop, pipeline, versioning, deep-research-agent, structured concurrency, and more. Every one of them running on JetStream and nothing else. github.com/resonatehq/n...

000

resonatehq.io @resonatehqio.bsky.social · 17/08/2026

Durable execution now runs on NATS. JetStream is both storage and transport, so there is no second datastore to run. Workers connect from the TypeScript and Python SDKs. www.resonatehq.io/providers/na...

010

resonatehq.io @resonatehqio.bsky.social · 17/08/2026

A Resonate schedule is a server-side cron rule that creates a new durable promise on every tick. Workers never poll it — they receive the fired promises, routed by resonate:target. docs.resonatehq.io/reference/sc...

000

resonatehq.io @resonatehqio.bsky.social · 15/08/2026

A user session as one generator function: issued, activity logged, idle timer running, expired, tokens revoked. The session id is the workflow id; the idle wait is a durable sleep. briefs.resonatehq.io/EyFlxCI5?utm...

000

resonatehq.io @resonatehqio.bsky.social · 13/08/2026

Workers register under a group name. Adding capacity means starting another process in that group. There is no distribution logic to write. docs.resonatehq.io/get-started/...

000

resonatehq.io @resonatehqio.bsky.social · 10/08/2026

A durable promise is pending until someone settles it, then settled permanently — there is no third state. Every operation on it is idempotent. www.distributed-async-await.io/sdk/promise-...

000

resonatehq.io @resonatehqio.bsky.social · 08/08/2026

A durable function spends most of its life not running. Awaiting an unsettled promise, the worker registers a callback and lets the execution go. www.distributed-async-await.io/sdk/suspend-...

000

resonatehq.io @resonatehqio.bsky.social · 07/08/2026

Date.now() in a durable function returns a different value on replay, so the execution diverges. ctx.date.now() records the first result and returns that one on every replay after. docs.resonatehq.io/develop/cons...

000

resonatehq.io @resonatehqio.bsky.social · 04/08/2026

Resonate's TypeScript SDK runs a deterministic simulation test every 20 minutes. One seed decides which messages drop, duplicate or arrive late, and which workers die. docs.resonatehq.io/evaluate/how...

010

resonatehq.io @resonatehqio.bsky.social · 03/08/2026

After a crash Resonate replays from the top; finished steps return recorded results. Checkpoints land on durable steps — ctx.run, ctx.sleep, ctx.promise. Code between them re-runs. docs.resonatehq.io/develop/cons...

ctx.run

000

resonatehq.io @resonatehqio.bsky.social · 30/07/2026

Durable replay: after a crash the run restarts from the top, but every completed step returns its checkpointed result. No repeated work. journal.resonatehq.io/p/serverless...

000

resonatehq.io @resonatehqio.bsky.social · 30/07/2026

You don't pay to wait: a refund awaiting human approval suspends on a durable promise for a day at zero compute — no Lambda, no held connection. journal.resonatehq.io/p/serverless...

000

resonatehq.io @resonatehqio.bsky.social · 30/07/2026

Multi-agent pipelines tend to lose work at the handoff between agents. This essay shows how checkpointing those handoffs keeps a failure from throwing away what came before. journal.resonatehq.io/p/durable-ha...

000

resonatehq.io @resonatehqio.bsky.social · 29/07/2026

Durable human-in-the-loop: a tool creates a promise, hands the id to a human or webhook, and pauses. The agent resumes there — even if the process died. journal.resonatehq.io/p/serverless...

000

resonatehq.io @resonatehqio.bsky.social · 29/07/2026

Durable AI agents that survive a Lambda crash: PydanticAI + Resonate. Wrap your agent, add an id to each run — tools, agent, and output types untouched. journal.resonatehq.io/p/serverless...

010

resonatehq.io @resonatehqio.bsky.social · 29/07/2026

Resonate's core is open source under Apache 2.0 — a single binary you can run yourself. The full picture of what's free and what's paid: resonatehq.io/pricing

000

resonatehq.io @resonatehqio.bsky.social · 28/07/2026

Turn each Kafka message into a durable workflow, so per-message processing becomes crash-safe and recoverable instead of fragile. docs.resonatehq.io/get-started/...

000

resonatehq.io @resonatehqio.bsky.social · 27/07/2026

How the same durable-execution model maps onto different languages: generators and yield in TypeScript and Python, async futures and suspension in Rust. distributed-async-await.io/coroutines

000

resonatehq.io @resonatehqio.bsky.social · 26/07/2026

The durable promise is Resonate's core coordination primitive. Here is its complete formal specification — state-transition tables and all. docs.resonatehq.io/spec/program...

000

resonatehq.io @resonatehqio.bsky.social · 25/07/2026

Draining a Kubernetes node with a human approval gate in the middle — the drain pauses until someone approves and survives a crash while it waits. github.com/resonatehq-e...

000

resonatehq.io @resonatehqio.bsky.social · 24/07/2026

A durable AI agent with a human in the loop, on Supabase alone. It suspends on a human question — a Postgres row, zero compute — and resumes when you answer with one SQL call. github.com/resonatehq-e...

010

resonatehq.io @resonatehqio.bsky.social · 24/07/2026

How does a crashed function resume mid-execution? Deterministic promise ids — parent.0, parent.1, and so on — let replay line up with the work that already completed. distributed-async-await.io/replay-and-d...

000

resonatehq.io @resonatehqio.bsky.social · 23/07/2026

ctx.sleep(7 days) on Supabase: The Edge Function returns immediately. For seven days the workflow is one Postgres row. pg_cron wakes it within seconds of the deadline and the next invocation picks up from the checkpoint. Durable sleep costs zero compute. github.com/resonatehq/r...

110

resonatehq.io @resonatehqio.bsky.social · 23/07/2026

For the systems crowd: Resonate's recovery protocol — a lease-and-heartbeat liveness mechanism and a settle → resume → execute sequence that makes sure dependents are notified after a crash. The actual spec, not a marketing summary. docs.resonatehq.io/spec/executi...

000

resonatehq.io @resonatehqio.bsky.social · 22/07/2026

"Cancel within 5 seconds" implemented as a durable promise — a one-click buy with a built-in cancellation window that survives restarts. briefs.resonatehq.io/K-0rsUiD

000

resonatehq.io @resonatehqio.bsky.social · 21/07/2026

A durable research agent on nothing but Supabase and an Anthropic API key. It plans, fans out 7 searches — each its own Edge Function invocation — then writes a cited report. While searches run, the parent is a suspended Postgres row, not a process. github.com/resonatehq/r...

010

resonatehq.io @resonatehqio.bsky.social · 21/07/2026

A lesser-known page in the docs: using Claude Code with resonate-bash to run durable shell tasks that keep going after the session that started them ends. docs.resonatehq.io/get-started/...

000

resonatehq.io @resonatehqio.bsky.social · 20/07/2026

One SQL file turns a Supabase project into a durable execution engine. resonate-pg: durable promises, timers, and schedules as Postgres rows. pg_cron is the clock, pg_net is the transport, Edge Functions are the workers. No other infrastructure. github.com/resonatehq/r...

010

resonatehq.io @resonatehqio.bsky.social · 20/07/2026

Run branches in parallel as durable promises. A failed branch retries on its own while the others stay checkpointed — no re-running the whole batch. docs.resonatehq.io/get-started/...

000

resonatehq.io @resonatehqio.bsky.social · 19/07/2026

Event sourcing with no separate event store at all — the workflow replays domain events into a projection, and Resonate's durable promise cache is the only persistence layer. github.com/resonatehq-e...

000

resonatehq.io @resonatehqio.bsky.social · 18/07/2026

Expose a durable Resonate workflow directly as an MCP tool — so an agent can invoke long-running, crash-safe work through the same interface it uses for everything else. github.com/resonatehq-e...

100

resonatehq.io @resonatehqio.bsky.social · 17/07/2026

New to Resonate and want the "why" before the "how"? This page lays out what durable execution is for, where it fits, and the case for the approach. docs.resonatehq.io/evaluate/why...

000

resonatehq.io @resonatehqio.bsky.social · 16/07/2026

Echo's how-it-works page renders its workflows as live call graphs, read from the Resonate server. New: deep research — one durable run per question, fanned out in parallel. echo.resonatehq.io/how-it-works...

000

resonatehq.io @resonatehqio.bsky.social · 16/07/2026

A distributed mutex built from durable promise ordering — no separate lock service, just promises sequencing access across workers. briefs.resonatehq.io/bWLQfb3S

000

resonatehq.io @resonatehqio.bsky.social · 15/07/2026

Make a webhook handler safe against duplicate deliveries: use the event id as the promise id, and repeated deliveries collapse into a single execution. docs.resonatehq.io/get-started/...

000

resonatehq.io @resonatehqio.bsky.social · 14/07/2026

A model-based conformance suite for the Resonate server: a formal model of the promise/task contract driven against the live server over raw HTTP. 58/58 hand-written traces, 183/183 generated sequences, 1500+ fuzz ops — zero invariant violations. github.com/imnaseer/res...

000

resonatehq.io @resonatehqio.bsky.social · 14/07/2026

A tool-calling agent's loop is a durable workflow. Synadia's new example runs agent loops on NATS with the Resonate TypeScript SDK — kill the process mid-task and it resumes where it left off. github.com/synadia-ai/s...

010

resonatehq.io @resonatehqio.bsky.social · 14/07/2026

AWS Lambda caps a single invocation at 15 minutes. This example uses Lambda as a thin trigger while the real work runs on a durable Resonate worker — so the work can outlast the function. docs.resonatehq.io/get-started/...

010

resonatehq.io @resonatehqio.bsky.social · 13/07/2026

Account creation that pairs Resonate's durable execution with TigerBeetle, using a "Write Last, Read First" pattern for correctness. github.com/resonatehq-e...

000

resonatehq.io @resonatehqio.bsky.social · 12/07/2026

Sleep for hours or days inside a workflow without keeping a process alive or running a cron job. The workflow suspends and wakes itself when the time is up. docs.resonatehq.io/get-started/...

000