NEW Now watching Shopify Scripts retirement Jun 30, 2026

Catch vendor API changes before
before your customers do.

Vendor Pulse watches the changelogs you can’t — Shopify, Stripe, OpenAI, GitHub GraphQL, Google Ads — maps every change to the exact files in your repos, and drafts a code-aware ticket with evidence, owner, and a remediation plan. No more dashboards. No more 3am incident calls.

Start watching free See how it works
No credit card.  2 vendors free forever.
vendorpulse.app / workspace / acme-corpLIVE

1·INGEST

Upstream changelogs, normalised
Shopify
Scripts fully retire Jun 30
2m
OpenAI
gpt-4-turbo deprecation
14m
Stripe
Checkout Sessions v2 beta
1h
GitHub
GraphQL field added
3h

2·MATCH

Code evidence from your repos
vendor Shopify
notice Scripts retirement
matches 5

apps/checkout/scripts/shipping_discount.rb
apps/checkout/scripts/loyalty_tier.rb
package.json@shopify/shopify-api 11.4.0
CODEOWNERS → @commerce-platform

severity breaking_high
confidence 0.94

3·TICKET

Drafted in Jira or GitHub Issues
[ACTION REQUIRED] CHK-1482 · drafted just now
Migrate Shopify Scripts to Functions before Jun 30

2 active scripts match. Editing is already blocked (Apr 15); execution halts at deadline. Remediation plan and test cases attached.

@commerce-platform due Jun 15 P0 5 evidence items
24h ago 18h 12h 6h now
Watching changelogs from
Shopify stripe OpenAI Anthropic GitHub Google Ads Twilio Meta
The problem

Vendors ship breaking changes every week.

You find out in one of three ways: a customer complaint, a production error, or a tab you forgot to read. The upstream signal exists — RSS, release notes, deprecation pages, scheduled cutovers — but the jump from “a change happened” to “this repo is affected and here’s the ticket” is still a manual slog nobody owns.

Silent deprecations

OpenAI quietly sunsets gpt-4-turbo. Your eval job explodes Tuesday morning.

Scheduled cutovers

Shopify Scripts retire Jun 30, 2026. Your agency has 14 clients running two scripts each.

Contract drift

Stripe adds a nullable field to a response. Your parser silently drops an event. Six weeks later, reconciliation calls.

How it works

From upstream change to assignable ticket — in under a minute.

Step 1 of 4

ingest
01 Ingest

Watch every changelog, normalize into one schema.

RSS, HTML, release-note pages, deprecation notices — polled on a schedule with dedupe. We turn heterogeneous posts into a single event stream with vendor, product, dates, change type, severity hints, and the original source URL.

02 Match

Find the exact files affected — or say nothing.

A GitHub App with read-only repo access indexes your integration surface: SDK versions, endpoint strings, env vars, GraphQL fields, config files. Each vendor notice is matched to concrete evidence. No evidence, no ticket.

03 Classify

Severity with receipts, not vibes.

A closed-world classifier scores each change breaking_high, action_likely, watch, or informational — using your evidence pack only. If confidence is low, we abstain and queue for review.

04 Ticket

Drafted in Jira or GitHub, assigned by CODEOWNERS.

Title, impact summary, evidence with direct file links, a 3–5 step remediation plan, suggested owner, and a due date anchored to the vendor deadline. Auto-create above your confidence threshold, or keep every draft in a triage inbox.

The product

Not another dashboard. An autonomous teammate for vendor risk.

Triage inbox, not a feed

The default screen isn’t a river of updates — it’s a review queue of matched changes with confidence scores and draft tickets. Approve, merge duplicates, suppress, or snooze. Every decision trains the policy engine.

3 breaking 5 action likely 12 watch 28 suppressed by policy

Least-privilege by default

GitHub App with read-only contents, encrypted secrets, tenant isolation, redaction before prompts, audit trail on every ticket action.

permissions:
contents: read
metadata: read
issues: write
— nothing else —

