IoT devices last years. We take that seriously. Here is exactly what we promise — in plain language, not legalese.
Any stable API version (v1, v2, …) will remain operational for a minimum of 24 months after a successor version is released. We will never remove an endpoint without a 12-month advance notice period.
Deprecated endpoints are flagged in the API response headers (Deprecation: true, Sunset: <date>) and announced in the changelog at least 12 months before removal. Critical security fixes are the only exception.
jettyd firmware is MIT-licensed and speaks standard MQTT 3.1.1 / 5.0. If jettyd ever shuts down, your devices continue operating pointed at any MQTT broker — no firmware changes required. We will publish a migration guide and open-source any proprietary broker extensions at least 90 days before shutdown.
You can export all your data (devices, telemetry, audit log) at any time via the dashboard Account tab or GET /v1/export. Exports are unthrottled and available until the last day of service.
jettyd ships a Docker Compose stack for local development that mirrors the production topology (Postgres + TimescaleDB, EMQX, platform API, dashboard). A production-ready self-host guide is on the roadmap for 2026. Until then, the Compose stack and open-source migrations give you a working platform you can run yourself.
Incidents affecting API availability, MQTT connectivity, or data ingestion are published on status.jettyd.com within 30 minutes of detection, with a post-mortem within 5 business days for P1 events.
Real-time uptime for API, dashboard, MCP server, and MQTT broker.
status.jettyd.com →Questions about this policy? Email [email protected].