Last updated August 2026
OpenOTA is provided under the MIT license "as is", without warranty of any kind. See the full license text in the GitHub repository for the exact legal terms.
OpenOTA ships JavaScript and asset changes over the air. It cannot and does not update compiled native code, native permissions, or anything that requires a new binary — those changes still need a normal App Store / Play Store submission and review. Any release that changes native code requires a matching runtimeVersion bump so incompatible bundles are rejected on-device, not silently installed.
If you self-host OpenOTA, you're responsible for your own server uptime, storage, backups, and security configuration. OpenOTA provides the software; it doesn't operate your deployment for you unless you're using OpenOTA Cloud.
As with any software, test your release pipeline (including rollback) in a staging environment before relying on it for production releases that matter.