Sentinel doesn't have a support org behind it - it has one person. This page is an honest inventory of how to get help and what you can actually expect back.
Most questions have a faster answer than an email round-trip. Worth checking first:
Walkthroughs for integrations, deal lifecycle, teams, and webhooks.
Interactive Swagger UI with every endpoint, its params, and response shape.
Every keyboard binding, verified against the source.
What shipped, when - in case your bug was already fixed in a recent release.
Credential scopes, encryption, deletion, and things we deliberately don't do.
No. Sentinel is run by one person, so realtime channels would be closed more often than they were open. Email and GitHub get answered; a phone that goes to voicemail wouldn't.
Not a contractual one. Response targets on this page are what we hit in practice, but we won't promise uptime tiers or credit schedules we can't back up.
We don't run a status page yet. If the app isn't responding, it usually means Vercel, Clerk, or the database provider is having an incident - check their status pages. Outages get logged in the changelog once they're resolved.
Product documentation lives under /docs. The /api-docs page has an interactive Swagger view of the REST API. Keyboard shortcuts are on /shortcuts. Everything else is on /resources.
Paid plans cancel from /settings · Billing. Account deletion (including revocation of integration tokens) is handled from /settings · Account. Email us if anything gets stuck.
That's on me. Nudge the same thread - you won't be annoying. Dropped replies are almost always accidental.
Sentinel is developed in the open. You can watch changes land in real time, open pull requests, or fork it for your own internal tools.