Work that runs itself. On time, every time.
Run agent work on a schedule, once, or when something happens. Retries and caps are built in.

Sales report for #revenue
- Every Monday at 9:00
- Last run done
- Runs a Harness task
Set it once.
Routines start on time, run once, and recover on their own.
Any trigger.
A schedule, a single time, an API call, a webhook, GitHub or an event.
Never twice.
Idempotent runs, with overlap and concurrency caps.
Catches up.
Missed runs catch up. Repeated failures pause the routine.
On the record.
Every run in a hash-chained audit.
The details.
- Verified webhooksOnly verified calls start a run.
- RetriesA failed run tries again.
- Pause after failuresA routine that keeps failing pauses itself.
- Runs what you have A Titan session or a Harness task.
Where Routines sits.
One stack, from the agent to the ground it runs on.
Runs where you run.
From the public cloud to networks sealed from the world.
01CloudLive in minutes.
02EdgeBeside the work.
03On-premYour servers. Your walls.
04Air-gappedNothing gets out.
- Signed, hash-chained ledger
- Signed webhooks
- Concurrency caps
- Pauses after failures
Questions.
What can start a routine?
A schedule, a single time, an API call, a webhook, GitHub, or an event.
What does a routine run?
A Titan session or a Harness task.
What happens when a run fails?
It retries. If it keeps failing, the routine pauses until someone looks.
What if runs overlap or are missed?
Runs are idempotent, with overlap and concurrency caps, and missed runs catch up.



