Busleyden Guard

AI pull request safety gate

Know what an AI code change can break before you merge it.

Busleyden Guard reviews pull requests, finds risky change surfaces, maps proof that should exist, and posts a GitHub check your team can act on.

Install GitHub App Request pilot
Runs where work happens
GitHub PR checks
Designed for
AI-heavy teams
Default posture
No source storage
GitHub Check

Change Consequence Gate

proof needed
Risk surface
Auth session, dependency lockfile, API middleware
Required proof
Session regression test, owner approval, scanner evidence
Reviewer route
@platform-review and @appsec-review
Merge guidance
Hold until missing proof is attached

The problem

AI makes code faster. It also makes review uncertainty explode.

Teams are merging more generated code, but reviewers still need to answer the same hard question: what changed, who owns the risk, and what proof is missing?

Hidden blast radius
Small-looking diffs can touch auth, payments, permissions, model loading, or CI secrets.
Review bottlenecks
Senior engineers spend time reconstructing context instead of making merge decisions.
Weak proof
Green tests do not always prove the risky behavior was tested.
No audit trail
After merge, it is hard to show why a risky AI change was accepted.

How it works

A guardrail your developers do not need to learn.

1

Open a PR

Busleyden Guard receives the pull request event from GitHub.

2

Analyze the change

It identifies risky surfaces and the evidence a reviewer should expect.

3

Post a check

The PR gets clear merge guidance: safe, proof needed, or blocked.

4

Keep the trail

Teams can review what was known before the merge decision.

Security posture

Built to be easy to approve.

Busleyden Guard starts with narrow GitHub permissions and a simple operating model. The app reads pull request metadata and changed files, then posts checks back to GitHub.

Security summary Data handling
Permissions
Checks, PRs, contents read
Default data model
No customer source storage
Install scope
Choose repositories

Pilot offer

Start with one repository and real pull requests.

The first pilot is designed to prove whether Busleyden Guard changes review decisions in your actual workflow before a broader rollout.

Founding pilot

$99

  • One GitHub repository
  • 30 days of PR gate checks
  • Self-service GitHub App setup
  • Founding-customer pricing while the product is young
Start with $99

Pilot fit

Tell us where AI code review is starting to hurt.

Share a few details and we will tell you whether Busleyden Guard is a good fit for your current engineering workflow.

Current stack

Decision artifact

The buyer-facing artifact is the AI Change Consequence Certificate.

It is built for one practical question: should this AI-assisted pull request merge now, wait for proof, or route to the right owner? The sales gate is met only when a real customer pays or records approval. Do not buy on a 1000x total-throughput claim; our public 3821.9354x proof is a bounded fanout result, not a promise that all engineering work becomes 1000x faster.

Sample certificate

What a reviewer gets before merging

Certificate ID
sample-auth-session-001
Policy status
attention_required
Reviewer action
Block merge until auth regression proof and scanner evidence are attached.
Decision
Block merge
Open sample certificate Open pilot scope

Fit calculator

Conservative payback calculator

Estimate only review-decision value. This ignores broad productivity claims and focuses on avoided review uncertainty.

Monthly review-decision risk
$0
Estimated monthly value
$0
Pilot payback
n/a
Break-even volume
n/a

Try the artifact

Generate a browser-only certificate preview

This demo shows certificate shape only. Real evidence comes from a repository install and real pull requests.

Attached evidence

Tighten session token validation

Status
attention_required
Changed surface
3 files
Owner route
@platform-review + @appsec-review
Affected tests
src/auth/test_session.py
Scanner evidence
Semgrep missing, OSV missing
Reviewer action
Block merge
Claim boundary
This browser demo previews certificate shape only and is not customer evidence.

Self-service pilot

Everything a buyer needs without talking to sales.

Start self-service $99 pilot, inspect the scope, forward the security notes, install the workflow, and keep the kickoff plan visible.

Download procurement brief Open data addendum

After approval
The first day is already scripted in the kickoff plan.
Forwardable answers for procurement and AppSec
Security, data handling, scope, and install artifacts are public.
Install path
GitHub App plus workflow file, scoped to one repository.
Self-service pilot Order form Kickoff plan Security review Install guide Workflow file

Approval evidence

Record budget-owner approval

Use this when a buyer has approved payment or signed written approval outside Stripe. Reconcile it with the approver before treating it as paid evidence.

Pilot feedback

Tell us whether the certificate changed a review decision.

This is how we keep the offer honest: a pilot is useful only if real reviewers say the artifact made review faster or safer.

Observed value

Not ready to buy?

Tell us the exact blocker.

If the $99 pilot is still not easy to buy, the blocker is product evidence. Tell us what must be true before you reconsider.