NewPlatform Capabilities

The complete solution for vendor API risk.

From ingest to actionable ticket, every step is designed to minimize noise and maximize action.

82%
ticket acceptance without heavy edits
<15%
false positive rate at default thresholds
30m
95th percentile feed freshness
3 min
connect repo to first drafted ticket
Core capabilities

Built for engineering teams who ship.

We've automated the tedious parts of vendor management so you can focus on code.

Triage inbox, not a feed

Review only matched changes with confidence, owner, and evidence. Approve, merge duplicates, suppress, or snooze in one flow.

  • ✓Prioritized queue sorted by severity and repo impact
  • ✓One-click actions: approve, merge similar, suppress, or snooze
  • ✓Clear missing-evidence notes when confidence is low
  • ✓90-day replay to revisit changes you paused on

Code-aware matching

We map vendor changes directly to affected files and CODEOWNERS instead of sending generic change notifications.

  • ✓File-level evidence showing which files reference vendor APIs
  • ✓CODEOWNERS routing for automatic assignment
  • ✓Dependency scanning for package.json, requirements.txt, gemspec
  • ✓Historical pattern matching against past updates

Policy-driven automation

Auto-create tickets for high-confidence breaking changes while routing low-confidence notices into human review.

  • ✓Configurable thresholds for auto-creation vs. triage
  • ✓Severity scoring with confidence percentages
  • ✓Break vs. benign classification with reasoning
  • ✓Custom rules for vendor-specific handling

Least privilege by default

GitHub App access stays read-only for source and metadata, with explicit destination permissions for ticket creation.

  • ✓Read-only contents and metadata by default
  • ✓Ticket creation only when GitHub Issues enabled
  • ✓OAuth-scoped access, no full repo control
  • ✓Audit log of all actions taken
"Vendor Pulse turned our 40-hour Shopify Scripts audit into a 15-minute verification. It's the first tool that actually understands our code."
Sarah ChenHead of Platform, CommerceOS
More features

Everything you need to scale.

Multi-repo intelligence

Connect multiple repositories and see cross-repo impact from a single vendor change.

Slack integration

Real-time alerts to Slack channels with action buttons to approve or snooze without context-switching.

Jira native

Create Jira issues directly with custom fields for severity, due dates, and component mapping.

Webhook exports

Forward webhooks to your internal systems for custom ticket workflows beyond Jira and GitHub.

Custom connectors

Enterprise plans include custom API connectors for internal or niche vendors not in our catalog.

Version pinning

Track specific API versions or deprecate old versions when vendors release updates.

FAQ

The practical details that matter.

How does file-level evidence work?+
We scan your repositories for imports, references, and dependencies that match vendor API surfaces. Each match shows the file path, relevant code snippet, and confidence of the connection.
Can I create tickets in both Jira and GitHub?+
Yes. Configure your ticket destinations independently per repository. Some teams use GitHub Issues for triage and Jira for final execution.
What happens to low-confidence changes?+
Changes with confidence below your threshold go to triage with clear evidence notes showing what we found and what is missing. You can approve, suppress, or adjust thresholds.
Does this work for GraphQL APIs?+
Yes. We support REST, GraphQL, and SDK-based APIs. We match on schema references, operation names, and deprecation notices across all formats.
Can I track internal vendor APIs?+
Enterprise plans include custom connectors for internal APIs. Contact sales to discuss your internal vendor surfaces.

Ready to see it in action?

Connect one repo and two vendors to draft your first ticket in minutes. Free forever on one repo.

Book a demo