Waitcher checks your websites, APIs and certificates on a
schedule, tells you when something fails and keeps the evidence so
you can see what went wrong.
The playground runs in your browser and sends no requests.
The last 24 hoursSample data. Each tick is one check; its height is the response
time.
leafarcade.comWebsite
48 of 48 passed
api.example.com/healthAPI
503 at 16:00 and 16:30, Slack alerted
46 of 48 passed
vividqr.appCertificate
Expires in 61 days
Nightly backupHeartbeat
Pinged at 02:04
00:0006:0012:0018:00Now
How it works
Add what matters
A website or API address, a certificate to watch or a heartbeat
for a scheduled job.
Hear about failures
Checks run on a schedule. After repeated failures an incident
opens and you get a message in Slack, by email or through a
webhook.
See why
Every run keeps its status, timing and failure reason, so you
can tell an outage from a slow response.
In early access
Website and API checks over HTTPS
Certificate expiry checks
Heartbeats for scheduled jobs
Incidents and alerts to Slack, email or webhooks
Up to 3 monitors, checked every 30 minutes, free
After launch
Browser journeys
Visual change checks
AI feature and agent checks
Public status pages
Prefer the terminal?
Write and run checks locally with the Waitcher CLI. Local runs
need no account. Connect to your workspace when you are ready.
Requires Node.js 24.15 or later.
Get the Waitcher CLI
Loading the verified archive…
Then run a local HTTP check
waitcher monitor init --file website.monitor.json --target https://example.com/
waitcher monitor validate --file website.monitor.json
waitcher run local --file website.monitor.json
Set up API and browser scripts
Prepare one runtime directory with the pinned test framework and
its Chromium build. HTTP checks do not need it.
waitcher monitor init --type browser --file shop.monitor.json --target https://example.com/
waitcher run local --file shop.monitor.json --runtime /path/to/waitcher-runtime
Runs save logs, traces and screenshots under
.waitcher/runs; add --video for a
recording. Local scripts are trusted code on your machine.
Connect to a hosted workspace
Run waitcher auth login to sign in through your
browser, then waitcher system capabilities to see
what your workspace can run. Apply a monitor paused, inspect one
run, then enable its schedule.
Launching soon. Start watching today.
Explore the playground now, or create a free account and watch up to
three sites.
Personal workspace/Monitors
Monitors
Know what works. See what changed.
Guest playground. All results and checks are
simulated. Changes stay in this tab. A free account runs real
checks: 3 monitors, every 30 minutes or longer.
Demo workspace Illustrative results, isolated from
live reports. No checks run here.
All schedules are paused. You can run a live check
once without enabling its schedule.
Execution report
Completed checks only. Missing checks are not counted as
passes.
Release comparison
Compare retained results attributed to each release. Timing does
not establish a cause. Execution errors are inconclusive, and
missing history is not a pass.
Probe diagnostics Administrator view
Resource use and storage limits for the shared probe.
Monitor
Status
Success · 24h
Last checks
Actions
Add your first monitor
Watch a website, an API, a browser journey, a scheduled
job or an AI feature.
No matching monitors
Try another name, target or filter.
Project timeline
Deployment markers and check outcomes are separate evidence.
Events are shown in UTC.
One probe. Clear evidence. All checks run from
the same server. A passing check verifies its assertions at that
moment; it does not guarantee continuous availability.
Visual review is not enabled in this workspace
This workspace has not enabled visual review. Your existing
monitors continue to run.
Visual demo. Fictional sample images. Approvals
stay in this tab; no website requests or schedules. Compare
images, then approve a sample candidate.
AI connection settings are not enabled for this workspace.
AI execution is not enabled on this instance. Saving a
connection sends no provider request and starts no monitor.
Your connections
Scoped keys and explicit model permissions.
No saved connections. Add one here or use the CLI with a
private key file.
Request accounting
No recorded AI requests in the last 31 UTC days.
AI request accounting by UTC day
UTC day
Requests
Accounted tokens
The same settings from your terminal
Keep non-secret configuration in connection.json and the
provider key in a private file. Local E2E projects can use
their own provider configuration without a Waitcher account.
After an uncertain write, refresh and inspect the connection
revision before retrying. Keys are cleared from the form after
submission and when you leave this screen.
Use a dedicated test account for one verified origin and
project/environment. Stored state is write-only to this service;
your selected script can access its session. Pages may appear in
private evidence and, when AI is enabled, reach your selected
provider. Saving an identity starts no monitor.
Browser identities are not enabled for this account.
Saved identities
Metadata only. Enable an identity explicitly, then bind its
current revision to a browser monitor.
HTTP targets are unavailable in this workspace.
Verify a target origin
Add a public HTTPS origin on port 443. Publish its proof, then
choose Verify origin. Creating or editing settings never
contacts the target automatically. Keep the proof file
published: active referenced origins renew verification daily;
failed renewals retry at most hourly. Paused or unbound
targets make no background verification requests.
Publish this verification file
Place the file at the exact path above, then choose Verify
origin in the target row. Keep this file published while
monitors use the target. A new proof resets verification
until you verify it again.
Target
Verification
Revision
Actions
Private request credentials
Store a header for one verified origin. Values are write-only.
Rotation changes the credential revision; monitors must
explicitly select the new revision.
Credential
Header
Status
Actions
Sign in to manage your account data.
Applies to your account across all projects.
Endpoint invocation budget
Applies to AI endpoint monitors and authenticated HTTP
requests. Model connection token budgets are separate.
Endpoint execution is held after a backup restore until the
next UTC reset. Restored counters may be incomplete; these
counts do not indicate available capacity.
A slot is reserved before dispatch. Completed and uncertain
dispatches consume one slot each. A proven preflight failure
can release its reservation. Queuing, preview and saving spend
no slots. Exhaustion is a coverage error, not a website
failure.
Per-monitor usage today
Monitor
Daily limit
Charged
Reserved
Completed
Uncertain
Recent UTC days
UTC day
Charged
Completed
Uncertain
Download your data
Export your configuration, monitoring history and retained
evidence with a checksum manifest. Scripts, logs and captures
may contain private information. The archive is not encrypted.
Stored integration keys and authentication tokens are omitted.
Re-enter integration keys when recreating your setup. Ready
downloads expire after 10 minutes. Exports are complete within
the stated size limits or fail explicitly.
Retention
Keep the evidence and history you need. Shortening retention
expires existing unpinned data during cleanup. Increasing
retention cannot recover expired data.
Pinned visual baselines and active work stay protected.
Expired files cannot be restored by increasing retention.
Stored usage includes expired files awaiting cleanup.
Recent activity
Configuration, credential and retention changes. Secret
values never appear here.
Delete account data
Review the account and its data before confirming. Monitoring
stops and account access is revoked after confirmation.
Live data is removed after active work and file cleanup
finish. Retained encrypted backups expire separately, and
restoring one requires the authoritative deletion ledger.
Your external Clerk sign-in identity remains separate.
Deletion finishes after the configured off-host collector
saves and verifies its recovery ledger. This can wait while
the Mac is asleep or offline.
Keep the receipt private. It lets you check progress after
account access is revoked. Save it before confirming
deletion.
Sign in to your own workspace to manage access tokens.
Save your new token
This token is shown once. Store it privately before leaving
this page. Anyone holding it can use the permissions you
chose.
Create access token
Your tokens
Revoke access at any time. Rotation keeps the same
permissions and expiry.
Token
Permissions
Last used · UTC
Expires · UTC
Actions
No tokens yet. Create one for your CLI, CI pipeline or agent.
Token activity
Creation, rotation, revocation and successful authentication.
Repeated authentication is recorded at most once per token per
minute. Up to 1,000 recent events are retained for your
account.
Use it from your terminal
Save the token in a private file. The CLI also accepts it
through stdin; keep it out of command arguments.
Waitcher