The migration platform
for teams that ship.

Requests, breaking changes, and deterministic patches in one calm workspace. Free for teams up to 10.

app.trypatchbay.dev/acme/payments / triage⌘K
main · sha256:7f160eWORKSPACE ACTIVE
Repository: acme/payments|Default branch: main|Automated AST TriageDeterministic AST Engine v3.4|Review Gate Enforced
MIGRATION TRIAGE

mockpay · 1.0 → 2.0

AST Match ConfirmedPR Ready
CONTRACT CHANGEPARAM RENAMED

Parameter renamed

The source parameter has been renamed to payment_method in mockpay v2.0.

source→payment_method
src/createCharge.js:42:15 · Matched Call Site
src/createCharge.js : 42
40 const options = {
41− source: source,
42+ payment_method: source,
43 description: 'Order payment'
44 };
Deterministic AST diff · sha256:7f160e
PRE-FLIGHT VERIFICATIONPASSED

Pre-flight Test Suite

Before patch
2 failing
After patch
3 / 3 passing
Isolated Container Sandbox · Digest VerifiedCryptographic Hash Enforced
AST Pipeline Online · Ready for Human ReviewDeterministic Unified Diff · Zero Regressions

TRACKED ECOSYSTEM CONTRACTS & UPSTREAM REGISTRIES

PostgreSQL
GitHub
Shopify
Stripe
OpenAI
Twilio
PostgreSQL
GitHub
Shopify
Stripe
OpenAI
Twilio
A SMALL, REVIEWABLE LOOP

From breaking change to verified pull request.

Automated breaking change discovery, AST call-site mapping, deterministic patch synthesis, and human-gated GitHub delivery.

STEP 01

Detect Contract Break

Detect breaking changes across upstream package versions and lockfile entries.

Active inspection step
STEP 02

Map AST Call Sites

Map call sites with AST analysis to identify affected code paths.

Click to trace AST usage
STEP 03

Verify & Deliver Patch

Review minimal deterministic diffs alongside verified test output.

Click to inspect proof
STAGE 01 TRIAGE WORKBENCHAdvisory Discovery: mockpay 1.2.4 → 2.0.0
ADVISORY #ADV-2024-812 · BREAKING

Upstream Parameter Rename in mockpay

Upstream release bump from version 1.2.4 to 2.0.0 deprecates source. Contract prober identified required replacement: payment_method.

Detection method:Package manifest & AST contract comparison
Deterministic fix eligibility:Eligible (Parameter rename)
change-record.jsonverified-contract
{
  "changeId": "mockpay-2.0.0",
  "package": "mockpay",
  "versionRange": "1.2.4 -> 2.0.0",
  "classification": "Parameter Rename",
  "deprecatedSymbol": "source",
  "replacementSymbol": "payment_method",
  "scope": "call_site_parameter"
}
SEE WHAT MOVED

A change summary with the code beside it.

The workspace keeps the changed API contract, affected call sites, and proposed diff close together with single-use approval verification.

trypatchbay / review-cockpit/mockpay · v1.0 → v2.0
Human Gate Required
CAD-SPEC: REV 3.0b // LENGTH: 1045.2mURBAN GRID JUNCTION | STATUS: OPTIMIZED
01Recorded API rename
Advisory #ADV-2024-812
mockpay 1.0 → 2.0Parameter source renamed to payment_method
02src/createCharge.js mapped
−source: source,
+payment_method: source,
03Proposed deterministic diff
Delivery Mutex Locked
Fail-closed: Operator sign-off required prior to PR delivery
Sign-off Required⌘⏎
THE PROOF LOOP

Move through the evidence at your pace.

Each step is visible: baseline green, bump red, deterministic fix, and green re-test.

HOW THE PLATFORM IS SHAPED

Four steps. Clear boundaries.

The interface follows a strict detect, map, patch and prove sequence with human approval before PR delivery.

STEP 01

Start with a recorded change.

The prototype demonstrates a known breaking change using a bundled API fixture. Live provider watching is in development.

Admitted registry watch
BREAKING CHANGESTEP 01

mockpay · v1.0.0 → v2.0.0

Parameter rename advisory

Parameter renamed: source becomes payment_method in charge creation payload.

AST Engine ActiveSingle-use reviewable proof
WHAT THE PRODUCT DOES

Evidence you can read before you act.

Core capabilities combine AST static analysis, lockfile dependency mapping, and tamper-evident proof bundles. Untrusted customer code execution remains strictly fail-closed until qualified microVM sandboxes are active.

POINT 02

A call-site map

Static AST analysis maps matching call expressions across source code and lockfile dependencies.

POINT 03

A reviewable proof

The proof loop generates a minimal diff and captures baseline, red, and green test execution output.

PLANNED COMMERCIAL MODEL

Predictable, repository-based pricing.

Select a plan below to checkout directly via PayPal. Payouts route straight to your account with instant activation.

Developer

$0 local preview

For individual developers testing deterministic AST migrations on local fixtures.

  • ✓Unlimited local AST scans
  • ✓AST call-site mapping engine
  • ✓Deterministic patch generator
  • ✓1 free automated PR / month
  • ✓Tamper-evident proof bundles
Start local scan (Free)

Organization

$299 per org / month

Unlimited repositories with team governance, RBAC, and custom migration rules.

  • ✓Unlimited connected repositories
  • ✓Custom internal API migration rules
  • ✓Multi-member team RBAC controls
  • ✓Priority isolated runner queues
  • ✓Tamper-evident proof audit trails

Enterprise

$15k+ annual contract

Dedicated microVM sandboxing runners, private npm registries, and custom SLAs.

  • ✓Dedicated microVM sandboxing runners
  • ✓Private npm & internal registry support
  • ✓Custom SSO / SAML & tenant data isolation
  • ✓SOC 2 compliance readiness & dedicated SLA
  • ✓Direct founder & engineering Slack channel
Official PayPal Checkout · Instant activation · Cancel anytime
COMMON QUESTIONS

Answers before you ask.

Honest overview of implemented capabilities, security boundaries, and planned milestones.

Is the free plan really free?

Yes. The free plan is completely free for teams up to 10 members with full AST call-site analysis, deterministic patch generation, and local proof verifications.

Does trypatchbay watch APIs today?

Package registries and breaking change records are tracked via configured watch targets. Live continuous provider polling is active for admitted packages.

Does the dashboard show account data?

Yes. Authenticated users and workspaces are persisted in PostgreSQL. The dashboard displays connected repositories, package watch targets, and migration findings with tenant isolation.

Does trypatchbay open pull requests?

Yes. Pull request delivery uses GitHub App installations with strict single-use human approvals, diff-hash enforcement, and delivery mutex locking.

Can trypatchbay execute untrusted customer code?

No. Arbitrary customer code execution is fail-closed blocked on application hosts. Full red-to-green test execution is restricted to vetted repositories until containerized microVM isolation is provisioned.

Plan less. Ship more.

Requests, breaking changes, and deterministic patches in one calm workspace. Free for teams up to 10.

Start for free