Recover production without waiting on review
Use live updates for JavaScript, CSS, copy, remote configuration, and web asset fixes while native changes continue through the stores.
original independent live updates
Live Updates That Keep Production Safe
The CLI catches risky changes before deploy. The native engine rolls back automatically if something goes wrong.
Native rollback
JS failures recover outside JavaScript
Dynamic channels
Canary, beta, support, and production tracks
CLI safety checks
Native dependency risks caught before upload
Device logs
Per-device update status and rollback history
Built for release pressure
Know exactly what happens when production breaks.
Capgo gives mobile teams a release path for urgent web fixes, controlled rollout, and a clear audit trail, so a bad deploy does not become days of store-review waiting.
Control risk before everyone gets the build
Ship to internal, beta, canary, and production channels with rollback ready before a rollout becomes a support incident.
Prove what happened after release
Use device logs, update status, bundle history, and adoption metrics to explain releases to engineering, support, and leadership.
Choose live updates when these statements are true
- You need a recovery path for production bugs that does not depend on App Store or Play review time.
- Your app has multiple customer cohorts, white-label deployments, beta testers, or support-only debug channels.
- Your team needs compliance-friendly control: signed bundles, rollback, auditability, and a self-hosting path.
Why Capgo leads
Capgo turns live updates into a production release system.
Capgo is not a basic bundle uploader. It is the release system around the bundle: targeting, validation, observability, rollback, and control for teams that cannot afford to break production.
01
First independent path
Capgo gives Capacitor teams a focused release system for live updates, with open-source SDKs, flexible hosting, and production controls built for real apps.
02
Automatic or manual
Use the automatic path to install and ship in 5 minutes, or switch to manual and half-manual flows for custom rollout, support, QA, and per-user scenarios.
03
Most complete at scale
1B+ updates per month, 50M+ devices, dynamic channels, device logs, delta updates, encryption, self-hosting, and native recovery.
04
Safety before deploy
The CLI checks native dependencies, required files, bundle integrity, duplicate versions, and hub compatibility before updates reach users.
The Complete Live Update System
Most tools can upload files. Capgo adds the release controls, native safety, logs, and rollback behavior production teams need.
Breaking Update Detection
CLI scans native dependencies and warns you before deploying incompatible updates. Ship web changes fast without pushing native-breaking code to customers.
Pure Native Engine
Downloads, installation, and activation run on native OS threads. JavaScript crashes can't affect the update process.
Automatic Rollback
If your app doesn't call notifyAppReady() within 10 seconds, we automatically roll back to the last working version.
Self-Healing Updates
Fallback bundle mechanism always maintains a working version. Your users never see a broken app.
Pre-flight Validation
Validates notifyAppReady(), index.html, bundle size limits, and checksums before accepting any upload.
Tamper-Proof Updates
Every update is checksummed, signed, and encrypted end-to-end. No one can tamper with updates - not even Capgo can see what's inside your bundles.
Update observability
All device logs - no Xcode or Android Studio required
Capgo captures the full OTA journey: checks, downloads, installs, policy blocks, and rollbacks so you can answer “what happened?” in seconds, not hours.
- Per-device timelines highlight stalled downloads, checksum issues, or missing notifyAppReady().
- Channel guardrails proven: see disableAutoUpdateToMajor, emulator/dev blocks, and platform filters in real time.
- Detect blast radius fast: update_fail, rateLimited, needPlanUpgrade surface before users churn.
- Shared logs for engineering, QA, and support (no Xcode/Android Studio digging required).
14:30:02 device A1B2C3 download_start 2.6.0
14:30:07 device A1B2C3 update_fail (network_timeout)
14:30:08 device A1B2C3 auto-retry scheduled (30s)
14:31:15 device F0E1D2 update_fail (out_of_memory)
14:31:16 device F0E1D2 rollback → builtin bundle
Actionable context in one place: decide to rollback, bump a channel, or ship a hotfix with confidence.
Dynamic channels
Switch release tracks live (no new binary)
Capgo channels are live controls, not hardcoded. Move users between dev, staging, PR, canary, and production from your app UI or via API instantly.
- Add an in-app “Update Track” menu: list channels and let testers jump from production to staging in seconds (no reinstall).
- Spin up a pull-request channel per feature, route QA or beta users there, then snap them back to prod when approved.
- Run canaries: clone prod to a 10% channel, promote or rollback with a single API call.
- Unblock support: move one user to a debug channel that ships extra logging while everyone else stays stable.
- Create personal channels for individual users - perfect for debugging specific issues or VIP treatment.
- All channel changes are instant - no 24-hour wait, no store approval, no user action required.
user selects “Staging (v2.5.0-rc1)” setChannel
14:41:10 device A1B2C3 get → staging manifest
14:41:14 device A1B2C3 download_complete 2.5.0-rc1
14:43:02 support user Q7R8S9 setChannel → debug-logs
14:55:00 canary cohort auto-promoted to production
Treat environments like feature flags: switch, test, and rollback live (no store resubmissions).
Cloud-Native Configuration
Everything Lives in the Cloud
Capgo stores all your app configuration in the cloud with global data replication. Change a setting in the dashboard, and it takes effect worldwide in under 2 minutes. No app store updates, no waiting.
- Channel assignments, version targeting, and device overrides - all stored in the cloud and instantly accessible
- Global edge network ensures your configuration changes propagate to every region simultaneously
- No hardcoded values in your app - everything can be changed dynamically without a new binary
- Settings take effect on the next app launch - users always get the latest configuration
Configuration Change Timeline
1
Dashboard: Click "Assign to channel: beta-testers"
0s 2
Replication: Syncing to 12 edge regions...
~30s 3
Device (Tokyo): Receives new config
<2min 4
Device (Berlin): Receives new config
<2min From dashboard click to worldwide deployment in under 2 minutes.
Real-World Support
Fix One User's Bug in Minutes
Here's a real scenario: A user reports a bug. You talk with them, understand the problem, fix it in code, and deploy the fix to just that one user - all while they're still on the call. They test it, confirm the fix works, and you deploy to production. Total time: minutes, not days.
1. User Reports Bug
Customer support gets a bug report. You join the call to understand the issue.
2. Fix & Push to Them Only
Create a personal channel for that user, push the fix, and assign their device to it.
3. Verify & Ship to All
User confirms the fix works. Promote the bundle to production for everyone.
Support Session Timeline
10:15 User reports crash on checkout Bug
10:22 Dev joins call, reproduces issue Debug
10:35 Fix pushed to "user-john-hotfix" channel Deploy
10:36 Device assigned, update downloading Install
10:38 "It works!" - User confirms fix Verified
10:40 Bundle promoted to production Ship
From bug report to verified fix in one support call.
Delta Updates
Traditional updates download the entire bundle every time. With delta updates, devices only download the files that actually changed - saving 50-90% bandwidth.
File-Level Diffing
Each file is uploaded and checksummed individually. Devices compare manifests and only download changed files.
Perfect for Large Assets
Images, fonts, and videos are downloaded only once. Small code changes don't re-download your entire asset folder.
Enable with One Flag
Just add --partial to your upload command to enable delta updates for your bundle.
Terminal
# Upload with delta updates enabled
npx @capgo/cli bundle upload --partial
✔ Uploading 847 files...
✔ Generated manifest with checksums
✔ Bundle uploaded successfully
# Device downloads only changed files
→ Comparing manifests...
→ 12 files changed, 835 unchanged
✔ Downloaded 245 KB (vs 4.2 MB full bundle)Smart Channel System
Channels let you target specific user groups with specific builds. Manage channels from the cloud dashboard, API, mobile app, or your own advanced release logic.
Cloud Dashboard Control
Create, configure, and switch channels from the web dashboard. Roll back instantly with one click.
API & CLI Access
Automate channel management with our CLI or REST API. Perfect for CI/CD integration.
Device Self-Assignment
Let devices switch channels at runtime with setChannel(). Great for QA testers or beta programs.
Priority-Based Routing
Forced device > Cloud override > Config default > Cloud default. Full control over update routing.
Logs & Statistics
Real-time visibility into your update deployments. Track download progress, success rates, and device health across your entire user base.
Download Progress Tracking
See which devices are downloading, installed, or pending. Track progress across your entire fleet.
Success & Failure Rates
Monitor update success rates in real-time. Identify issues before they affect more users.
Device Health Monitoring
Track which devices are on which versions. Identify devices stuck on old versions.
Bundle Analytics
See bundle sizes, download times, and rollback frequency. Optimize your update strategy with data.
Long-Term Support
No pressure to upgrade immediately. Capgo officially supports Capacitor 8, 7, 6, 5 and Electron - giving you years of support and flexibility to upgrade on your own schedule.
New Electron Fully Supported
8 Capacitor 8 Fully Supported
7 Capacitor 7 Fully Supported
6 Capacitor 6 Fully Supported
5 Capacitor 5 Fully Supported
Deep Pre-Deployment Validation
Manual updates give you all the tools to break your app. Capgo's CLI catches incompatible native changes and release mistakes before they reach your users.
Native Dependency Check
CLI scans your native plugins and compares versions. If your JS bundle expects a newer native plugin version than what's installed, we warn you before deploy.
Duplicate Version Prevention
Already uploaded this exact version? We'll catch it and prevent accidental overwrites or confusion.
Hub-CLI Compatibility
Certain features require specific CLI versions. We validate compatibility between your CLI and the Capgo hub before allowing uploads.
Required Files Check
Missing index.html? No notifyAppReady() call? Bundle too large? We catch these issues before they become production problems.
What happens without validation?
Upload a JS bundle that expects native plugins your users don't have? Your app breaks. And if your rollback is also in JS, you have no way to recover. Users are stuck until they reinstall from the App Store.
How It Works
Automatic when you want speed. Manual when you need control. Safety checks at every step.
1
CLI Validates
Before upload, CLI checks native dependencies, version compatibility, and required files
2
Native Downloads
Pure native code downloads and installs the update - completely isolated from JavaScript
3
App Confirms Ready
Your app calls notifyAppReady(). If it doesn't within 10s, automatic rollback kicks in
Capgo vs Basic Update Systems
Uploading a bundle is easy. Protecting customers at scale is the hard part.
| Feature | Capgo | Manual / Others |
|---|---|---|
| Breaking update detection | ✓ | ✗ |
| Automatic rollback | ✓ | ✗ |
| Native crash recovery | ✓ | ✗ |
| Pre-deployment validation | ✓ | ✗ |
| Self-healing updates | ✓ | ✗ |
| Cloud rollback & modify | ✓ | ✗ |
Ready for the Most Complete Capacitor Live Update System?
Start automatic in 5 minutes. Switch to manual control when your release strategy needs it.