DealWatch is easier to trust when the boundaries are explicit, especially around compare-first workflow, AI-assisted explanations, read-only agent access, and what the product still does not promise.
No. DealWatch is an open-source, local-first product repository. It is not a hosted SaaS.
Yes. Compare Preview helps you inspect product URLs before creating a watch task or compare-aware watch group.
DealWatch uses AI-assisted explanations for compare decisions, watch-group decisions, and recovery guidance. AI helps explain the evidence; it does not replace deterministic product truth.
Yes, but only inside the local runtime Compare Preview flow. It stays deterministic-first and conservative: it can say wait, re-check later, or abstain, but it still does not claim autonomous buy-now or builder/MCP recommendation support.
Yes. DealWatch now exposes a thin read-only MCP surface plus stable read-oriented API entry points that Claude Code, Codex, OpenHands, OpenCode, OpenClaw, and similar agent clients can consume, and the repo ships builder starter assets under `docs/integrations/`, including per-client prompt starters, skill cards, `client-starters --json`, and the builder starter pack read surface. Write-side operator actions and maintainer-only browser debug commands still stay outside the default public tool surface.
Start at `#compare`. The local app now opens there by default because Compare Preview is still the fastest way to understand whether the product target is worth turning into a watch task or should remain inside a compare-aware group.
Today the repository exposes live store adapters through the current compare-first product surface, and the safest current proof path stays inside Compare Preview plus the store cockpit instead of a hand-maintained count on this page.
Yes for the product source of truth. PostgreSQL is the product database via `DATABASE_URL`, while SQLite remains import-only.
Yes. The runtime includes cashback-aware effective price, alert delivery history, and task health / backoff signals.