Alert speed
Fast alerts, framed honestly
SpotSitter is designed around frequent checks and multi-channel alerts, but speed depends on the configured cadence, delivery providers, device settings, and how quickly you act after the alert arrives.
Paid launch cadence
60s
Configured target check interval for paid watches before production SLI proof is published.
Free launch cadence
120s
Configured target check interval for Free watches before production SLI proof is published.
Founder receipt
52 hours
Mother's Day 2026 Cake Bake Shop watch ran 2,395 checks before the catch.
Launch cadence versus guaranteed performance
Paid watches are configured around a 60-second target check cadence, and Free watches are configured around a 120-second target check cadence. Those are launch targets, not a guarantee that every alert will be delivered, opened, or booked inside a fixed window.
Production p50 and p95 performance should be published only after the production cadence and service-level evidence are available. Until then, speed copy should remain framed as design intent and configured cadence.
What can affect delivery
Alert delivery can be affected by SMS carrier filtering, push-notification permissions, email filtering, Discord webhook health, device connectivity, Disney site behavior, and user response time.
SpotSitter can detect and send an alert, but it cannot control whether a carrier delays a text, whether a browser allows push notifications, whether an email lands in a filtered folder, or whether the opening remains available while you book.
The founder receipt
The original founder proof was a Mother's Day 2026 Cake Bake Shop reservation watch. It ran for 52 hours, made 2,395 checks, caught the opening on Friday at 4:51 PM, and the confirmation email arrived nine seconds after the alert.
That receipt is useful evidence that the workflow can work. It is not a promise that every future watch will catch every opening or produce the same booking outcome.
Related transparency pages