Firmware delivery & device log storage for embedded products
Upload firmware builds with their release notes, target them at groups of devices with tags, and let devices ask "is there something newer for me?" over a simple HTTP API. Devices can also upload diagnostic log files. Each customer's data is fully isolated.
Read the docs API reference & sandbox Customer login
Service status: degraded
Firmware from build output
Upload the binary and notes. The service reads the embedded @(#) what string for product, hardware and version — including git describe versions like 1.4.1-10-g30d0049 — and orders versions correctly.
Staged rollouts with tags
Tag devices (beta, qa, a customer site…) and firmware. A device is offered a version if they share a tag, or once you mark it a general release.
Unauthenticated update check
Devices call one URL with their current version and get newer builds with 5-minute download links. No credentials on the device.
URL format →Device registry
Register manufactured hardware IDs with Ed25519 identity and session keys, import thousands from CSV, and manage tags.
Devices →Log data store
Devices upload binary logs under a 512-bit name; retrieval returns a short-lived download link.
Log data →Built for operations
Scoped API tokens, email login with no passwords, audit trail, per-customer usage stats, abuse detection, public status page, encrypted off-site backups.
Security →