An order that waits days for a payment or a manager's approval survives crashes, restarts, and deployments in Cadence, a workflow engine that resumes each process exactly where it stopped. Developers write the order's logic as ordinary Go or Java code. The engine records every step in an event history and replays it to rebuild state on any worker. Activities send the emails, call the APIs, and write the database rows, each with its own retry policy, timeout, and heartbeat. A durable timer waits seconds or months without holding a thread, a cron schedule launches recurring runs, and a signal delivers the payment confirmation into the running workflow. Queries read its state without changing it, child workflows split big processes into reusable parts, and versioning allows code changes while older executions are still in flight. Domains separate teams and applications, task lists carry their own rate limits and priorities, global domains replicate across clusters and fail over between them, and archival retains closed histories. Cadence Web finds executions with SQL-like queries, lays out event history as a grouped table or a timeline, and exposes payloads, pending activities, and stack traces. It can start, reset, signal, cancel, or terminate runs, with batch actions for thousands of workflows at once. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.