Connect, install, understand.
How to connect each provider, what Keelnest checks, and how to fix what breaks. Each connection takes a few minutes and can be revoked at the provider.
Start here
- What Keelnest checksThe five-minute check, what every HTTP status means for your visitors, the guards on top, and how long each observation is kept.Read it
- What breaks, and the fix30 failures that reach an AI-built app after launch, each with how to tell, the fix, and a prompt for your builder.Read it
- Error captureOne dependency or one script tag, and an incident says what broke — in Next.js, Node, Vite, Astro or Cloudflare Workers.Read it
- The Keelnest badgeA “Watched by Keelnest” badge for your footer or README, with the site’s state and its uptime over 30 days — and nothing else.Read it
Integrations
Each connection feeds one guard, or is read only when a key leaks. What it reads, what it never does, and how to make the credential, one page each.
Money
Payments against a learned baseline, webhook health, checkout evidence.
Backend
Database and auth health, config drift, security advisors, whether auth email can be delivered.
Spend
AI and hosting usage against budgets, spike alerts.
Errors
Runtime errors so incidents say what broke.
Code
What changed in each publish, and later, repairs.
Leaked keys
Read only when one of the account's keys is found in an app's public code. It feeds no guard.
Also worth reading: what each connection can read, every tier compared, and the free health check for any public address.
May we use Google Analytics to see which pages help? No advertising cookies either way. Privacy