Don't rewrite your jobs.
Govern them.
Temporal and Inngest want your business-critical work rebuilt on their framework. Weev puts a control plane in front of the jobs you already run — same code, explicit dependencies, every run accounted for.
One night of jobs nobody wants to migrate.
A rewrite is not a migration path.
Durable-execution frameworks assume you can rebuild the job. For settlement runs, billing batches and regulatory exports you can't — so they stay on cron and stay invisible.
Same script, same infrastructure. What changed is that the reason it runs is written down, checked, and visible to everyone who depends on it.
Teams whose worst outage would be a job that quietly didn't run.
Adopt it on a Tuesday. One job.
Nothing is rebuilt and nothing is cut over. Cron keeps firing until Weev owns the run — then you delete the line. The next job inherits the graph.
Three steps. No migration.
Where the job lives
Annotate jobs in your own code. Dependencies and batches become versioned, reviewable config.
Validated before release
The control plane checks the graph — cycles, missing edges, orphaned jobs. Invalid orchestration fails review, not production.
Why it ran, not just that
Every run traces back to a definition and a trigger. State, logs and timing in one place, live.
Start with one job.
Zero rewrites.
No credit card. No new runtime. Start with the job you check every morning.