Know when the software you depend on changes.
Your product runs on dozens of APIs you don't control. Drift watches them, and when something moves it tells you what it touches on your side — not 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
sign up → verify number → activate
- Code
3 files
sendVerification · retryQueue · webhook handler
- Customers
4,810 users
verified a number in the last 30 days
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
2
Worth taking
- TwilioMessagingVerification API v3 deprecatedAction needed4h
- VercelBuild imageNode 22 becomes the default runtimeAction needed2d
- OpenAIModelsCached input pricing down 18%Opportunity3d
- AnthropicMessagesNew extended cache tierOpportunity5d
- StripeBillingField added to invoice line itemsReviewed8d
- SupabaseAuthSession cookie default changedReviewed11d
- ResendSendRate limit raised to 100/sNo impact14d
- AWSS3Nothing in the last 30 daysNo change—
A deprecation notice is not a decision. This is.
- ARR at stake
- —
- Customers
- 6,014 users
- Margin
- +$4.1K / yr
- Contracts
- 0
- Claims
- 0
- Engineering
- ~4.5 hours
- 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 and the 6,014 people who verified a number through them in the last month, and estimates four and a half hours 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.
6,014 users
Every new signup
From a changelog entry to a pull request.
- 01
Watch
API schemas, SDK releases, docs, pricing pages and terms for every vendor in your dependency graph.
- 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
A proposed change with the incompatibilities called out. Eventually, a pull request you review.
10 vendors watched today
Anthropic, OpenAI, OpenRouter, Stripe, GitHub can be connected today. The rest are sources the model is built for and cannot be connected yet — the app never offers a provider whose consent flow it cannot complete.
Model inference
- Anthropic — can be connected today
- OpenAI — can be connected today
Model routing
- OpenRouter — can be connected today
Payments and revenue
- Stripe — can be connected today
Source control and code access
- GitHub — can be connected 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 maps your dependency graph in minutes. The first report usually contains at least one change nobody had noticed.