Name: Updrift
Brand: Updrift

Drift detection

Find where provider APIs contradict your code.

Stripe says one thing in OpenAPI. Your handlers still do another. Updrift catches the contradiction before renewals go quiet.

app.updrift.dev/reports/drift

Updrift

Pro

Drift report · acme-corp/payments-api

3 drifts found

Provider shipped

stripe OpenAPI · 2026-04-15

Webhook.construct_event(payload, sig, secret)

changelog · silent

outcome.type always string for EU

Your code still does

billing/webhooks.py:47

Old verify call. No tolerance / api_version.

invoices/export.ts:88

Assumes outcome.type is never null

41 Stripe usages · 3 silent breaking3 need fixes

app.updrift.dev/connections

Updrift

Pro

Connections

Link your repos and the providers you ship on.

acme-corp/payments-api
GitHub · main · 847 files · pushed 2h ago
✓ Connected
acme-corp/billing-web
GitHub · main · 312 files · pushed 5h ago
✓ Connected
Stripe
Live catalog · OpenAPI + changelog · synced 6m ago
✓ Connected
Notion · Eng runbooks
Beta · 124 pages · synced 10m ago
✓ Connected

4 sources connected · 1,159 files indexedAll synced

How it works

Three steps before the silent break.

Use cases

How teams use Updrift.

Ship Stripe changes without a 2am pager.

Every OpenAPI shift that hits your webhooks and renewals shows up as an evidence-backed finding before customers feel it.

Payments teams

Ship Stripe changes without a 2am pager.

Every OpenAPI shift that hits your webhooks and renewals shows up as an evidence-backed finding before customers feel it.

0silent breaks in prod

The semantic change engine

We read meaning, not diffs

Renaming a field is easy. The changes that take payments down are semantic, and a lot of them never show up in a changelog. We read Stripe's OpenAPI, docs, SDKs, and deprecation headers, then spell out what each change does to your handlers.

What monitoring tools tell you

"Stripe released API version 2026-04-15"

"18 endpoints changed"

"See changelog for details"

"3 fields deprecated"

What Updrift tells you

Auth flow changed: your webhook signature check breaks in 3 handlers

Retry semantics changed: your idempotency keys collide on refund retries

Pagination changed: your invoice export quietly drops everything past page 1

Undocumented: `outcome.type` is null for EU accounts. 7 call sites hit.

Roadmap · runtime drift

Version drift is only half of it

APIs also change how they behave without bumping a version. Latency jumps. Webhooks arrive out of order. A field goes null for one region. Nothing lands in the changelog. Next up: watch how providers actually behave in the wild.

09:14stripe /v1/charges p99 latency +340ms vs 7-day baseline

09:31webhook `invoice.paid` arriving out of order (12 events)

10:02`outcome.type` returning null for EU accounts · undocumented

10:15rate limit ceiling lowered · 429s at 82/s, was 100/s

The pipeline

No PR ships without proof

Watch, understand, map, migrate, replay, then PR. If the sandbox can't prove the fix, you get a written report instead of a guessed pull request. We do not guess with your payments code.

Watch

Specs, docs, SDKs, headers, behavior. Diffed daily.

Understand

Figure out what changed and why it matters to your code.

Map

Pinpoint the endpoints, handlers, retries, and middleware hit.

Migrate

Write the migration: code, tests, docs, comments.

Replay

Stripe sandbox: fails before the fix, passes after.

Plain-English summary. You review. You merge.

Proof gate

Same path as pnpm moat:demo

Scan, finding, fail/pass replay, then PR

Skewed webhook signatures have to fail before the migration and pass after. Old-format traffic still has to pass. Only then do we set proved=true.

01
Scan
Fixture repo with real Stripe webhook usage
02
Finding
webhook_verification_changed shows up as silent breaking
03
Replay
Sandbox matrix: skewed signature fails before, passes after
04
PR
Migration branch with tests. You review. You merge.

Integrations

Connects where your code and payments already live.

Stripe and GitHub are live. Razorpay and Notion are in beta. Everything else is on request. Every tile carries LIVE, BETA, or ON REQUEST.

StripeLIVE

GitHubLIVE

RazorpayBETA

NotionBETA

GitLabON REQUEST

BitbucketON REQUEST

ConfluenceON REQUEST

GitBookON REQUEST

MintlifyON REQUEST

CashfreeON REQUEST

JuspayON REQUEST

PhonePeON REQUEST

SetuON REQUEST

ChargebeeON REQUEST

HasuraON REQUEST

PostmanON REQUEST

ZohoON REQUEST

FreshworksON REQUEST

Trust & security

Your code never leaves your control.

Updrift analyzes in flight, then discards the clone. Secrets stay sealed. Payments teams get specifics, not slogans.

Zero data retentionShallow clone, analyze, delete. Customer source is not kept after the scan and never used for training.

SOC 2 in progressControls are designed. Audit logging from day one. Type II audit is not complete yet, and we say so.

Encrypted in transitTLS for HTTPS and Postgres. Installation tokens and webhooks sealed at rest with libsodium.

Read-only by defaultGitHub App: Contents and Metadata only. Opening a PR needs a separate opt-in. Never on your default branch by default.

Zero data retentionShallow clone, analyze, delete. Customer source is not kept after the scan and never used for training.

FAQ

Common questions

For public repos we do a shallow clone, analyze it, then delete it. Nothing sticks around after the scan. Private repos use the same model through a read-only GitHub App (Contents and Metadata only). Installation tokens and alert webhooks are sealed at rest with libsodium. We never train on customer source.
No. The free scan is read-only and emails you a drift report. Auto-fix PRs need an org opt-in for write access. Scan and PR write are separate. We never open a PR without sandbox proof and your opt-in.
Dependabot bumps package versions. Updrift watches semantic API drift in the integrations those packages call: field renames, webhook verification changes, silent pagination or retry behavior. We map the exact lines in your repo, and we only open a PR when sandbox replay proves the fix.
You get a written report with file and line evidence. No PR. The gate is hard: proved=true only when the fail-to-pass matrix holds. Otherwise you get the finding, not a guessed migration.
Run npx updrift scan locally (read-only, about 90 seconds, no signup), or paste a public GitHub URL in the free scan form above. You'll get a drift report by email. Sign in later if you want continuous Drift Watch or auto-fix PRs.
Yes. Stripe and GitHub are live. Razorpay and Notion are in beta. GitLab, Bitbucket, Confluence, GitBook, Mintlify, and India-first surfaces (Cashfree, Juspay, PhonePe, Setu, Zoho, Freshworks, Postman, Hasura, Chargebee) are available on request. Every logo in Integrations is tagged LIVE, BETA, or ON REQUEST.

Free Drift Watch scan

What breaks in your repo on the next Stripe version?

Paste a public GitHub URL. We email a drift report covering the lines that break, the deprecations you lean on, and the undocumented bits you're exposed to. Same engine we run in production. No signup. Read-only. Minutes, not days.

Read-only · report in minutes · public repos need no GitHub App

We run this engine against 5 Stripe API versions, 3 ingested pairs, and 3 payment fixtures (Express, Flask, Next). Methodology.

Plans

Plans that scale with how deep you go.

Drift Watch is free forever: monthly report, one repo, breaking-change alerts. Solo, Team, and Business add auto-fix PRs, continuous scans, and unlimited repos. We're onboarding design partners by hand right now.

Drift Watch
Free forever. Monthly report, one repo, breaking-change alerts.
Solo
Auto-fix PRs, sandbox replay, weekly scans.
Team
Continuous scans, Slack, priority queue.
Business
Unlimited repos, audit export, invites.

Talk to us