Skip to content

Work

Recurring operations

Automations

Start it without being there.

An automation is a mission with a trigger. A schedule is the common one — a nightly pass over a repository — and a run can also be started by hand or by an incoming webhook. Missed occurrences are handled explicitly: a machine that was asleep at 2 AM can run the occurrence it missed, run only the most recent one, or skip them, rather than silently doing nothing.

Concurrency is a choice

When a run is still going and the next is due, the automation can skip it, queue it, or cancel the older one.

Runs keep their history

Each run records what triggered it, when it was scheduled for if it fired late, what it cost, and how it ended.

The morning report

Catch Me Up assembles what happened from Velora's own records — findings, checks, decisions and spend — rather than asking a model to summarise the night.

Driveable from a script

The terminal app can list what is waiting and act on it, so an automation can hand off to your own tooling.

Need help? Contact Velora support →