$ cron job manager
Cron, minus the 3am debugging.
See, edit and run every cron job on every machine in one place, from your desktop, terminal or browser.
Where did that job actually run?
Crontabs pile up on every box you have ever SSHed into. norc lists every job on every machine in one view, each with its run history, and brings existing entries under management.
Did the 2am job even run?
A monitor can tell you a job failed. Cron cannot tell you a job never started. norc checks every job against its schedule and flags the runs that never happened.
Who can read the command in your crontab?
Cron commands often carry tokens and paths. norc encrypts job commands at rest and decrypts them only for your signed-in session. It is server-side encryption, not end-to-end, and the security page spells out exactly what that covers.
Still editing crontabs by hand over SSH?
Edit schedules in a UI with next-run previews. norc only touches the jobs it manages, so hand-written entries stay exactly as they are.
Want an AI assistant without handing it your servers?
Describe a job in plain words and norc's assistant proposes the schedule and command. It runs on your own API key from your own provider account, so you install no agent and give nothing shell access: it suggests, you review the diff, you apply. Prompts are not kept by default. If you turn on history, it is sealed in your browser to a key norc never sees.
What norc adds to cron
Cron doesn’t keep a run history or alert you when a job is missed. norc adds both, on top of the cron you already run.
Missed-run detection
norc checks every job against its schedule, so it flags runs that never happened after a reboot, a stopped daemon or a corrupted crontab.
Catch-up for missed runs
Laptop asleep at 2am? When it reconnects, norc queues the missed runs, up to the limit you choose.
One view of every machine
Laptops, servers and VMs in one list, each job with its run history. No more SSHing around to find where the 2am backup lives.
Safe edits, no SSH
Edit crontabs in a UI with next-run previews. norc only touches the jobs it manages; hand-written entries stay untouched.
Outbound-only agent
The agent connects out to norc. No inbound ports, no SSH keys handed over. Your system cron still runs the jobs, even if norc is down.
Plain-English schedules
Optional: describe a schedule and get the cron expression, with the next runs previewed. Bring your own key.
How it works
Pair a machine, see its jobs, get flagged when a run is missed. The agent connects outbound only.
Pair a machine
Link a laptop or server in a few seconds with a device code. Nothing inbound, no credentials to hand over.
See every job
Your existing crontab shows up as it is; hand-written entries are listed and left alone. Add or edit jobs in the UI or with norc jobs add.
Get told when a run is missed
norc checks each job against its schedule and alerts you when a run is missed or fails, then catches up what it can.
How norc differs from cron monitors
Monitors like Cronitor and Healthchecks.io notice when a job doesn’t check in. They don’t edit schedules remotely, show every machine in one place or catch up a missed run. norc does those and keeps the monitoring.
| norc | Healthchecks.io | Cronitor | Sentry Crons | |
|---|---|---|---|---|
| Pricing model | flat tier by machines and jobs | per job | per monitor + user | per cron monitor |
| Jobs keep running if norc is down | ✓ real cron runs them | n/a · monitors only | n/a · monitors only | n/a · monitors only |
| Edit jobs remotely, no SSH | ✓ | — | Partial · CLI only | — |
| One view of every machine | ✓ | — | — | — |
| Plain-English schedules (optional) | ✓ | — | — | — |
$ norc runs on macOS and Linux desktop and the command line. The iOS and Android apps are coming soon, and Windows desktop is in progress.
// cron runs your jobs. It never tells you when one doesn’t.
norc sits on top of it and does.