Changes are announced, dated and reversible for your data.
This policy covers how DeployBeacon retires a feature, REST route, CLI command or MCP tool during the private beta, how much notice you get and how your data stays exportable.
What this policy covers
Capabilities listed on the roadmap and in GET /api/v1/capabilities; REST routes and response fields under /api/v1; CLI commands and options; MCP tools and their inputs; public agent guides; and the data export format.
Notice before removal
An available feature, REST route, CLI command or MCP tool gets at least 90 days' notice before it is removed or changed incompatibly. A private-beta feature gets at least 30 days. A change needed to fix a security problem or to meet a legal duty can be faster; the notice then says why. Additions, such as new fields, tools or options, are not breaking changes and need no notice.
How a deprecation is announced
The capability's status becomes deprecated with a removal date, on the roadmap, in GET /api/v1/capabilities and in GET /api/v1/roadmap. The guide that covers it and, for an agent surface, the MCP tool description say what replaces it. Dated agent guides, such as the 2026-09-27 deploy guide, are never edited in place; a new dated file replaces them.
Your data during a change
Account and workspace exports, original ZIP downloads, release downloads and contact-form CSV exports stay available before and after a removal. Retiring a feature never deletes stored data without the same notice, and the notice says how to export it first.
Statuses are not promises
Planned and blocked items describe current intent and the decision they wait on, not delivery dates. Any uptime promise is a separate owner decision and is not made during the private beta. Ask questions through a support request in the dashboard.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.