Bug reports, feature requests, existential questions about CI/CD—all welcome.
Email support@deploybar.app I read every email. Response time is typically under 24 hours.Open Settings → Accounts and click Sign in with GitHub. DeployBar uses GitHub’s device flow—no personal access token needed, no scopes to figure out. Just enter the code on GitHub’s site and you’re done. DeployBar auto-discovers repos you push to, so there’s nothing else to configure.
If you prefer a classic PAT, expand “Use Personal Access Token instead” in the settings. You’ll need the repo scope.
Vercel dashboard → Settings → Tokens. Create a token with read access. If you’re monitoring team projects, enter your Team ID or slug in DeployBar’s Vercel settings tab.
In the macOS Keychain, sandboxed to DeployBar. They never leave your machine. You can verify this in Keychain Access or remove them from DeployBar’s settings at any time. See the privacy policy if you want the full explanation, but the short version is: we literally cannot see your tokens.
A deploy failed and you haven’t acknowledged it yet. Open the dropdown, find the failure, and either click the row to see it in your browser or hit the × to dismiss it. The icon stays red on purpose—silent failures are how things end up broken for a week.
Every 15 seconds by default. You can set it anywhere from 15 seconds to 5 minutes in Settings → General. With auto-discover, it makes about 7 API calls per tick (1 for your activity, ~5 for active repos, 1 for Vercel)—about 1,680 requests/hour, well within GitHub’s 5,000/hour limit.
Yes. The device flow OAuth grants access to your private repos automatically. If using a PAT, you need the repo scope. Auto-discover will pick up any private repo you push to.
Your token was revoked, expired, or had its permissions changed. Generate a new one from GitHub or Vercel, paste it into Settings, and DeployBar will resume polling immediately.
No. Zero. The app has no backend, no analytics SDK, no crash reporter. Nothing leaves your Mac except the API requests you configured it to make. The privacy policy is refreshingly short.
macOS 14 Sonoma or later.
Maybe. Tell me which one and how many repos you’d monitor. That’s the most useful signal.