Skip to main content

For teams that just found a security hole

Found a security hole in your app? Fix it for every user today.

With Capgo, a fix in your web code reaches users at their next app open, not after days of store review. Every update is end-to-end encrypted and signed, so nobody can read or fake it on the way.

Same day
from fix to users’ phones
End-to-end
encrypted, signed bundles
SOC 2 Type II
and ISO 27001 certified
Capgo Live Updates 
npx @capgo/cli@latest bundle upload --channel=production
# encrypted and signed with your private key
# checksum verified on every device
# fix live at the next app open

Fix in your web code

JavaScript, HTML, CSS and assets ship as a live update.

No store review wait

Apple and Google allow web code updates without a new review.

The Problem

A security hole in a shipped app stays open for days

Apps ship fast, with holes

AI-built and rushed apps ship with exposed API keys, open database rules and old vulnerable packages. Attackers now scan app stores for them.

Store review keeps the hole open

Even with a fix ready, App Store or Play Store review can take a day or more. Meanwhile users keep running the vulnerable version.

Users don’t update

Many users wait weeks before installing a new store version, so the vulnerable build keeps running on their phones.

Without Capgo

How a security fix usually reaches users

Each step adds hours or days while the hole stays open.

1

Build and sign a new native version

Bump the version, build for iOS and Android, sign both and upload them.

2

Wait for store review

Apple and Google review the new build. A fast review is never guaranteed.

3

Wait for users to update

Users install the new version when they choose to, if they ever do.

How it works

Ship a security fix the same day

You need a Capacitor app with the Capgo updater installed. Every command below is from the Capgo CLI docs.

  1. Turn on end-to-end encryption once

    Create your key pair. The private key stays on your machine and the public key is saved in your app config.

    npx @capgo/cli@latest key create
npx @capgo/cli@latest key save
    Encryption docs

  2. Fix the code and upload it

    Patch the vulnerable code or update the package, build your web app and upload it. The CLI encrypts and signs the bundle before it leaves your machine.

    npm run build
npx @capgo/cli@latest bundle upload --channel=production
    bundle upload reference

  3. Install the fix right away

    Set autoUpdate to always and the app installs the fix as soon as it downloads, instead of waiting for the next restart.

    // capacitor.config.ts
plugins: {
  CapacitorUpdater: {
    autoUpdate: 'always',
  },
}
    Update behavior docs

  4. Check who has it, roll back if needed

    See which devices installed the fix in the dashboard. If the fix breaks something, go back to the previous bundle.

    Rollback docs

The Solution

Why Capgo is safe to ship security fixes with

An update system can be attacked too. Capgo is built so it cannot push code that you did not sign.

End-to-end encrypted bundles

Bundles are encrypted before they leave your machine and decrypted only inside your app. Capgo, its storage and its CDN see only encrypted files.

Encryption docs

Signed and checked on every device

Each bundle has a checksum signed with your private key. The app checks it before installing, and deletes any changed or fake bundle without running it.

Encryption docs

Your private key never leaves your machine

The CLI never sends your private key to Capgo, and Capgo does not store it. Without it, nobody can publish a valid encrypted update to your app.

bundle upload reference

Native fixes, built fast

Live updates change web code only. A fix in native code still needs a signed store build, and Capgo Build makes that build in minutes, without a Mac.

Capgo Build docs

Security and compliance

Certified, and open to review

Check how Capgo works instead of taking our word for it.

SOC 2 Type II and ISO 27001

Capgo is SOC 2 Type II and ISO 27001 certified. See the reports at trust.capgo.app.

Open trust.capgo.app

Open source updater and CLI

The Capgo updater plugin and CLI are open source, so your security team can review the exact code that runs in your app.

Free security scanner

Scan your Capacitor app for hardcoded secrets and risky settings with the Capgo security scanner, then ship the fixes the same day.

Run the security scanner

Apps built with Capacitor

Banking apps need safe, staged interface fixes

Banking and money apps with accounts, payments, offers, investments, and support flows have to move quickly while preserving trust. Capgo fits fixes that can be shipped through the approved web layer and expanded gradually.

Vyom - Union Bank of India app icon FINANCE

Vyom - Union Bank of India

Banking app with account, payment, loan, and offer flows that need controlled rollout.

Google Play installs
28.0M
Store rating
3.7
IndOASIS Indian Bank MobileApp app icon FINANCE

IndOASIS Indian Bank MobileApp

Mobile banking surface where reviewed interface changes should expand gradually.

Google Play installs
15.4M
Store rating
4.2
Orange Money Sénégal app icon FINANCE

Orange Money Sénégal

Wallet app where support copy and transactional UI changes need caution.

Google Play installs
2.6M
Store rating
4.0

Customer proof

What teams shipping with Capgo say

5.0/5 rated by developer teams 9,400+ teams Read reviews
Portrait of Sergiu S

Sergiu S

Lead Developer, drivolino GmbH

“The Capgo Capacitor Updater plugin completely transformed how we ship updates. What used to take days now takes just minutes.”

no-tone @ Webincode

Developer, Webincode

“Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.”

Kapil

Founder, NuTriQ

“Being able to push production OTA updates instantly without waiting for full App Store review cycles has been a massive operational advantage.”

FAQ

Security fix questions

What live updates can fix, and what they cannot.

Can I ship a security fix without App Store review?

Yes, when the fix is in your web code: JavaScript, HTML, CSS or assets. Apple and Google allow apps to update this code without a new review, as long as the app’s main purpose stays the same. A fix in native code needs a new store build.

Store compliance docs

How fast does the fix reach users?

The app downloads the fix in the background and installs it at the next app open. With autoUpdate set to always, it is installed as soon as it downloads, so active users get it the same day.

Update behavior docs

Can an attacker use Capgo to push code to my app?

Not without your private key. With encryption on, the app installs only bundles whose signed checksum matches your key, and deletes any other bundle.

Encryption docs

Does encryption stop people from reading my app’s code?

No. Encryption protects bundles in storage and on the way to devices. The key that decrypts them is inside your app, so someone with your app can still read the code. Never put secrets in your web code.

Encryption docs

What if the fix breaks something?

Go back to the previous bundle from the dashboard or the CLI. You can also send the fix to a small group first with a channel, then to everyone.

Rollback docs

Be ready before the next security hole

Set up Capgo during the 14-day free trial, so your next security fix takes minutes to ship, not days. Set up Capgo with a 14-day money-back guarantee, so your next security fix takes minutes to ship, not days.