Know when the software you depend on changes.
Drift watches ten vendors and checks every change against the ones your code actually calls. When one of them moves, it tells you what it touches on your side, not just that it moved.
Deprecation notices are addressed to everybody. Breakage is personal.
What you can already see
- Vendor changelogs
- Public
- Deprecation emails
- In someone's inbox
- Status pages
- After the fact
- Your dependency list
- package.json
What nothing tells you
- Whether your product uses the part that changed.
- Which files and workflows sit behind it.
- How many customers stop being able to sign up.
The information exists. It is just spread across a vendor's changelog, your codebase and your analytics, and nobody's job is to join those three together on a Tuesday morning.
One change, followed until it reaches a person.
Drift does not stop at “Twilio changed something”. It keeps going until the answer is a number of customers and a date.
- Vendor
Twilio
Messaging API v3 · deprecation notice
- Service
Notifications
apps/api/notifications · 2 production deploys
- Workflow
Onboarding · checkout
verify a number at sign-up · confirm it at checkout
- Code
3 files
sendVerification · retryQueue · webhook handler
- Customers
356 accounts
customers on the onboarding and checkout workflows
Tracing…
Most vendor changes are harmless. Two of these are not.
A monitor that shouts at everything gets muted. Drift ranks by whether your product is actually exposed, and says plainly when nothing is.
7
Changed in 30 days
2
Need action
5
Recorded, no action
- TwilioMessagingVerification API v3 deprecatedAction needed4h
- OpenRouterModelsA model your code names is withdrawnAction needed2d
- OpenAIModelsCached input pricing down 18%Price down · recorded3d
- AnthropicMessagesNew extended cache tierReviewed5d
- StripeBillingField added to invoice line itemsReviewed8d
- SupabaseAuthSession cookie default changedReviewed11d
- ResendSendRate limit raised to 100/sNo impact14d
- PostmarkEmail APINothing in the last 30 daysNo change—
A deprecation notice is not a decision. This is.
- ARR at stake
- —
- Customers
- 356
- Margin
- —
- Contracts
- —
- Claims
- —
- Engineering
- Half a day
- Risk
- Medium
Drift answers the rows it can see. The blank ones are not missing data — they are outside what this system reads.
Twilio retires the messaging API on 14 November. Drift finds the three files, the two workflows that call it and the customers on those workflows, and estimates the migration at half a day of work.
That is a complete dependency answer, and it is still only half of one. The workflows in question are onboarding and checkout, so the real exposure is not a user count — it is that nobody new can join until it is done. Preflight is what turns the first sentence into the second.
2 workflows
Every new signup
From a changelog entry to a migration plan.
- 01
Watch
Changelogs, model lists, SDK releases, docs and pricing pages for the vendors your code calls.
- 02
Diff
Nogu compares what changed against the surface your code actually calls, not the vendor's whole API.
- 03
Trace
Affected services, files and workflows, with the customer volume standing behind each one.
- 04
Migrate
The exact call sites, the steps and an effort estimate — handed to Patch when you want a draft pull request.
10 vendors watched today
Drift reads these vendors’ public changelogs, model lists, releases and pricing pages every six hours, with nothing to connect. GitHub is what tells it which of them your code calls.
Model inference
- Anthropic
- OpenAI
Model routing
- OpenRouter (available today)
Payments and revenue
- Stripe
Source control and code access
- GitHub (available today)
Transactional email
- Postmark
- Resend
Messaging
- Twilio
Database and auth
- Supabase
Edge and networking
- Cloudflare
Find out what is already about to break.
Connect GitHub and Drift indexes which vendors your code calls, and where. The first poll sets a baseline; every change after it is traced to your code.