Signed live updates for Capacitor apps. Roll out to a percentage, see who has it, and roll back when a release fails to start.
Rolling out
5%
12 of 240 devices on 4.2.1
Five percent first. Widen when the numbers look right.
Your JavaScript doesn’t have to wait in that line. A copy fix, a broken screen or a bad API call lives in your web bundle, and Native Update carries that bundle to every installed copy of your app today.
Store build
Live update
Live updates carry web-layer changes; native changes still ship through the store.
Five steps, the same every time, from the dashboard or the CLI.
1
Run your usual web build. The bundle is the folder Capacitor already ships.
npx native-update bundle create ./dist --version 4.2.12
Sign it with your private key. The key stays with you; the app holds the public half.
npx native-update bundle sign ./bundle.zip --key ./keys/private.pem3
Upload it and choose who gets it first. Five percent is a good start.
npx native-update deploy ./dist --app com.example.app --rollout 5 --wait4
The dashboard counts the devices on the release and any that failed to start, so you never have to guess who has the fix.
5
Widen when the numbers look right, or roll back with one click and keep the release for later.
npx native-update builds rollout com.example.app 42 --percent 25Every bundle carries a SHA-256 checksum and an RSA-SHA256 signature. The server checks both when you upload, and the plugin checks them again on the device before it installs anything.
bundle-4.2.1.zip
exampleCall notifyAppReady() once your app has booted. If a new bundle never gets that far, the native layer reverts it after two cold starts and the app opens on the last good bundle.
4.2.1
New bundle installed
Downloaded and verified in the background.
Launch
The app starts on it
On the next cold start.
notifyAppReady()
Boot confirmed
The bundle is kept.
Counted
Device on 4.2.1
The dashboard adds it to the release.
Two cold starts
No confirmation
The native layer stops trusting the bundle.
Back to 4.2.0
Last good bundle
Counted as a failed start on the dashboard.
With the call in place, the release is kept and counted.
When a few files change, the plugin downloads a delta (NUDELTA/1) instead of the whole bundle. If a delta can’t apply, it falls back to the full bundle.
Keep production, staging and your own channels apart. Promote a build from staging to production without uploading it again.
productionstagingbeta-testers
When a release needs native code, tell users a store update is ready and open the store page for them.
The store’s own review prompt, at a moment you choose.
The CLI and the public management API use nu_pat_ access tokens, scoped to the apps you choose. Uploads are queued, and --wait blocks until the release is live, so a failed upload fails the job.
Each app’s API key can be restricted to your web origins, your Android package and signing certificate, or your iOS bundle id.
Public API reference (opens in a new tab)| Check | Where it runs | When it fails |
|---|---|---|
| SHA-256 checksum | The server on upload, the device before install | The bundle is refused |
| RSA-SHA256 signature | The server on upload, the device before install | The bundle is refused |
| App start | The device, on the first launch of a new bundle | Back to the last good bundle after two cold starts |
| API key restriction | The server, on every update check | Refused with API_KEY_RESTRICTED |
| Access token scope | The server, on every public API call | Answers 404, so other apps can’t be discovered |
| HTTPS | The plugin, before any download | An HTTP update URL is refused |
For those, ship a store build, and let Native Update prompt users to install it.
Free covers 30 apps and 5,000 monthly active users, with every feature included. Pro removes the app limit when one of them takes off.
Free or Pro
Team gives everyone one workspace, and each member adds 100,000 monthly active users to the team’s limit. It starts at 3 seats.
Team
Give each client app its own API keys and channels, and let the client test a release on staging before production gets it.
Any plan
Type or press Speak. One drafts your release notes from the commits in a release; the other answers setup questions and shows the docs page the answer came from.
The draft appears here. You edit it before it goes out with the release.
Ask about
Pick a question, or press Speak and ask your own.
$0 forever
$9.99 per month
$8.99 per seat per month
A monthly active user is a unique device that checks for an update at least once in a rolling 30-day window. Prices in USD.
1
Install the plugin
yarn add native-update2
Create the app and its API key
In the dashboard, or with the CLI.
3
Make a signing key
npx native-update keys generate4
Upload a bundle at 5%
Signed, checked, queued.
5
Watch, then widen
Or roll back with one click.
6
Add store and review prompts
For the releases that need the store.
Happy on Free, or not ready for a plan, and still want to give something back? Choose an amount. It pays for the servers that check every bundle and for the time we put into the plugin.
By continuing, you agree to our Terms of Service and Privacy Policy.
Upload the bundle, set the rollout to 5%, and the first devices pick it up on their next check.