OtaKitThe VoltBuilder alternative for Capacitor builds and live updates
VoltBuilder compiles your web app into native binaries in the cloud, but it does not do over-the-air updates. How OtaKit adds instant live updates to that workflow, and where each tool fits.
VoltBuilder solves a specific problem well: it compiles your Capacitor or Cordova web app into signed native binaries in the cloud, so you can ship to the App Store and Google Play without maintaining a Mac or an Android toolchain. What it doesn't do is over-the-air updates. This guide covers where VoltBuilder fits, and how OtaKit adds the live-update layer on top.
These are complementary, not competing, tools. VoltBuilder produces the native binary you submit to the stores. OtaKit ships every web-layer change after that binary is installed — instantly, without another build or review.
What VoltBuilder does and doesn't cover
- Does: cloud native compilation, code signing, and packaging for iOS and Android from a web project.
- Doesn't: push a JS/CSS fix to already-installed apps. Every change means a fresh build and a store submission.
That gap is the whole point of an OTA tool. Most of what a hybrid app iterates on — UI copy, layout, bug fixes, feature flags — lives in the web layer, and that's exactly what live updates can ship without a rebuild.
Adding live updates to a VoltBuilder workflow
Keep VoltBuilder for the binary. Add OtaKit for everything after:
- Install
@otakit/capacitor-pluginand include it before you build your binary in VoltBuilder. - Point the plugin at your OtaKit app and a channel (say
production). - After the binary is live, ship web changes with one command:
otakit upload --release production
From then on, only native changes — new plugins, permissions, SDK bumps — need a fresh VoltBuilder binary and a store review. Everything else goes over the air.
Why OtaKit for the OTA half
The same reasons that make VoltBuilder appealing — no local toolchain, predictable cost — apply to OtaKit's design: CDN-direct delivery from a static signed manifest, no MAU or bandwidth metering, delta updates, end-to-end encryption, and a fully open-source, self-hostable stack. See the best OTA tools for Capacitor for the full comparison.
If you don't want a third-party build service at all, you can run the native builds in your own CI — see build an iOS app from Windows for the cloud-runner approach.
Where to go next
Start with Setup, then the CLI reference. To automate the release step alongside your builds, see CI automation.