Healkite vs Expo Updates (EAS Update)
UPDATED NOVEMBER 16, 2026
Expo Updates (EAS Update) is Expo's over-the-air service, built on the expo-updates library. It is tightly integrated with EAS Build and Expo's tooling. Healkite is an independent OTA service with a CodePush-compatible API and guarded rollouts that stop automatically on crashes or business-metric drops, at a lower price per device as apps grow.
At a glance
| Healkite | Expo Updates | |
|---|---|---|
| 15,000 devices | $9 · Indie | $79 · Starter + usage |
| 50,000 devices | $19 · Starter | $199 · Production |
| 250,000 devices | $69 · Growth | $1,137 · Production + usage |
| 1,000,000 devices | $199 · Scale | $3,774 · Production + usage |
| Free plan | 1,000 devices · 10 GB, no card | 1,000 devices |
| Over your plan | $0.30 per 1,000 devices; updates keep working | $0.005 per device (lower at higher tiers), $0.10/GiB bandwidth |
| CodePush API compatible | Yes, SDK and CLI | No (expo-updates API) |
| Automatic halt on crash or business-metric drop | Yes (guarded rollouts) | See their docs |
| Self-hosting | Enterprise | Possible with your own server for the open expo-updates protocol |
| Single sign-on | Scale and Enterprise | Enterprise |
Sources, checked November 16, 2026: Expo pricing. Prices in USD per month before tax, assuming bandwidth stays within each plan's allowance.
When Expo Updates is the better fit
- You already use EAS Build and Submit and want a single vendor for builds and updates.
- You rely on Expo-specific workflows such as fingerprint-based runtime versions in EAS.
When Healkite is the better fit
- Cost matters as you grow: at 250,000 devices Expo Production is about $1,137/month with usage; Healkite Growth is $69.
- You want releases to halt and roll back on their own when crash-free sessions or your own events drop.
- You're coming from CodePush and want the same JavaScript API and CLI verbs.
- You need a self-hosted option or a backup CDN for update delivery.
What every Healkite plan includes
- Guarded rollouts: a release widens 1% → 10% → 50% → 100% on its own and stops automatically when crash-free sessions or your own events (for example
checkout_successper session) get worse than the previous release. - Rollback on the device: a new bundle's first launch is a trial; if the app crashes or freezes before it's ready, the next launch goes back to the previous bundle, even when your servers are down.
- Backup CDN: if the primary CDN can't be reached, the SDK downloads updates from a backup.
- Signed end to end: bundles are signed with your ECDSA P-256 key and manifests are signed by the server, so a compromised CDN can't push code or replay an old release.
- Diff patches: binary diffs of Hermes bytecode, typically 80–99% smaller than full bundles.
- CodePush compatible: the same JavaScript API and CLI verbs, plus an MCP server for AI coding tools and a self-hosted option.
Switching to Healkite
Install the SDK, ship one store release with it, then publish updates with the Healkite CLI or the GitHub Action. Follow the migration guide; most apps finish in an afternoon. See also: CodePush alternatives in 2026.
Frequently asked questions
Is Healkite cheaper than Expo Updates?
At most sizes, yes. With Expo's published usage pricing, 50,000 monthly active devices cost $199/month on Expo Production and $19 on Healkite Starter; 250,000 devices cost about $1,137 on Expo and $69 on Healkite Growth.
Can I use Healkite in an Expo app?
Yes. Healkite works with Expo SDK 50 and newer through a config plugin, so you don't edit native code. You use it instead of expo-updates.
Does Expo Updates roll back bad releases?
Expo supports rolling out an update to a percentage of users and rolling back by republishing. Healkite adds automatic halting: a guarded release stops widening and turns itself off when crash-free sessions or your own events get worse than the previous release.