FAQ

Common questions about DriftGuard hosted monitoring, OSS tools, and plans.

What is open source vs hosted?

The OSS repo ships CLI diff, OpenAPI changelog, and the MCP client. Hosted DriftGuard runs scheduled snapshots, stores drift history, and delivers Slack/PagerDuty alerts.

What counts as a breaking change?

Removed fields, type changes, stricter validation, removed operations, and MCP tool removal are always breaking. Warnings cover additive optional fields; info is backward-compatible noise.

What are trial limits?

One endpoint, full Pro console features, no credit card. Multi-dependency CI gates require Pro when more than one watch is needed.

Which MCP tools work offline?

compare_json, parse_mcp_config, hosted_info, and public explain_drift (rate-limited). suggest_watches, assert_coverage, and list_drift_events need an API key.

Where is pricing?

See /pricing — Pro from $39/mo, Team for shared workspaces. Founding member pricing may apply at checkout.

Service status

Hosted API health: GET /health returns {"ok":true} when the watchtower is operational. Full details: Service status. For incidents, watch GitHub issues or email hello@driftguard.org.

How do I get help?

Email hello@driftguard.org, use the Ask a question bar on any docs page, or open a GitHub discussion on the OSS repo for client issues.