Overview
Documentation
Hopskip is a durable execution engine, in the same family as Temporal. You write a workflow as an ordinary async function. Hopskip records every step it takes in an event log, so if the process dies mid-run, the workflow resumes from where it left off instead of starting over.
Three design choices separate it from orchestrators built on task polling:
- Sandboxed execution. Workflow code runs inside a Wasm runtime that Hopskip controls. Determinism is enforced at the sandbox boundary, not by lint rules and code review.
- A log-structured, cryptographically verifiable event store. State is an append-only log with Merkle commitments, tiered from memory to object storage and queryable in place.
- Push-based dispatch. Workers hold persistent bidirectional gRPC streams to the server. The server sees every task first, so retries and other resilience policies are declared server-side instead of written into each worker.
What you get
- Workflows are ordinary async functions. Mark the durable entry point
and every
awaitbecomes a checkpoint. No base class to extend, no replay annotations, noContinueAsNew. - Millisecond replay. Memory snapshots every N events keep the cost of resuming a workflow constant, no matter how long it has been running.
- Verifiable history. Every event carries the SHA-256 of its predecessor and the OIDC identity of its trigger, forming a per-workflow Merkle Mountain Range. Any run’s history can be proven with an inclusion proof.
- SQL visibility, built in. The server projects the log into an embedded columnar store, so you can query live workflow state in plain SQL. No Elasticsearch.
- Polyglot, and proven. TypeScript, Python, Rust, Haskell, and Go are launch languages. A cross-SDK conformance suite runs every feature in all five with interchangeable histories: a history recorded by one SDK replays through any other.
Where to go next
| If you want to | Read |
|---|---|
| Run your first workflow | Getting started |
| Understand the execution model | Durable execution |
| Know why replay is safe | Determinism & the sandbox |
| See what executes your code | Workflow modes |
| Pick an SDK | TypeScript · Python · Rust · Go · Haskell |
| See the whole system | Architecture |
Status: draft 0.1. Hopskip is pre-1.0. The workflow ABI (
hopskip:workflow@x) is frozen per version, but SDK ergonomics and the CLI are still moving. See Compatibility & versioning for what is stable today.