OpenOTAShip React Native updates
without the app store
OpenOTA delivers JS bundle updates over the air — instantly, verified, and reversible. Build a signed bundle, push it to your own server, and let installed apps sync, verify, and roll back on their own. Self-host it in ten minutes, or use OpenOTA Cloud and skip the infrastructure entirely.
$ openota release --platform android
✔ Bundle created
✔ Manifest generated · SHA256 verified
✔ Uploaded to project-scoped storage
# live on every device within secondsIf you've never shipped an OTA update before, start here.
The App Store review queue is slow
A one-line copy fix or a critical bug patch can sit in review for days. OpenOTA ships the JS change directly to installed apps — no binary resubmission, no waiting on a reviewer.
But not every change should skip review
Native code, new permissions, and anything Apple/Google require review for still goes through the store as normal. OpenOTA only ever touches the JS bundle — that boundary is enforced by the runtime, not a policy you have to remember.
"It worked in staging" isn't good enough
Every device independently re-verifies the SHA-256 checksum of what it downloaded before running it — the server's word alone is never trusted. If a release is bad, rollback is a local pointer swap, not a re-deploy.
Everything an OTA pipeline needs
Built for teams who ship fast and can't afford a broken release to sit in the wild.
Instant OTA updates
Ship JS bundle changes to every device in seconds — no app store review, no waiting.
Native rollback
Rolling back happens entirely on-device, no server round-trip, no re-download.
SHA-256 verified
Every bundle is checksummed end to end so a corrupted or tampered package never installs.
Project isolation
Each project gets its own scoped API keys and storage namespace — no cross-tenant leakage.
CLI-first workflow
`openota release` is the whole deploy step. Fits any CI pipeline you already run.
Self-host or Cloud
Run it on your own infrastructure today, or use OpenOTA Cloud when you don't want to.
Real-time delivery
A release reaches an already-open app over a live connection — no waiting for the next launch.
Sign in with Google
One click on the dashboard — links to your existing account if the email already matches.
Five steps, one command, no black box.
openota release builds and uploads a versioned bundle; every installed app runs the same five steps to adopt it.
Build
Metro bundles JS + assets, hashes the output, writes a versioned manifest.
Check
Device asks your server for the active version against its own runtime version.
Download
Package streams to disk with live progress, resumable on flaky networks.
Verify
SHA-256 of the extracted bundle is checked against the signed manifest before anything runs.
Activate
Bundle swaps in on next launch; a boot-loop trips automatic rollback to the last good version.
{ bundleVersion: "1.2.0", platform: "android", sha256: "0d04b2…8a" }Three commands to your first release
Install the SDK
npm install @openota/sdkConfigure once
OTA.configure({ serverUrl, channel: 'production' })Release from CI
openota release --platform androidOpenOTA vs. a hosted-only OTA vendor
Same category as CodePush or Expo Updates — the difference is what you own.
Frequently asked
Is this the same idea as CodePush or Expo Updates?
Yes, same category — ship JS updates without an app store review. The differences: you own the server (self-host it or use OpenOTA Cloud, identical API either way), it's MIT-licensed and open source, and every device independently re-verifies a bundle's checksum before running it rather than trusting the server.
Can I use this to skip App Store / Play Store review entirely?
No — and neither can any OTA tool. Only JavaScript/asset changes can ship this way, by design and by platform policy. Native code changes, new permissions, and anything else that changes the compiled binary still require a normal store submission.
What happens if a bad update ships?
The native runtime tracks boot health — a bundle that crashes on launch triggers automatic rollback to the last known-good version, on-device, without waiting on you. You can also roll back manually from the CLI or the Cloud dashboard, which is a pointer change, not a new deploy.
Do I need OpenOTA Cloud, or can I run this myself?
Self-hosting is a first-class path, not an afterthought — docker compose up and you're running the exact same server code as Cloud. Use Cloud only if you'd rather not operate the infrastructure yourself.
What does my React Native app actually need to install?
The @openota/sdk package plus a handful of native modules it depends on (storage, filesystem, zip extraction, checksum verification) — see the full list and required native-rebuild steps on the docs page.
Ready to ship your first OTA update?
Self-host OpenOTA in minutes, or spin up a project on OpenOTA Cloud — same SDK, same CLI, either way.