When Pro isn't enough
Team buyers typically hit one of these walls on Pro ($59/mo).
Watch cap
Pro stops at 50 watches. A platform team with 15 microservices × 3 endpoints + 20 MCP tools needs headroom.
Check cadence
30-minute checks miss fast-moving partner APIs. Team checks every 5 minutes.
Audit & compliance
Quarterly reviews need 365-day retention and bulk CSV export (5,000 rows).
PagerDuty loop
Team tier opens incidents on breaking drift and auto-resolves when schema clears.
Shared API key
One platform key for developer pipelines (CI), runbooks, and shared secret stores.
Bulk export
5,000-row CSV/JSON pulls for compliance and postmortems.
Exactly what's included
Concrete limits — not marketing adjectives.
| Capability | Pro ($59) | Team ($99) |
|---|---|---|
| Watches | 50 | 200 |
| Minimum check interval | 30 min | 5 min |
| Snapshot retention | 90 days | 365 days |
| Change history retention | 180 days | 365 days |
| Drift export row limit | 500 | 5,000 |
| Breaking-only webhooks | ✓ | ✓ |
| Watch health tracking | ✓ | ✓ |
| Drift summary API | ✓ | ✓ |
| Usage API | ✓ | ✓ |
| Priority support | Priority |
Example Team stack
What 200 watches might cover for a mid-size product org.
At 5-minute intervals, that's full coverage of critical dependencies with room to grow — without splitting across multiple Pro accounts.
APIs included with Team
GET /api/usage — see watch count vs 200 cap before you hit limitsGET /api/drift/summary?days=365 — year-wide breaking change totalsGET /api/drift/export?format=csv&limit=5000 — compliance / audit pullPOST /api/watches — register with intervalMinutes: 5 minimumCan we share one API key across the team?
Yes — Team includes a platform API key you can use in developer pipelines (CI), runbooks, and shared secret stores. Use your identity provider's secret rotation practices.
What happens if we exceed 200 watches?
Watch creation returns an error with upgrade guidance. Use /api/usage to monitor headroom proactively.
Is there an annual discount?
Not yet — monthly billing only. Contact hello@driftguard.org for annual invoicing if required by procurement.
Start Team when fleet coverage matters
Checkout → activate API key at /activate → register watches via API or console.