SOURCE MONITORING
Monitor official sources
Connect changelogs, API docs, and SDK releases once. Croze continuously detects new provider changes.
Customer migration infrastructure
Ship v2.Keep every customer.
Croze keeps customer code aligned with every API release—automatically identify affected integrations, apply updates, run tests, and open review-ready pull requests.
THE MISSING DELIVERY LAYER
A changelog tells customers what changed.Croze changes the code.
API providers already know what customers need to change. Customer repositories already contain the context needed to apply it. Croze connects the two.
One confirmed release becomes a version-aware migration campaign, carrying only the relevant changes to each eligible integration.
EXECUTABLE CHANGE LEDGER
Official intent.Ready to run.
Croze monitors your changelog, docs, and SDK releases, then turns every confirmed change into a versioned migration contract.
ACMEPAY / CHANGE LEDGERChanges
3 need reviewVersionChangeDetectabilityStatus
v2.0.0amount_cents replaced by MoneyCompilerConfirmedv2.0.0refund.completed finalizes refundsBehaviorConfirmedv1.9.1Refund completion becomes asynchronousManualConfirmedv1.9.0payment.succeeded status requiredPartialConfirmedTHE PROVIDER CONTROL PLANE
One release.Every affected codebase.
Configure the official migration once. Croze targets customers by installed SDK version and tracks every repository from queued to verified.
ACMEPAY / CAMPAIGNSAcmePay API v2
LIVESDK MIGRATION
Runningv1.8.x → v2.0.0
97Targeted
→1Migrating
→1Verified
→0Complete
Customer / repositoryMigrationVerification
Northstarcheckout-serviceVerifiedAll checks passed
Juniperbilling-workerMigratingRunning checks
Orbitmerchant-platformQueuedWaiting
PROVIDER-APPROVED MIGRATION SPEC
Encode the fix once.Reuse it safely.
Turn official API intent into a precise, versioned transform with detection rules, code changes, and verification requirements.
ACMEPAY / MIGRATION SPECamount_cents → Money
CONFIRMEDAPPLIES TO
TypeScript SDK v1.8.x–v1.9.x
Derived from the provider-confirmed API and SDK contract.
✓Detection rule✓Code transform✓Verification plan
−amount_cents: total,+money: { amount: total, currency: "USD" }, confirm: true,ONE CONTINUOUS WORKFLOW
From official release to verified customer rollout.
The provider supplies intent. Croze supplies the migration infrastructure. Customers keep control of their repositories.
CHANGE LEDGER
Confirm the migration contract
A machine-drafted change enters the ledger with source evidence, detectability, and a provider-reviewed migration spec.
VERSION-AWARE CAMPAIGNS
Target the right customers
Repository lockfiles determine each starting version, so every customer receives only the changes in their upgrade interval.
REPOSITORY VERIFICATION
Validate in each repository
The GitHub App applies the migration in an isolated branch, runs the repository’s checks, and returns the evidence.
CUSTOMER-CONTROLLED BY DESIGN
The provider defines the fix.The customer controls the merge.
Selected repositories only
Customers choose exactly which repositories the GitHub App can access.
No automatic merges
Every delivered change stays under the customer’s existing review and merge policy.
A complete audit trail
Every rollout records the source, migration version, repository checks, and final outcome.
Provider update→Croze migration→Repository verification→Customer approval
YOUR NEXT RELEASE
Stop announcing migrations.Start delivering them.
See an API change move from provider intent to a verified customer rollout.