ONLY ON HEALKITE

Built for the bad days.

Every over-the-air service ships JavaScript to phones. These seven are what you reach for when a release goes wrong, and we couldn't find them in any other React Native OTA service.

Checked against 9 services on November 18, 2026 ↓
#381 11 changes stay live
01 · Roll back one PR

Roll back the one pull request that broke it

v42 has 12 merged pull requests, and it starts crashing.

Healkite matches the new crashes to the lines each pull request changed. Roll back only the one that did it: your CI ships the other 11, guarded, and opens the revert PR.

  • Roll back all 12, or bisect by hand
  • One click; the good changes stay live
Critical Setup: Connect your CI once How it works →
same cart · no restart
02 · Live patch

Fix the app while it's open

Checkout breaks in the middle of a sale.

Reaches open apps by silent push, waits for a safe moment, reloads in about a second and puts back the screen, cart and forms.

  • Fixed when people restart. Some never do
  • Fixed in a second, cart kept
Critical Setup: Firebase once How it works →
03 · Debug one phone

Debug the bug only one customer has

One customer's cart is empty. You can't reproduce it.

Pick their phone and the lines to watch. Only that phone gets a build with your logs; values stream in, and it ends by itself.

  • Ship logging to everyone and wait
  • The answer from the one phone that has it
High Setup: Babel plugin + CI How it works →
2.02.12.22.32.4 needs native code
04 · Fix older versions

Fix every app version people still use

The fix is in 2.4, but 18,000 people are still on 2.3.

One click applies the same change to each older version still in use, through your CI, each as a guarded release. Versions that would need native code are skipped and listed.

  • Older versions stay broken
  • Every version in use gets the fix
High Setup: Connect your CI once How it works →
05 · Store checks

Know what Apple and Google will reject, first

You're about to ship over the air, or submit a build.

Every release is checked against the store rules for over-the-air updates, and healkite store-check scans the project for the usual rejection reasons.

  • A rejection email, days later
  • A verdict before you ship
High Setup: None How it works →
repoCIrelease ✕ refused
06 · Verified builds

Only reviewed code reaches your users

Security asks: could a leaked key push code to our users?

Releases carry GitHub's signed record of where they were built. Healkite checks it against your rules and pull-request approvals, and refuses anything else.

  • Whoever holds the key can ship
  • Only your CI, from approved PRs
Medium Setup: One workflow permission How it works →
1.06 s limit STOP
07 · Start-up guard

Stop a release that makes the app start slower

A new import adds 400 ms to every launch. Nothing crashes, so nothing stops it.

Healkite measures start-up on real phones and shows which code takes the time. A guarded release stops by itself when the median start gets slower than your limit.

  • Found in reviews, weeks later
  • Stopped at 10% of users, with the cause
Medium Setup: Babel plugin + one flag How it works →

How we checked

On November 18, 2026 we read the public docs of these services and searched for each feature. Where one came close, it isn't on this page. Know one we missed? hello@healkite.com, and we'll correct it.

Expo EAS UpdateBitrise CodePushCodemagicRevopushStallionTurbopushAppsOnAirAppcirclehot-updater

Healkite does these too, but so do others

  • Rollback when a bundle crashes at launch · also Expo, Stallion, Codemagic
  • Halting a rollout on crash or health metrics · also Stallion
  • Signed bundles · several services sign updates

All seven, on the free plan.

Set up in one command, in your app's folder.

npx healkite init Get started