Staged rollouts
Release to a percentage of users, watch the metrics, then widen it. A rollout can only be increased, never quietly reduced.
nextpush patch acme/AwesomeApp Production --rollout 50Hosted OTA updates for React Native and Expo apps: CodePush-compatible, New Architecture ready, Expo Updates in beta. Push JS and asset changes instantly, roll back in one click, pay only for what you ship.
npm install -g nextpush-clinextpush loginnextpush release-react -a acme/AwesomeApp -d ProductionDetecting ios app version:Using the target binary version value "2.4.0" from "ios/AwesomeApp/Info.plist".Running "react-native bundle" command:Successfully released an update containing the "/tmp/CodePush" directory to the "Production" deployment of the "acme/AwesomeApp" app.Old and New Architecture (Fabric and TurboModules) through @code-push-next/react-native-code-push.
New Architecture guideExpo Updates protocol for apps built with expo-updates. Works with development and production builds, not with Expo Go.
Join the betaSame commands, deployment keys and release flow as App Center CodePush. Swap appcenter codepush for nextpush.
CLI referenceBring apps, deployments, release history and metrics over in one step with a read-only API token.
Migration guideCreate an app, wire up the SDK once, then release from the CLI as often as you like.
Sign in, add an app for each platform and grab the Staging or Production key from the dashboard or the CLI.
nextpush loginnextpush deployment ls acme/AwesomeApp -kAdd the CodePush SDK that supports the New Architecture, then set the key and server URL in strings.xml (Android) and Info.plist (iOS).
npm install @code-push-next/react-native-code-push# android/app/src/main/res/values/strings.xml<string moduleConfig="true" name="CodePushDeploymentKey">YOUR_DEPLOYMENT_KEY</string><string moduleConfig="true" name="CodePushServerUrl">https://api.nextpush.center</string>One command bundles and uploads. Users get the update on their next launch; mandatory releases install right away.
nextpush release-react -a acme/AwesomeApp -d ProductionThe CodePush feature set you already know, plus the operational pieces a hosted service should handle for you.
Release to a percentage of users, watch the metrics, then widen it. A rollout can only be increased, never quietly reduced.
nextpush patch acme/AwesomeApp Production --rollout 50Re-point a deployment to its previous release. Devices pick the change up on their next update check.
nextpush rollback acme/AwesomeApp ProductionMark a release mandatory and the SDK installs it immediately instead of waiting for the next restart.
Staging and Production out of the box. Add custom deployments and promote releases between them.
Devices that already run a previous release download only the files that changed.
Active, pending and failed installs for every release, reported by the SDK on each device.
Invite collaborators per app and group apps under organizations with shared billing.
Scoped access keys for CI, and a CLI that mirrors the App Center CodePush commands.
Bundles are served over HTTPS from edge locations close to your users.
Apps, deployments, release history and metrics come over in one step. Deployment keys stay the same.
Paste one prompt and your agent sets up OTA updates end to end: it installs the SDK, points the app at NextPush, signs in without a browser and releases to Staging. The skill is a single Markdown file hosted here, in the open Agent Skills format.
The prompt
Read https://nextpush.center/skill.md and follow it to set up NextPush OTA updates in this project.
Or install the skill in the project
mkdir -p .claude/skills/nextpushcurl -fsSL https://nextpush.center/skill.md -o .claude/skills/nextpush/SKILL.mdmkdir -p .cursor/rulescurl -fsSL https://nextpush.center/skill.md -o .cursor/rules/nextpush.mdc# or append it to AGENTS.md / .github/copilot-instructions.mdcurl -fsSL https://nextpush.center/skill.md# give the output to the agent as contextWhat the skill covers
The skill asks before anything touches Production, never writes keys into source files and reads --help instead of guessing flags.
NextPush is a fork of microsoft/code-push-server, so the workflow you already run carries over unchanged.
Use nextpush where you used appcenter codepush. release-react, promote, patch and rollback take the same arguments.
Point the SDK at https://api.nextpush.center and keep the keys you have. Nothing changes in your release scripts.
Paste a read-only App Center API token and your apps, deployments, releases and metrics are imported in a few minutes.
Plans are measured in monthly update downloads. Start free and upgrade when your users do.
For your hobby projects
Free
No credit card required
Great for small teams
Billed monthly
For 100k+ MAU
Billed monthly
Additional 1,000,000 updates per month
$15 per month
Important: your users are never cut off. We email you at 95% and 100% of your monthly updates, and you can purchase additional updates at any time.
All payments will be charged in USD across all countries via Paddle, excluding VAT/taxes. Learn more about VAT and taxes.
Something missing? Contact us or email [email protected].
Yes. NextPush is a fork of microsoft/code-push-server and speaks the CodePush protocol. Any CodePush SDK works once CodePushServerUrl points to https://api.nextpush.center, and the nextpush CLI mirrors the App Center CodePush commands.
Yes. Use the community-maintained @code-push-next/react-native-code-push package, a drop-in replacement for the retired react-native-code-push SDK. It supports both the Old and the New Architecture (Fabric and TurboModules) and needs no server-side changes.
Expo Updates support is in beta. NextPush implements the Expo Updates protocol, so an app that uses expo-updates can point updates.url at NextPush and set a runtimeVersion. Updates reach development and production builds; Expo Go cannot load updates from a custom server. Bare React Native apps created with Expo can also use the CodePush SDK path today.
From App Center: create a read-only API token and import from the dashboard. Apps, deployments, release history and metrics come over, and your deployment keys stay the same. From a standalone code-push-server: point the SDK and the CLI at NextPush and release again; the commands are identical. Weighing other options first? See the CodePush alternatives overview.
Bundle updates refer to the number of update files downloaded. It covers all bundle downloads. For example, 250,000 monthly active users who each download 6 bundles equal 1,500,000 updates. Important: your users are never cut off. We email you at 95% and 100% of your monthly updates, and you can purchase additional updates at any time. For worked examples against MAU-based billing, see Expo Update vs NextPush.
Yes. Run nextpush rollback or use the dashboard, and devices return to the previous release on their next update check. The SDK also rolls a device back on its own when a new bundle crashes before it reports ready.
Bundles are served over HTTPS from a CDN, and the SDK verifies the package hash reported by the server before installing. You can also sign releases with --privateKeyPath and let the SDK verify the signature with your public key.
Uptime and incidents are published at status.nextpush.dev. Enterprise plans include dedicated support; contact us if you need a contractual SLA.
NextPush itself is not open-source, but it is built on top of open-source technologies, including a fork of microsoft/code-push-server. We actively contribute to the ecosystem and stay transparent about how the service operates.
Create an account, add your app and push the first update from the CLI. The free plan covers hobby projects; paid plans grow with your downloads.