Capgo

Capgo delivers over-the-air updates to Capacitor applications through an architecture built on Supabase and edge runtime functions. It sends signed web assets directly to iOS and Android runtimes without waiting for app store reviews. Because both the backend and client plugin are open source, teams retain direct custody of the release pipeline.

Why Capgo instead of Appflow

Ionic Appflow operates as a proprietary cloud service where application bundles, signing keys, and device metadata transit Ionic-managed servers. For teams with strict compliance or data-residency mandates, routing mobile code through a closed SaaS introduces third-party dependency risks. Capgo eliminates this by making the entire distribution backend self-hostable on Supabase under private VPC control. Teams sign update bundles locally with their own cryptographic keys, maintaining complete data custody.

The operational scope also diverges. While Appflow includes cloud CI machines to compile native iOS and Android binaries, Capgo focuses strictly on over-the-air artifact delivery, differential synchronization, and channel orchestration. Engineering teams run native compilation in their standard CI/CD runners, using the Capgo CLI only to bundle, encrypt, and push web layers. With Appflow scheduled for sunset in 2027, Capgo provides an open-source migration path that removes vendor lock-in without sacrificing staged rollouts.

What it does well

• Self-hosted backend: Runs on Supabase PostgreSQL and Edge Functions, enabling deployment within private VPCs or internal networks.
• Differential synchronization: Computes file-level diffs so devices download only modified assets, minimizing cellular bandwidth during updates.
• Cryptographic validation: End-to-end encryption and digital signatures ensure update bundles cannot be tampered with in transit.
• Channel routing: Isolates releases into development, staging, and production channels, with overrides to target individual QA devices.
• Automated rollback: Automatically reverts the mobile app to the previous working bundle if a newly downloaded version crashes on startup.
• CI/CD integration: A dedicated CLI automates bundle packaging, signing, and channel deployment from GitHub Actions or GitLab pipelines.

Limitations

• No native code updates: Capgo only updates web-layer assets; changes to native plugins or SDKs still require standard app store submission.