Developer documentation
Understand your plan and billing.
How Watchdog handles cancellation, failed payments, telemetry allowances, retention and the seven-day downgrade grace period.
Code and examples reviewed
Manage your plan in Account & billing. You do not need a payment card to use Developer.
| Included | Developer | Pro |
|---|---|---|
| Price | Free | US$19/month |
| Monitored jobs | 2 | 20 |
| Settled run history | 7 days | 30 days |
| Accepted events per UTC calendar month | 10,000 | 100,000 |
Upgrade and renewal
Checkout and payment-method management are hosted by Stripe. Pro renews monthly until you cancel. Returning from checkout alone does not grant access: Watchdog confirms the current subscription with Stripe. If your plan has not updated, refresh billing status in your account or contact support.
Cancellation and failed payments
Cancel in the billing portal from Account & billing. Cancellation stops the next renewal; Pro access stays active through the current paid period. When Stripe reports that paid status has ended—including an unpaid subscription—Watchdog starts a seven-day grace period with Pro monitoring and history limits.
A failed-payment notification does not itself decide access: Watchdog reconciles the current Stripe subscription status. Update your payment method through the portal. If payment recovers during grace, monitoring continues. If Stripe is unavailable, Watchdog waits for a fresh confirmation before pausing jobs.
Choose two jobs before downgrading
During Pro or its grace period, choose two enabled jobs in Account & billing. After the seven-day grace and fresh billing confirmation, those jobs remain monitored and the rest pause. If no valid choice is saved, the two oldest enabled jobs are kept. This pauses Watchdog monitoring only; it never cancels or retries your agents. After upgrading again, explicitly resume any paused jobs.
When an allowance is exhausted
Each accepted event counts, and a run can emit many events. Identical retries count once. Allowances reset at the start of each UTC calendar month. Deleting history does not reset usage. There are no automatic overage charges.
New events beyond the allowance receive HTTP 429 and are not monitored. A run also has a 5,000-event limit. Paused-job telemetry receives HTTP 409. Your agent should handle these delivery errors. Watchdog cannot evaluate an event that was rejected or never arrived.
History and support
History cleanup removes settled runs in batches after the plan’s window. Active runs, open incidents and outstanding deliveries may stay longer. See retention details. For billing errors or questions, email contact@withwatchdog.com. Cancelling renewal and requesting account deletion are separate actions.