Agents write code.
Bumpkit decides what ships.
Every change checked, every release decided, everything proven after.
60 free release checks a month, no card needed.
- Pull request #479, version 1.4.1: shipped. On time, no findings.
- Pull request #481, version 1.5.0: on hold. Breaking change waits for a human who didn’t write it.
- Pull request #482, version 2.0.0: blocked. Live secret key in config/billing.go line 12.
- Pull request #485, version 2.0.1: checking. Agent-written, reading 8 checkers.
Four questions. Zero guesswork.
Every release has to answer them. Bumpkit does, with proof from your code. Each capability below is in early access: ask from its page in your dashboard, and we email you when it's on.
- What will this change break?What a change removes, breaks or affectsPlatform 2
- Is it safe to ship?Your rules, your approvals, your hotfixesPlatform 3
- Who or what made it, and was that allowed?Agents, approvals, a record auditors trustPlatform 7
- Did it break production?Errors, the likely cause, the rollbackPlatform 6
What will this change break?
Bumpkit reads the code in 15 languages and finds every place a change reaches, down to the file and line.
What you see
A plain-English check on every pull request, before anyone hits merge.
How it worksMore: API contract checks · Code quality · Other repositories · Confidence score · Supported languages
Removing Session.Token hits 12 places across billing, checkout, auth and more. Each dot shows what the gate does about it.
- Needs approval
- Needs review
- For information
Is it safe to ship?
Bumpkit applies your rules. When it matters, a human signs off.
What you see
Your rules live in one file in your repo. With the GitHub App, the gate reads that file from the base branch, so no pull request gets to rewrite the rules it's judged by.
How it worksgate: block_on: [secret, data_loss] require_approval: - breaking: true when: agent - area: [billing, authentication] when: always freezes: - name: year-end start: 2026-12-20 end: 2027-01-04 mode: approve
Can this fix go out right now?
Yes, after a quick check. And Bumpkit makes sure every future release still has it.
$ bumpkit contains 3f2a9c1 3f2a9c1 fix: null pointer in checkout REF HOW v2.0.1 contains release/1.9 cherry-picked $ bumpkit hotfix version v2.0.2
Is the release ready to ship?
Bumpkit checks every change in a release batch, the pull requests that ship together as one version.
What you see
One view of the release: what's ready and what's still waiting on a human.
How it worksMore: Release notes
- #481ready
- #485ready
- #482uncoupled · waiting for approval · breaking change
Did it break production?
Bumpkit compares errors before and after the release, pins down the likely cause, and lines up the rollback.
What you see
The release, the likely culprit, and a rollback ready to approve.
How it worksMore: Roll back a release
- Release v2.0.0 arrived and is delayed: more errors since this release, a nil pointer in session.Token.
- Most likely cause: commit 9c1e4ab from #482, auth/session.go line 42.
- Rollback plan: revert 9c1e4ab. Applies cleanly, waiting for an owner.
From the error to the commit behind it to the fix.
Will your agents step on each other?
Not with Bumpkit. Agents claim what they will change and hear about clashes before they write a line.
What you see
Agents coordinate through Bumpkit before they write code. Works with Claude Code, Cursor, Codex and any MCP client.
How it works-
$ bumpkit claim migrationnext migration this agent · claimed -
$ bumpkit intent --paths billing/charge.gobilling/charge.go cursor/refundsthis agent · waiting -
$ bumpkit merge-planmerge order 1 #4902 #4823 #488
Can you prove it to an auditor?
Yes. Every release gets a hash-chained record of who wrote it and who approved it.
What you see
One record per release, chained so no one can quietly edit it, and exported as a signed bundle for your auditor. Stream it to your SIEM, or open change tickets in Jira or ServiceNow.
How it works{ "version": "2.0.0", "agents": ["claude"], "outcome": "needs_approval", "rules": ["breaking, when: agent: needs_approval"], "approvers": ["dana"], "hash": "9f2c…" }
Integrations marketplace
Turn on apps from the marketplace in your dashboard. Integrations are included in every plan. Most are in early access; the ones marked Available now are on today.
Apps
- SlackAvailable now
- DiscordAvailable now
- PostHogAvailable now
- LinearAvailable now
- GitHub
- GitLab
- Bitbucket
- Azure DevOps
- Sentry
- Jira
- ServiceNow
- Claude
- Cursor
- Microsoft Teams
- Datadog
- PagerDuty
- Vanta
- Drata
Built into Bumpkit
- MCPAvailable now
- WebhooksAvailable now
- Git hooks
- Deploy events
- CI and code scanning
- Audit log streaming
Will it pass your security review?
Single sign-on, provisioning, roles, a full audit trail and control over what Bumpkit keeps.
What you get
The controls your security team asks about on the first call. Built in, turned on per workspace.
How it worksMore: Compliance evidence · Data handling
any standard OIDC or SAML 2.0 identity provider
people come and go with your directory
every decision, approval and admin change
read-only access for your auditor
findings only or nothing at all; export or delete any time
Pay per check. Re-runs are free.
1 credit = 1 release check = $0.10. Re-runs of the same commit are free. Every workspace gets 60 free credits each calendar month (UTC), no card needed. No seats, no repository limits.
| Free $0 60 credits a month | Credits $0.10 per check, prepaid | Enterprise Custom annual contract | |
|---|---|---|---|
| Release checks | 60 a month | Prepaid packs | Custom volume |
| Re-runs of the same commit | Free | Free | Free |
| Repositories and teammates | Unlimited | Unlimited | Unlimited |
| SSO, SCIM, SIEM, signed evidence, auditor access | Not included | Not included | Included |
| Start freeOpen dashboard | Contact us | Talk to us |
Let agents write the code. Know what ships, and what it did.
60 free credits every month. $0.10 a check after that. No seats, no repository limits.