The token that expired on day nine
A 90-day access token runs out mid-trip. The nightly sync gets a 401, retries every few seconds, and fills the logs. Nothing alerts, because nothing "crashed".
Agent Out-of-Office Kit
Can your agents run for ten days without you?
Twelve questions. A score, and the three things most likely to go wrong while you're away.
Free. Takes about two minutes. Your answers stay in your browser.
Your readiness score
Answer for everything that runs while you're away: agents, scheduled jobs, automations. If it's true for some but not all, answer no.
What breaks in week two
The first few days are usually fine. These are the kinds of problems that wait until you've stopped checking.
The job that just stopped
A server reboots for an update and the cron entry doesn't come back. No error, no email. You find out when a customer asks why the report never arrived.
The retry loop that ran all night
A provider rate-limits you at 2am. The agent retries instantly, forever. Every retry is a paid call. The budget alert email arrives, in an inbox you aren't reading.
The card that got declined abroad
Your bank flags a charge from another country and freezes the card. The provider's renewal fails, the account is suspended, and every job that depends on it goes with it.
The alert in the muted channel
The monitoring worked perfectly. It posted to the work Slack you muted on the way to the airport.
The agent that tidied up
An agent with delete rights decides a folder of "old" files is clutter. It's right that they're old. They were also the only copy.
Leave without watching the dashboard — $29
A pre-departure runbook, spend caps for every provider, and a heartbeat monitor that messages you when a job goes quiet. Runs on your own free Supabase project.
- Pre-departure runbook: one page, in order
- Spend-cap checklist, with where to look in each provider's console
- Heartbeat monitor: SQL plus a five-minute setup guide
- Ping snippets for curl, Python, Node, n8n and cron
- Kill-switch patterns, including a one-tap phone shortcut
- Return-day checklist
One-time payment. You host it; we never see your data.
Questions
Which Supabase tier do I need?
The free tier is enough. The monitor is three small tables and a check that runs every five minutes, well inside the free limits (as of November 2026, Supabase lists 2 active free projects and a 500 MB database). We suggest a fresh project just for this, so it can't interfere with anything else.
One thing to know: Supabase pauses free projects after a week of inactivity. Your pings and the five-minute check keep it busy, but Supabase doesn't spell out exactly what counts as activity, so the kit adds a short "all quiet" message every morning. If that message doesn't arrive, you know the monitor itself needs a look.
Which alert channels does it work with?
Anything that accepts a webhook. The setup guide has copy-paste settings for Discord, Slack, Telegram, ntfy and Google Chat. Pick one that buzzes your phone and that you won't mute on holiday.
Is any of my data sent to you?
No. The score on this page runs entirely in your browser. Your answers are saved only in your browser's local storage so they're there when you come back, and you can clear them any time. There are no trackers or analytics on this page.
The monitor runs in your own Supabase project, with your own keys. We never see your jobs, pings, logs or alerts.
What format is the kit?
Plain Markdown files, one SQL file and a CSV. They open in any editor, in GitHub, or in Notion. You get a download page straight after paying.
Do I need to be a developer?
You need to be comfortable pasting SQL into the Supabase editor and adding one HTTP call to the end of each job. If you've built an agent or an n8n workflow, you can do this.