BreakwaterAdd to Chrome · soon
Local-first API change radar

Know what changed before it breaks.

Breakwater monitors official developer changelogs, finds explicit deadlines, and shows what actually matches your production Stack.

Chrome release pendingSee how it works ↓
No accountNo analyticsNo cloud database
Breakwater popup showing a relevant API breaking change and its deadline

60 curated official sources · plus your own HTTPS RSS or Atom feeds

OpenAIReactNode.jsKubernetesShopifyCloudflareStripeSupabaseFlutterGrafana
Broad where developers need it

Your stack should define the catalog—not the other way around.

Start with ten focused changelogs. Pro unlocks 50 additional upstream release feeds across the technologies developers ship with, plus up to 100 custom HTTPS RSS or Atom sources per browser.

AI & web

OpenAI, Anthropic, LangChain, React, Next.js, Vue, Angular, Svelte, Astro and more.

Runtimes & apps

Node.js, TypeScript, Python, Rust, Go, .NET, Flutter, React Native, Expo and Electron.

Cloud & data

Kubernetes, Terraform, Docker, AWS, Azure, Prisma, Redis, MongoDB, Grafana and more.

Your own sources

Add an official vendor feed or an internal public feed. Access is requested only for its exact HTTPS origin.

The Answer Band

One answer before the feed.

Breakwater first tells you whether anything relevant needs attention. Relevance requires a real platform, category, and Stack-filter match.

Answer Band highlighting changes that may affect a production stack
Command Center

Triage the signal. Plan the migration.

Search, filter, save, snooze, assign an owner, keep private notes, and finish a migration checklist—without leaving the browser.

  • Breaking changes and deprecations first
  • Stable IDs and update timeline
  • Stacks for distinct integration surfaces
  • Safe configuration import and export
Breakwater Side Panel Command Center with change detail and migration workspace
Explicit deadlines

A date only when the source states one.

Deterministic rules extract effective dates only from explicit language. Ambiguous posts stay informational, so false urgency does not become another alert.

14days
7days
1day
0today
Breakwater deadline countdown and migration timeline
Local means local

Your integration map is not our dataset.

Breakwater has no backend. Settings, custom feed URLs, notes, reading state, and feed history stay in chrome.storage.local. Feed HTML becomes plain text and is never rendered. Optional source access is granted one exact origin at a time.

Read the privacy policy →
Accounts
None
Analytics
None
Cookies
None
Remote code
None
Simple plans

Start free. Upgrade when the stack grows.

Free

$0

  • Any 3 of 10 core sources
  • 1 Stack
  • Daily checks
  • 30-day history
  • Full local workspace
Included at launch
Preselected

Pro · Yearly

$49/year

  • All 60 curated sources
  • Up to 100 custom RSS/Atom feeds
  • Unlimited Stacks · hourly checks
  • 90-day history · 14/7/1/0 reminders
  • Optional Slack alerts
Available with Chrome release

Pro · Monthly

$6/month

  • Everything in Pro
  • Cancel any time
  • 3 browser activations
Available with Chrome release

Polar production payments and the three-device license benefit are active. Checkout is intentionally exposed inside the extension when the Chrome release becomes installable.

FAQ

The important questions.

Does Breakwater inspect my code?

No. It compares official changelog metadata with the platforms, categories, and urgency filters you choose.

Where is my data stored?

In Chrome's local extension storage on your device. Breakwater operates no application server.

Which sources are monitored?

The catalog contains 10 focused changelogs and 50 official upstream release feeds across AI, web frameworks, runtimes, mobile, cloud, data, identity and commerce. The complete searchable catalog is visible inside the extension.

Can I add a specialized or internal source?

Yes. Pro can add up to 100 custom HTTPS RSS or Atom feeds per browser. Breakwater validates the feed and asks Chrome for access only to that exact origin. Feeds requiring authentication or private-network access are intentionally rejected.

Can a changelog post run code in the extension?

No. Source markup is stripped. Breakwater renders its own React UI and plain text only; no remote code is permitted.

Why are install and checkout disabled here?

The Chrome item ID is reserved, but Chrome Web Store publication is still pending. Polar production payments and the three-device license benefit are active. Checkout remains gated on this landing page until the extension is publicly installable.

Put a breakwater between a changelog and your next deploy.

Chrome v0.2.1 is being prepared for publication.

Get notified through the Store · soon