Show HN: Waymark – A workflow engine that compiles jobs instead of replaying
Hey everyone! @mozgiii and I have been working on Waymark for the better part of the last year. Waymark’s an open source durable execution library with similar functionality to Temporal or DBOS. A few unique design decisions: — Write jobs in normal code (right now Python but JS coming soon). Instead of running control flow as-is, which requires booting up an interpreter to replay past state, we’ll just compile your code directly. We walk your AST and map your logic to our stackless VM bytecode.
Read original source
Source record
Recorded metrics
points · 4 votes
2026-11-05 15:13:39.355Z
cumulative since publication
Research analysis
Project record
Repository: piercefreeman/waymark. Source account: Hey everyone! @mozgiii and I have been working on Waymark for the better part of the last year. Waymark’s an open source durable execution library with similar functionality to Temporal or DBOS. A few unique design decisions: — Write jobs in normal code (right now Python but JS coming soon). Instead of running control flow as-is, which requires booting up an interpreter to replay past state, we’ll just compile your code directly. We walk your AST and map your logic to our stackless VM bytecode.
Observed adoption & comparisons
Source votes: 4 votes (Nov 5, 2026 UTC; cumulative since publication); previous same-scope observation: 4 (Nov 5, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “D4Vinci/Scrapling” (GitHub Trending, Nov 5, 2026); “garrytan/gstack” (GitHub Trending, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.