Set & Forget

Store releases are slow. Capgo updates are instant.

Install the native app once through your private store or MDM. After that, ship web fixes through Capgo, track who received them, and keep offline devices on the last good bundle.

Plan an Instant Rollout Read Live Update Docs

Capgo channels dashboard used to manage private enterprise app releases

Install once: Ship the signed native shell through your enterprise store or MDM.
Update during sync: Devices pull the latest bundle during scheduled sync windows, check-in time, or any available network window.
Run offline: The app keeps working from the cached bundle when the device is offline.

When every store release slows the team down

Store and enterprise package releases are slow to coordinate and hard to verify across every device. Capgo gives you an instant release path for the web layer, with channels, device logs, staged rollout, and rollback built in.

Install once: 1x
Update during sync: CI upload
Run offline: cached

The set-and-forget workflow

1
Ship the native shell once

Distribute the signed iOS or Android app through MDM, an enterprise app store, or your internal device provisioning flow.
2
Lock devices to the right channel

Use a default channel for production, then split by site, country, team, or hardware generation when needed.
3
Publish web updates from CI

Build, test, and upload the Capacitor web bundle to Capgo. Native code changes still go through your normal enterprise packaging process.
4
Let devices update when online

Devices fetch updates during planned connectivity windows and keep the last good bundle locally for offline use.
5
Watch, rollback, repeat

Use channels, device logs, staged rollout, and rollback so local teams are not asked to debug production installs.

Designed for offline enterprise constraints

Use Capgo as the release layer for web assets, not as a replacement for your native distribution process. Native binaries still move through your enterprise packaging flow.

Offline-first runtime: The app opens from the installed native shell and the last verified Capgo bundle, so users can keep working without a live connection.
Site-by-site control: Promote a release to one site first, validate it with a small group, then expand the same bundle to more locations.
Low-touch users: Users keep opening the same internal app. Updates download in the background when devices reach Wi-Fi or a scheduled sync window.
Audit-friendly releases: Engineering can see bundle versions, channels, rollout state, and device logs without asking local teams to troubleshoot.

Example implementation pattern

Use Capgo as the release layer for web assets, not as a replacement for your native distribution process. Native binaries still move through your enterprise packaging flow.

CI upload

# Build and publish the web layer
npx @capgo/cli@latest bundle upload --channel site-eu

# Promote after the first site validates it
npx @capgo/cli@latest channel set production com.enterprise.app --latest

App channel config

const config = {
  plugins: {
    CapacitorUpdater: {
      defaultChannel: 'production',
      autoUpdate: true,
    },
  },
}

What this is, and what it is not

Use this for private enterprise distribution through MDM, Apple Business Manager, Android Enterprise, or an internal enterprise store.
Capgo updates JavaScript, HTML, CSS, and assets. Native plugin changes still require a new signed native package.
Offline devices keep running the last successful bundle until they reconnect and fetch the next approved update.
This is not a consumer App Store bypass. It is a private-app operating model for teams that already self-distribute.

Real app examples

Account apps need quiet, automatic maintenance

Telecom and support apps have billing, plan, support, and device workflows that must stay current without asking users to install a new binary for every small improvement.

Example type: Set and forget
Store categories: PRODUCTIVITY, TOOLS, Tools
Source: Public store dataset

Install once, update automatically

Keep support flows current

Reduce manual release overhead