Skip to main content
For startups

A mobile release pipeline without a platform team

Push web-layer fixes as live updates, build iOS and Android binaries in the cloud, and run both from the CI you already use. Your team stays on the product.

From $12/month billed yearly. 14-day free trial, no credit card.

Where startup time goes

Release work competes with product work

Store review sits on small fixes

A one-line JavaScript fix waits for a new binary and store review, often 24–48 hours, sometimes much longer. Then users still have to update.

Nobody owns the build machine

iOS builds need a Mac, signing certificates, and provisioning profiles. On a small team, that work lands on whoever is free that day.

A bad release is hard to undo

Without a rollback path, a broken screen stays live until the next binary is approved and installed.

What Capgo covers

Live updates, native builds, and CI in one tool

The parts of a release pipeline a small team would otherwise build and maintain.

Ship web-layer changes the same day

Upload a new JavaScript, HTML, and CSS bundle with one CLI command. Devices download it in the background and apply it on the next launch. Native changes still go through the stores.

Live updates docs

Upload from the CI you already use

Add one upload step to your pipeline. Every merge to main can publish a bundle to the right channel.

CI integration docs
  • GitHub Actions, GitLab CI, Bitbucket, and Azure DevOps
  • Separate staging and production channels
  • Delta updates that send only changed files

Roll out gradually, roll back automatically

Send a bundle to a share of devices first. If a new bundle never calls notifyAppReady(), the device goes back to the last working version on its own.

Progressive rollout docs

Native builds without a Mac

Capgo Build compiles iOS and Android apps in the cloud and can upload them to App Store Connect and Google Play. A typical build takes 2–3 minutes.

Capgo Build docs
  • iOS builds on Capgo's Mac machines
  • Signing credentials saved once with the CLI
  • Store upload from the same command

How it works

How a startup team ships with Capgo

From the first upload to a CI pipeline. Every command below is from the Capgo CLI docs.

  1. Add Capgo to your app

    The init command walks you through adding the updater plugin, building, and uploading your first bundle.

    npx @capgo/cli@latest init
    Quickstart

  2. Upload from CI

    Save your Capgo API key as CAPGO_TOKEN in your CI secrets and add one upload step after the web build.

    # After your web build, with CAPGO_TOKEN set in CI secrets
npx @capgo/cli@latest bundle upload --channel production
    GitHub Actions guide

  3. Roll out to a share of users

    Send the new bundle to 10% of production devices. Promote it to everyone when install and failure data look right.

    npx @capgo/cli@latest bundle upload --channel production --rollout 10
npx @capgo/cli@latest channel set production --rollout-promote
    Progressive rollout docs

  4. Build native binaries in the cloud

    Save your signing credentials once, then request iOS and Android builds from your laptop or from CI.

    npx @capgo/cli@latest build credentials save --appId com.example.app --platform ios
npx @capgo/cli@latest build request com.example.app --platform ios
    Capgo Build docs

Apps built with Capacitor

Audience apps need rapid product iteration

Interactive, education, and survey apps can tune onboarding, live event flows, and engagement prompts every week. Startups can use Capgo to learn faster without turning every experiment into a store release.

Poll Everywhere app icon BUSINESS

Poll Everywhere

Live audience app where activation and event-flow experiments need quick turns.

Google Play installs
1.1M
Store rating
3.2
StudySmarter - School & uni app icon EDUCATION

StudySmarter - School & uni

Learning app where onboarding, study paths, and subscription surfaces need iteration.

Google Play installs
6.5M
Store rating
4.8
Poll Pay: Money for Surveys app icon LIFESTYLE

Poll Pay: Money for Surveys

Survey app where rewards and engagement prompts can be adjusted frequently.

Google Play installs
11.3M
Store rating
4.4

Customer proof

What teams shipping with Capgo say

5.0/5 rated by developer teams 9,400+ teams Read reviews

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.”

Nate van Jole

CTO, Private

“Getting set up took less than a day. Channel-based rollouts let me test on my own device before anything hits production users.”

sikafanka

Design, radius 5

“Capgo Build helped us simplify our Capacitor app release process. We can build and ship iOS and Android apps from one clear workflow.”

FAQ

Startup questions

What small teams ask before adding Capgo to their release process.

How much does Capgo cost?

Plans start at $12/month billed yearly, or $14 billed monthly. Every plan starts with a 14-day free trial, no credit card needed. There is no free plan.

See pricing

Do we need a DevOps engineer to set this up?

No. Setup is the init command plus one upload step in your CI. Capgo runs the update servers, the bundle storage, and the build machines.

CI integration docs

What can we ship without a store review?

Changes to JavaScript, HTML, CSS, and assets. Native code, new plugins, and permission changes need a new binary. Capgo checks bundle compatibility with the native side before upload.

Native compatibility docs

What happens if we ship a broken update?

If the new bundle does not call notifyAppReady() within 10 seconds, the device goes back to the previous working version. You can also point a channel back to an earlier bundle.

Rollback docs

Do we need a Mac for iOS builds?

No. Capgo Build runs iOS builds on Capgo's Mac machines and can upload the result to App Store Connect.

iOS build docs

Try the full pipeline on your app

During the 14-day trial, run init, upload a bundle from CI, and request a cloud build.