About the VibeOK bot
VibeOK opens apps in a real Chrome browser to check that signup, login and checkout still work. It only visits apps whose owners added them, plus single page loads that someone requests from our homepage.
How to recognise it
Every request ends its user agent with:
VibeOK/1.0 (+http://localhost:3000/bot)
The full user agent looks like this:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<version> Safari/537.36 VibeOK/1.0 (+http://localhost:3000/bot)
We'll list our IP addresses here before launch. Until then, match on the user agent.
How often it visits
- Each flow runs every 5, 15 or 60 minutes, depending on the owner's plan.
- A failed check is retried once, a few seconds later.
- It never fills in card details. Checkout checks stop once the payment page opens.
Allow it through your firewall
Cloudflare
Security → WAF → Custom rules → Create rule. Match User Agent contains "VibeOK/1.0", action Skip (Bot Fight Mode and managed rules).
Vercel
Firewall → Add rule → If User Agent contains VibeOK/1.0, then Bypass.
CAPTCHA or Turnstile on signup
Bots are meant to fail CAPTCHAs, ours included. Monitor login with a test account that skips the challenge, or check that the signup page loads and the button is there instead of submitting it.
Keep it out of your analytics
Most analytics tools drop headless browsers already. If you see visits, exclude user agents containing VibeOK. In Plausible and Umami that's a filter; in Google Analytics, a data filter or a check before loading the tag: !navigator.userAgent.includes("VibeOK").
Seeing VibeOK on a site you didn't sign up for?
Someone may have added your site by mistake. Email hello@tryvibeok.site with the address and we'll stop the checks.
Back to VibeOK