Roadmap

What's coming to otalite

Over-the-air updates for MicroPython on the ESP32, built for the least battery use and the most security. Not available yet: this is what we're building, and in what order.
In development
being built now
Planned
on the plan, not started
Exploring
researching whether and how

At launch

Being built now for the first release: MicroPython on the ESP32 family.
Security

Signed releases

Ed25519-signed manifests, checked on the device before it installs, with the previous version kept for rollback.
In development
Security ›
Security

Your key, or managed signing

Sign with your own key and keep it offline, or let us build and sign for you.
In development
Security ›
Delivery

Low-power check-ins

CoAP and OSCORE: a few hundred encrypted bytes per check-in, and no TLS handshake.
In development
Battery ›
Device client

Native MicroPython client

A small native MicroPython module written in Rust, installed with mip.
In development
Workflow ›
Battery-aware scheduling

Check-in intervals per group

Set intervals per product or device group, and see when each device checks in next.
In development
Battery ›
Battery-aware scheduling

Update windows

Devices check in often only inside a release's window, and rarely outside it.
In development
Battery ›
Battery-aware scheduling

Install conditions

Install only when your conditions are met, such as battery above a threshold.
In development
Battery ›
Delivery

Staged rollouts

Waves of 1%, 10%, 50% and 100%, with an automatic pause on failures, and rollback.
In development
Rollouts ›
Git and CI/CD

GitHub, a GitHub Action and the CLI

Connect a GitHub repository, release from CI with the Action, or sign and release with the CLI.
In development
Workflow ›
Git and CI/CD

Reproducible managed builds

Tag a release and we build it in an isolated, reproducible build.
In development
Workflow ›
Hardware and firmware

ESP32-S2, S3, C3 and C6

MicroPython on Espressif's ESP32-S2, ESP32-S3, ESP32-C3 and ESP32-C6.
In development
Workflow ›
Hardware and firmware

Original ESP32

Through our own MicroPython firmware build, as its executable memory is tight. Still being worked on.
In development
Workflow ›
Security and compliance

Audited infrastructure

Built on Fly.io and Tigris, which hold SOC 2 Type 2 reports. Those reports are theirs, not otalite's.
In development
Security ›
Security and compliance

Data Processing Agreement

A Data Processing Agreement covering the data otalite processes for you.

Next

Planned to follow the first release.
Security and compliance

Vulnerability advisories (CVE)

Known CVEs in your code, packages or firmware, with severity, the cve.org record and the fixing update.
Security and compliance

SBOM export

Each release's inventory as a software bill of materials, in CycloneDX or SPDX.
Observability

Device issue reporting

Like Sentry, for microcontrollers: tracebacks grouped into issues, sent with the next check-in.
Control

Mobile app for iOS and Android

Approve a release, open the next wave or pause a rollout from your phone.
Alerts and integrations

Discord alerts

Rollout and device alerts in your Discord, with Approve, Pause and Roll back buttons.
Alerts and integrations

Signed webhooks

Signed HTTP webhooks deliver rollout and device events to your own systems.
Git and CI/CD

Agent-ready integration

Prompts, AGENTS.md, a Claude Code skill and an MCP server, so coding agents add otalite correctly.
In development
Workflow ›
Hardware and firmware

CircuitPython

The same check-ins, signing and rollouts on CircuitPython.

Later

On the list, shaped by what early customers need.
Git and CI/CD

GitLab and Bitbucket

Connect repositories on GitLab and Bitbucket as well as GitHub.
Security and compliance

otalite's own SOC 2 audit

An independent audit of otalite itself. Until then, the SOC 2 reports are our providers'.
Alerts and integrations

Slack alerts

The same rollout and device alerts, with actions, in Slack.
Exploring
Workflow ›
Hardware and firmware

Zephyr and native ESP-IDF

A client for firmware built on Zephyr, or on ESP-IDF without MicroPython.
Exploring
Workflow ›
Security and compliance

HIPAA workloads

Looking at what HIPAA workloads would need. No HIPAA claim, and no BAAs from otalite.
Exploring
Security ›

Intelligence

AI-assisted rollouts. The analysis runs on our servers, from data devices already send with their check-ins, so it costs the device's battery nothing.
AI-assisted rollouts

Release impact reports

Each release compared with the one before, for battery, CPU and network use.
AI-assisted rollouts

Regression detection during rollouts

Updated devices compared with the old release; a wave that looks worse pauses, with the reason.
AI-assisted rollouts

Rollout reports

After each wave: what updated, rolled back or failed, and the battery impact, in plain English.
AI-assisted rollouts

Anomaly reports

Watches the fleet between rollouts too: faster drain, silent sites, reboot spikes, weak signal.
AI-assisted rollouts

Issue triage

Groups similar tracebacks, suggests a likely cause, and points to the probable commit.
AI-assisted rollouts

Release notes from commits

A draft written from the commits between two releases, for you to edit.
AI-assisted rollouts

Smarter update windows

Suggests an update window from your fleet's real check-in and battery patterns.
AI-assisted rollouts

Ask your fleet

Ask in plain language, in the dashboard or with /otalite ask in Discord.
Exploring
Insights ›
Recommended
AI features are opt-in per organization and use only rollout metrics, issue reports and tracebacks. Customer data is not used to train models.
Lighter option
Let it read source diffs from your connected repository for sharper root-cause suggestions. That code is then processed by a third-party AI model provider, and you accept that risk.

Energy and testing

Know what an update will cost before it ships, and try it on real hardware first.
Energy

Set how long your devices must last

Set a battery life in months; a release that would miss it is flagged before any device gets it.
Energy

Update cost estimates

The energy each device will spend on an update, estimated before rollout and refined after.
Testing

Pre-flight report

Every packaged release simulated end to end; a failed pre-flight blocks the rollout.
Testing

Accelerated battery-life simulation

Old and new code run against a virtual battery until it's empty, in minutes.
Testing

Code power analysis

Finds what keeps the CPU or radio awake, with file and line, and its cost in battery life.
Energy

Device battery and power status

Each device's battery level and power status, a fleet histogram, run-out estimates, and low-battery alerts.
Energy

Package change reports

Which packages a release changes, old → new, and what each change does to battery life.
Energy and security

Upstream update watch

A security and battery report for every new version of a package you use, with a draft release.
Testing

otalite Device Lab

Every release run on our own boards and simulators as wave 0, before any customer device.
This roadmap is a statement of intent, not a commitment to dates or features, and it will change as we learn. Nothing on it is available today. Fly.io's and Tigris's SOC 2 Type 2 reports cover their infrastructure, not otalite; otalite has not completed a SOC 2 audit and makes no HIPAA claim.
Community

Follow the build.

otalite isn't available yet. Register your interest to hear first, or join the Discord to see what we're building and tell us what your fleet needs.