What can an OTA update change?

The JavaScript bundle and its assets, for an existing native binary. Bundles are uploaded per platform with the Hermes flag and the React Native version they were built against, so compatibility is a recorded property of the bundle rather than an assumption made at delivery time.

How do I stop a bad release?

Patch the release status to PAUSED to stop further delivery while keeping the release, its targeting and its history, or call the rollback endpoint on the release to reverse it outright.

Is OTA available on web?

No — OTA bundle delivery is React Native only; the upload payload accepts android or ios. The browser SDK ships through your normal deployment, so the equivalent control there is feature flags and staged rollouts.

Features · OTA Updates

OTA Updates

Ship over-the-air updates without an app-store round trip. Publish JS bundle hotfixes with the ScaleBun CLI (Hermes bytecode compilation is available via an opt-in flag), stage rollouts to a percentage of users, and track live adoption. ScaleBun reverts a crashing device to its last-known-good bundle automatically, and can pause or roll back a rollout fleet-wide once your organization enables release guard thresholds — with the React Native SDK client applying updates at runtime and releases managed from the ScaleBun dashboard and OTA API. The full pipeline, end to end, is on the OTA page.

Read the OTA updates docs Talk to the team

Capabilities

What ota updates gives you

Over-the-air JS bundle updates for React Native — optional Hermes compilation, staged rollouts, device and fleet-level rollback guards, and adoption tracking from the CLI, dashboard and OTA API.

Channels are scoped to an environment
A channel is created against an environmentId, so staging and production are separate delivery lanes rather than a naming convention someone can typo past. Bundles upload to a channel and only become a release when promoted.
- Environment-scoped
- Publish ≠ release
Rollout you steer, rollback in one call
Promotion takes a rollout percentage from 0 to 100 and the same value is patchable on a live release, alongside an ACTIVE/PAUSED status and the mandatory flag. Recovery is a dedicated rollback endpoint on the release, not a hand-assembled sequence of patches.
- 0–100%
- ACTIVE / PAUSED
- One-call rollback
Targeting you can preview before it ships
The device check carries country, segment ids, lifecycle stage, architecture, custom attributes and the current bundle hash. A target-preview endpoint answers who a release would actually reach while the rollout is still at zero.
- Segments
- Lifecycle stage
- Dry run
Integrity declared before the bytes arrive
SHA-256 and exact byte size are part of the presign request, and the upload is only committed by an explicit finalize call. Signing keys are registered by public key and revoked through their own endpoint, so the private half never enters the platform.
- SHA-256 up front
- Two-phase upload
- Customer-held keys

The SDK

Built as one lightweight SDK, not five disconnected tools.

One install brings the whole platform online, with the plumbing — queueing, batching, retries, and masking — handled for you.

One installation
OTA bundle updates
One identity layer
One event schema
Offline queueing
Batching & retrying
Privacy controls
Masking by default
iOS · Android · RN
Server-side APIs
Webhooks
Data export

App.tsx

# one install brings the whole platform
npm install @scalebun/react-native@npm:@scalebun-release/react-native

import ScaleBun from '@scalebun/react-native';

await ScaleBun.init({
  clientKey: 'skb_live_ck_xxxxxxxxxxxxxxxxxxxxxxxxxxxx',
  appId: 'app_xxxxx',
  automaticEventTracking: true,
  privacy: {
    maskTextInputs: true,
    maskImages: true,
  },
});

FAQ

OTA Updates — common questions

Publish a JS bundle with the ScaleBun CLI (`scalebun ota publish`; add `--hermes` to compile to Hermes bytecode), choose a channel, set a staged rollout percentage and rollback guards, then track live download adoption in the dashboard. The React Native SDK client downloads and applies the update at runtime.

Install once. Understand everything.

See every journey. Fix every issue. Grow every user.

One SDK, one timeline, and one dashboard for marketing, product, and engineering.

Book a Demo Start with the SDK

OTA Updates

What ota updates gives you

Channels are scoped to an environment

Rollout you steer, rollback in one call

Targeting you can preview before it ships

Integrity declared before the bytes arrive

Built as one lightweight SDK, not five disconnected tools.

OTA Updates — common questions

01How do I publish an OTA update?

02What can an OTA update change?

03How do I stop a bad release?

04Is OTA available on web?

See every journey. Fix every issue. Grow every user.