residency: ap-southeast-2
retention: 30d evidence

Historical replay

Onboard and we’ll replay the last 90 days of every vendor you connect. First-run value, before you wait for a single new change.

CODEOWNERS-aware

Tickets route to the squad that actually owns the affected files. No more unassigned bucket, no more Slack paging roulette.

Policy engine

Auto-create above 0.85 confidence for breaking changes. Require human review for everything touching billing. Suppress info-level notices for vendors you don’t care about. Policies are declarative, versioned, and auditable.

when severity = breaking_high and confidence > 0.85
auto_create in jira://billing as P0
when vendor = "Meta" and severity = informational
suppress
Connectors

Every vendor that breaks your weekends.

Plus custom connectors for internal platform teams. Request a vendor →

82%Ticket acceptance rate without heavy edits
<15%False positive rate at default thresholds
30m95th-percentile freshness on monitored feeds
3 minFrom connect-repo to first drafted ticket
We used to find out about Shopify changes when a client emailed us at 11pm. Vendor Pulse turns every changelog post into a ticket with the exact file paths. Friday panic, gone.
Priya Shah Head of Engineering · Coral Commerce (Shopify Plus agency)
Pricing

Priced on repos & vendors, not seats.

The value scales with your integration surface — not how many engineers open the app.

Free
A$0 / forever
See the value before you pay. Dry-run only.
  • 1 repo, 2 vendors
  • Draft tickets, no auto-create
  • 90-day historical replay
  • Community support
Start free
Starter
A$49 / repo / mo
Small team with a handful of critical integrations.
  • 3–5 vendors
  • Jira or GitHub Issues
  • Auto-create above threshold
  • Slack alerts
Start Starter
Agency
A$399 / month
Shared inbox with client-level segregation.
  • Unlimited client repos
  • Per-client policies
  • Australian residency option
  • SSO & audit log
Talk to us
One-off Deprecation Impact Reports from A$299. Great for migration planning before committing to monitoring.
Questions, answered

The boring things
that matter.

What permissions does the GitHub App actually request?+
Read-only contents and metadata, plus issues: write if you pick GitHub Issues as your ticket destination. Nothing else — no write access to code, no PR creation, no workflow permissions. Scope installation to a subset of repos on install.
Do you train on my code?+
No. Source code is never sent to model providers for training and is never used to improve any shared model. We send minimal file-path and structural evidence to the classifier and ticket writer, redact secrets and large code blocks before assembly, and retain that evidence for 30 days by default (configurable per plan).
What happens when a model is unsure?+
It abstains. If confidence is below your threshold or the evidence pack is thin, the change is queued for human review with a note on what’s missing. We’d rather tell you “this needs a person” than invent a ticket.
Which ticket systems do you support?+
Jira Cloud and GitHub Issues at launch. Linear and GitLab are on the expansion roadmap; tell us which you need at signup and we’ll prioritise.
Can I host in Australia?+
Yes — the Agency plan ships with Sydney residency (AWS ap-southeast-2) and a documented subprocessor map. Lower tiers run globally with project-level data controls. We’re happy to walk your security team through the full trust doc.
How is this different from Dependabot or a changelog reader?+
Dependabot watches package manifests — great for versioned SDKs, blind to vendor-side policy changes like Shopify Scripts retirement or a GraphQL field removal. Changelog readers aggregate the firehose. Vendor Pulse sits in the middle: upstream-aware like a reader, repo-aware like Dependabot, ticket-first like neither.
Can I self-host?+
Not today. Enterprise self-hosting is on the roadmap; talk to us if that’s a dealbreaker and we’ll share timelines.

Stop reading changelogs.
Start shipping against them.

Connect a repo, pick two vendors, and Vendor Pulse will have its first draft ticket ready in under three minutes. Free forever on one repo — no credit card, no demo call.

Vendor Pulse

Review Inbox

DRY RUN Auto-refresh 30s
total
breaking
action likely
watch
needs review
informational
Status
Severity
Vendor
Loading…