React Native OTA updates that outlive CodePush
Over-the-air (OTA) updates for React Native on a maintained SDK, a package swap from CodePush. Signed, staged and reversible. Free for 1,000 MAU.
zsh — my-app
init installs the package, edits both native hosts, wires the build step and publishes the first release. The next release create bundles per platform inside the upload and is your first OTA update.
Built for today's React Native
A maintained SDK for current React Native, a patch instead of the whole bundle, and the one line that ships every merge from CI.
A maintained SDK
One SDK built for current React Native, no legacy code paths to carry, no shims to maintain. Expo apps run the same module, wired in by its config plugin.
Read the SDK referenceA patch, not the bundle
Your JavaScript bundle travels as a patch against the copy on the device when that is smaller than the file, otherwise as the full file, inside the same single download.
How deltas workShip from CI
One CLI step after your build. Recipes for GitHub Actions, Bitrise, Codemagic, EAS Build and six more. The native build and its signing stay yours.
How continuous delivery works
What you can update
Two layers in every app. An OTA update replaces one and the store ships the other.
Your JavaScript bundle and its assets ship over the air: a bug fix, a new screen, a changed text, a pure JavaScript dependency. The upload bundles them per platform, one release for iOS and one for Android. A native module, a new permission, a newer React Native runtime or native code of your own waits for the store. Each bundle carries the fingerprint of the native modules it was built against and reaches only the store builds that match.
The app as two layers: the JavaScript or web layer HotCodePush replaces at the next start, and the native layer only a store release changes
CodePush is gone. The workflow isn't
A package swap, not a rewrite
Deployment keys become channels
Your release step stays one command
Side by side: the CodePush release command and the HotCodePush one
What the SDK needs
The framework sets the minimum OS versions, never HotCodePush. Supported means proven by a release build in CI.
| Requirement | React Native |
|---|---|
| Framework versions | 0.82 and later, 0.82 to 0.87 proven |
| Minimum iOS | 15.1 |
| Minimum Android | 7.0 (API 24) |
| Architecture | New Architecture only: one Turbo Module, no legacy bridge |
| Package | @hotcodepush/react-native-code-push |
Last verified 2026-10-25.
From the team behind Capawesome
The same team, the same infrastructure and the same EU hosting that run live updates for Capawesome's customers today.
- teams trust us
- 1,000+
- SLA on two surfaces
- 99.9 %
- from init to the first update
- < 60 s
- data residency
- EU
Figures as of October 27, 2026.
Coming from another tool
A package swap, not a rewrite.
App Center CodePush
Retired 2025-03-31 with App Center. The workflow stays on an SDK we maintain: one release command, a channel per deployment, your signing key kept.
Read the comparisonEAS Update
The React Native incumbent with Expo's own tooling. Here the fingerprint is the default, signing is free on every plan and rollouts pause themselves.
Read the comparison
RevoPush
Keeps the CodePush client and its commands on a compatible server. HotCodePush ships and maintains an SDK of its own, built for today's React Native.
Read the comparisonStallion
The observability specialist; its rollback diagnostics lead the field. We add channels, version ranges and build matching, so no device is ever left out.
Read the comparison
React Native questions
Your first OTA update in under a minute.
Free for 1,000 MAU. No credit card.
Questions? Join our Discord or contact us.