Scheduled tasks
Cron expressions with a real execution history. Skip, queue, or terminate overlapping runs. Catch up missed firings after a reboot. Page Slack, Telegram, or email on failure.
One binary · Linux · macOS · WSL · 25 MB RAM idle Schedule, supervise,
Schedule, supervise,
observe. One binary.
It's 3 AM. Your backup didn't run. You won't know until morning. RunWisp fixes that - one static binary that replaces crond, supervisord, and the tab you forgot to open.
Install in 30 seconds
curl -fsSL https://get.runwisp.com | sh No Node, no Python, no Docker required. Or grab a release binary.
Example run history: backup-db retried once and recovered, certbot and sync-s3 all green, worker service up 41 days.
Three jobs, one process, one file.
Scheduled tasks, long-running services, and health checks, all defined in the same runwisp.toml and run by the same daemon.
Long-running services
Supervise worker processes with restart policies, instance counts, and graceful-stop windows. Same TOML file, same dashboard, same logs.
Health checks
Hit an endpoint, exit non-zero if it's broken. RunWisp captures the run, keeps the output, and pages you the way you want to be paged.
Plain cron is invisible.
crond runs your job, dumps stderr somewhere you'll never read, and forgets about it. No exit-code history. No "did the last run finish?" No notification when it didn't.
RunWisp captures every run (stdout, stderr, exit code, duration) and keeps the last N per task in embedded SQLite. Stream the output live in your browser. Re-trigger with one click. SSH at 3 AM is optional now.
Not a DAG engine. If you need workflows with dependencies, reach for Dagu or Airflow. RunWisp does one machine, well.
crontab fire & forget
# did this run? find out tomorrow.
0 3 * * * /usr/local/bin/backup.sh runwisp.toml every fire, recorded
[tasks.backup]
cron = "0 3 * * *"
retry_attempts = 2
notify_on_failure = ["slack-ops"]
keep_runs = 60
run = "/usr/local/bin/backup.sh"Same data, two surfaces.
A Svelte dashboard ships inside the binary; a TUI for SSH sessions. No extra installs, no separate server.
localhost:9477 trigger runs · stream logs live
runwisp tui the same view, over SSH
Up and running in three commands.
From curl to "my backups have a dashboard." No package-manager wrangling, no runtime to install.
1/3
Install the binary
One curl. A single static Go binary lands on your PATH.
$ curl -fsSL https://get.runwisp.com | sh
2/3
Write runwisp.toml
Tasks and services in one file, checked into your repo. The schema is the source of truth.
[tasks.backup-db]
cron = "0 2 * * *"
on_overlap = "skip"
keep_runs = 30
run = "pg_dump db | gzip > dump.gz"
[services.worker]
run = "./bin/worker"
restart = "on-failure"
cron = "0 2 * * *"
on_overlap = "skip"
keep_runs = 30
run = "pg_dump db | gzip > dump.gz"
[services.worker]
run = "./bin/worker"
restart = "on-failure"
3/3
Run runwisp
Schedules fire, services supervise, logs persist. Open the dashboard on :9477, or stay in the terminal.
$ runwisp
# → dashboard at http://localhost:9477
# → dashboard at http://localhost:9477
Predictable, observable, scriptable.
The stuff a solo dev or a small ops team actually needs, without standing up Airflow.
history
Every run, every detail
Exit code, duration, stdout, stderr, timestamps: captured for every firing, browsable in the UI, queryable over REST. No silent failures.
binary
One binary, zero deps
Static Go binary. No Python, no Node, no external database. Embedded SQLite, embedded dashboard. Runs on a Raspberry Pi.
toml
TOML is the source of truth
Schedules, retries, services, notifiers, all in runwisp.toml. The dashboard reads and triggers; it never edits your config.
on_overlap
Never let runs stack up
Per-task on_overlap: skip, queue, or terminate. Per-service instance counts. Restart backoff that resets on stability.
catch_up
Reboots don't drop runs
Boot the machine, start RunWisp, and missed firings replay, bounded by max_catch_up_runs. No quiet gaps in your history.
notify
Notify the way you want
Slack, Telegram, Discord, email, webhook, or an in-app bell. Per-task overrides. Flapping coalesces into one alert, not a storm.
ui
Web + terminal UI
A Svelte dashboard ships inside the binary. A Bubbletea TUI for SSH sessions. Same data, two surfaces, no extra installs.
logs
Live log streaming
Watch a task's output as it happens, in the browser or over SSH. Tail historic logs without grepping through files.
offline
Works without internet
Everything runs with the network unplugged. No phone-home, no account, no dependency on anyone's servers to fire a job.
What it replaces, and what it doesn't.
RunWisp sits between "edit crontab over SSH" and "stand up Airflow." Here's the honest yes/no against the tools you're probably running today.
| Capability | cron | systemd timers | supervisord | PM2 | RunWisp |
|---|---|---|---|---|---|
| Run history per firing | ✗ | journal | ✗ | limited | ✓ |
| Captured stdout / stderr | ✗ | journal | ✓ | ✓ | ✓ |
| Retries with backoff | ✗ | unit | ✗ | restarts | ✓ |
| Failure notifications | ✗ | ✗ | ✗ | ✗ | ✓ |
| Catch-up after downtime | ✗ | persistent | ✗ | ✗ | ✓ |
| Scheduling + supervision in one | ✗ | two units | ✗ | conflated | ✓ |
| Built-in web dashboard | ✗ | ✗ | basic | paid | ✓ |
| Single static binary, no runtime | ✓ | ✓ | Python | Node | ✓ |
| Same on macOS / WSL / Docker | varies | Linux | ✓ | ✓ | ✓ |
| Pre-installed on the box | ✓ | ✓ | ✗ | ✗ | ✗ |
Deep dives, side-by-side configs & migration cheat sheets:
vs cron
vs supervisord
vs systemd timers
vs PM2
vs Ofelia
vs Jobber
vs Dagu
FAQ
Does RunWisp need to run as root?
No. Run it as whoever owns the work. When the daemon does run as root, set
user = "deploy" per task or service to drop privileges. Otherwise every task runs as the daemon's user.Can it run alongside my existing crontab while I migrate?
Yes. RunWisp doesn't touch
/etc/crontab or anyone's user crontab. Move one job at a time. runwisp import cron reads an existing crontab and emits an annotated runwisp.toml with # TODO markers where a human decision is needed.What does it cost? What's the license?
The daemon is Apache-2.0, free to self-host, forever. No telemetry, no account, no paid tier gating any feature. The Web UI and TUI ship in the binary.
Which platforms does it run on?
One Go binary on Linux, macOS, WSL, and Docker, about 25 MB RAM idle. Same TOML, same SQLite conventions, same dashboard port everywhere. The only platform-specific piece is the autostart wrapper (systemd unit, launchd plist, or container init), documented per OS.
Is it a workflow / DAG engine?
No, and proudly so. RunWisp runs independent tasks and services on one machine. If you need multi-step pipelines with dependencies and conditionals, use Dagu or Airflow. RunWisp is the layer below that, and most boxes never need more.
How does it handle timezones and DST?
Cron expressions evaluate in a configured timezone, per-task if you want. Fall-back fires once (the suppressed firing is still recorded in history); spring-forward fires once at the next valid minute. DST is named, auditable behaviour, not an annual silent bug.
apache-2.0 · no telemetry · free to self-host
Start in 30 seconds. Ship on your terms.
A single Go binary. If it doesn't earn the disk space, rm it. No account, no signup, no catch.
Install in 30 seconds
curl -fsSL https://get.runwisp.com | sh