RerunLabFree
$0/ month
- 5 enabled watches
- 10,000 checks per period
- 10-minute minimum interval
- 3 days of event and check history
- 1 projects · 1 members
- 10 manual delivery replays per day
NO AUTOMATIC OVERAGES
Clear limits.
Predictable polling.
Choose an allowance that fits how often you need to check. Enabled watches and included checks are separate limits.
Private beta: Free pilot access is available by invitation. Builder and Pro describe planned paid allowances; checkout is unavailable.
Builder
$19/ month
- 50 enabled watches
- 100,000 checks per period
- 1-minute minimum interval
- 7 days of event and check history
- 10 projects · 3 members
- 100 manual delivery replays per day
Pro
$49/ month
- 200 enabled watches
- 500,000 checks per period
- 1-minute minimum interval
- 30 days of event and check history
- 50 projects · 10 members
- 500 manual delivery replays per day
How many checks will you need?
4,320 checks in a 30-day period.
Estimate = watches × seconds in period ÷ interval. Expiry and failure backoff can lower actual usage. One watch every 60 seconds uses about 43,200 checks in 30 days.
What counts as a check?
One admitted source network attempt, including previews, manual checks, HTTP 304, upstream errors and timeouts. Local validation failures and waiting for concurrency do not count. A worker crash after dispatch is conservatively counted. Inbox reads and webhook retries do not consume source checks.
What happens at the limit?
Polling pauses. Retained events remain readable and existing deliveries continue. There are no automatic overage charges. Free allowances reset on the first of the month UTC; paid allowances follow the subscription period.
Billing and changes
Paid subscriptions, when enabled, bill monthly in USD. Applicable taxes are shown in checkout. Cancellation and downgrades take effect at paid period end. Surplus watches pause without deleting their history; shorter intervals must be edited before resuming on Free. Existing events keep their original expiry.
Delivery limits
One optional webhook per watch. At most eight delivery attempts within 24 hours. Replay requires retained payloads with a full 24-hour window remaining. No unlimited event, delivery or retention promise.
Read all limits →Common questions
Does this reduce API requests?
It moves polling to RerunLab. Conditional requests can reduce transferred data when supported, but upstream requests still occur.
Is it real time?
No. Events follow successful checks at the configured interval; failures and backoff can increase delay.
Can it watch any URL?
V1 supports publicly reachable HTTPS JSON GET endpoints under documented limits. No browser pages, private networks or automatic pagination.
Can my agent receive events?
Through a connected webhook workflow or later inbox retrieval. Automatic wake-up depends on the agent’s runtime.
Do you support WebSockets?
Not in the initial release. Use signed webhooks or the durable inbox.
What happens when I run out of checks?
Source polling pauses; retained events remain accessible and existing deliveries continue. There are no automatic overage charges. Maximum watch count and included checks are separate limits.
Can I just use cron?
Yes. RerunLab packages scheduling, comparison state, failures, delivery retries and history into a managed service.
What do you store?
Encrypted credentials, selected values needed for comparisons and events, and operational metadata for documented retention periods. Full source responses are not permanently archived.