Skip to main content
Capgo Builder

Ship without the Mac One command. Straight to the stores.

Signed iOS and Android CapacitorJs builds from any machine.

14-day unlimited free trial. No credit card required.

iOS · Apple Silicon Android · Apple Silicon No Mac, no Android SDK Avg build 2-3 min
Capgo Builder

One command, from any machine, straight to the stores

capgo build request --platform ios
Switch between iOS and Android · Replay to watch again
From Martin

Why we built Capgo native builds

Capgo founder Martin on turning Capacitor projects into signed iOS and Android releases without asking you to hand over your App Store credentials.

Martin, Founder, Capgo

Builder proof

Teams already shipping with Builder

Short notes from Capacitor teams using Capgo for builds and releases.

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

sikafanka Design, radius 5

We originally discovered Capgo through its plugins, and that turned out to be a great entry point into a much more efficient release process for our team.

Mikołaj Wilczek Principal Mobile Platform Engineer, Tellent
What's in the box

Built for shipping, not babysitting.

Click any tile to see exactly what's behind it.

Capgo Builder
Native builds without the pain.
One CLI for iOS and Android on Apple Silicon. Store-ready output, live logs, no stored credentials.
$ capgo build request --platform ios      ✔ 2m 41s
$ capgo build request --platform android  ✔ 1m 22s

One CLI command

Same flag, both platforms. Build, sign, ship.

capgo build request --platform ios archives, signs and uploads to TestFlight. --platform android assembles, signs with your keystore and uploads to Play. One CLI, identical UX.

Apple Silicon runners

M4 Mac runners for iOS and Android. Fast, consistent builds.

iOS and Android jobs run on M4 Mac runners with fast Xcode, Gradle, and Fastlane. You don't pick the runner; we do, by platform flag.

Zero-trust security

Credentials never stored. Deleted after every build.

Credentials live locally at ~/.capgo-credentials/credentials.json, are sent only to ephemeral build envs over HTTPS, and are wiped the instant the build ends. Logs stream to your terminal and are never written to Capgo disk.

Direct store upload

Straight to App Store Connect / TestFlight and Play Console.

Default app_store distribution uploads straight to App Store Connect / TestFlight via Fastlane; Android bundles go to the Play Console. Pick ad_hoc for internal-only iOS builds. Skips ASC validation.

Live build logs

Stream build output in real time over WebSocket.

Logs stream over WebSocket with heartbeat + ack. A qr_download_link message renders a scannable QR + URL for APK / IPA downloads right in your terminal.

Android flavors + Cordova

Flavors, keystores, and Cordova plugins handled automatically.

--android-flavor production for any flavor your build.gradle declares. We auto-detect Cordova plugins from capacitor-cordova-android-plugins/build.gradle. No manual config. Keystore + Play service-account JSON passed by flag.

Setup in 60 seconds

Optional .p8 for iOS, or we create one for you. One Google sign-in for Android.

bunx @capgo/cli@latest build init --platform ios|android launches a wizard. iOS: drop a .p8 → CSR, certificate, P12, bundle ID, provisioning profiles, all auto. Android: one OAuth click → Play Console project, service account, keystore, all auto. Resumable, Ctrl-C-safe, runs the same in CI.

CI/CD ready

Works in GitHub Actions, GitLab and Bitbucket. No interactive input.

Single command, environment-variable-driven. No TTY, no prompts. Drop it into your existing pipeline and the same wizard-generated credentials work non-interactively.

Tap any tile to expand, or use Tab then Enter.

60 seconds, both platforms

Setup in 60 seconds.

One .p8 for iOS, one Google sign-in for Android. Capgo handles certs and keys.

$ bunx @capgo/cli@latest build init --platform ios
Before: 10+ Apple Developer Portal steps · CSRs · profiles After: drop one .p8

Guided App Store Connect key creation runs on macOS.

New · works in your AI editor

Don’t feel like doing the setup yourself? Just ask AI to do it.

Capgo MCP ships in the CLI. Install it in your editor, ask in plain language, and it runs keystore, signing, Play, and your first build. You only approve Google sign-in.

1Install Capgo MCP in your AI tool
+ any supported MCP client
Codex · --client codex
                        
  npx install-mcp 'npx @capgo/cli@latest mcp' --client codex

                      
2Then just ask
you Help me set up Capgo Builder
  • Runs keystore, signing, Google Play, and your first cloud build from chat
  • Credentials stay on your machine. Secrets are never echoed back.
  • install-mcp writes the client config; Capgo tools still run through @capgo/cli

Your agent uses Capgo tools, stops at human gates, and cannot fake a passing build. It can debug failures too.

Trust model

Your secrets stay your secrets.

We build apps. We never store your credentials.

Storage

Credentials live on your machine, not ours.

Stored locally at ~/.capgo-credentials/credentials.json. Capgo servers never persist them.

Transit

HTTPS to ephemeral build envs only.

Credentials stream to a per-build env, are used once, and wiped at job end.

Logs

Logs never touch Capgo servers.

Build output streams to your terminal only. Nothing is written to our disks or retained.

Isolation

Build envs destroyed after every build.

Zero log storage by default. Zero artifact storage by default. Both are opt-in, with explicit TTLs.

Honest comparison

Capgo Builder vs. the alternatives.

Same builds. Less to trust.

Capgo Builder DIY CI/CD GitHub Actions / Bitbucket / GitLab Competitor cloud
Setup time ~60 seconds. capgo build init takes one .p8 and creates CSR, cert, P12, bundle ID, and provisioning profile. Days. Write the Fastlane lane, manage signing yourself, wire up secrets, debug runner failures. Generate certs in the portal, upload .p12 and profiles, connect a Git repo.
Source code access Zero. The CLI zips only the files needed to build and uploads them to a one-shot runner. We never see your repo. Lives on your runner. Your control, your responsibility. Required. Clones your full repo from Git hosting on every build.
Credential storage Never persisted on our servers. Credentials stay on your machine, reach only the active build env, and are deleted within 24 hours, even after failed builds. Stored in your CI provider's secret store (GitHub Secrets, GitLab CI Variables). One more vault to audit. Stored on the vendor's servers, encrypted at rest. You trust their key management.
Build log storage Not stored. Logs stream to your terminal over WebSocket and disappear when the build ends. Retained by your CI provider for ~90 days. Visible to anyone with repo access. Persisted in their database for 30-90 days depending on plan.
Try before you pay Yes. 14-day free trial, no credit card. Sign up, run capgo build request, and ship. Plans from $14/mo with native builds and live updates included. "Free" until runner minutes run out, then macOS billing adds up fast. $19/mo minimum. Live updates are a separate add-on. Free tier needs their open-source program.
Cost per build Plan minutes, then credits. Plan minutes included. Top up with prepaid credits in volume tiers. No surprise per-minute bills. ~$4-5 in macOS minutes on GitHub runners alone, before engineer time. Metered against monthly build minutes on your tier; overage policy not publicly listed.
Live (OTA) updates Included. OTA JS, CSS, and asset updates ship with every Capgo plan. Same account, no add-on. Not included. Build or buy OTA separately. A separate paid add-on, billed on top of builds.
Time to maintain Zero. We maintain the build system, Fastlane templates, runner images and certificate refresh logic. Hours every month: cert renewals, API changes, runner drift, Gradle updates. All on you. Zero. They maintain the platform.
AI build debugging Right in the CLI. On failure, the CLI offers Capgo AI: reads the log and returns cause and fix without leaving your terminal. You read the raw logs yourself and search the errors. Dashboard AI only, not inline in the CLI where you build.

Based on public competitor cloud docs and pricing, plus GitHub Actions macOS rates.

When a build breaks

Build fails? AI explains why and how to fix it.

Capgo AI, your AI, or skip. Always your choice.

capgo build request --platform ios
$ capgo build request --platform ios [CapApp] Creating App.xcarchive ✖ Archive failed: Command CodeSign failed with a nonzero exit code   error: No profile matching 'com.acme.app' found for team ABC123 ? Choose AI analysis (optional) Capgo AI   Local AI · write the prompt to a file   Skip Capgo AI finished ◆ Likely cause Your App Store provisioning profile doesn't include the bundle ID com.acme.app. ◆ Fix Regenerate the profile for that bundle ID, or run capgo build init --platform ios to recreate certificate + profile automatically, then re-run the build.
Optional. Only runs if you choose Capgo AI.
  • Plain-language cause

    Plain-language cause, not just the red error line.

  • A concrete fix

    The exact flag, file or setting to change, copy-paste ready.

  • Always optional

    On failure you pick: Capgo AI, a prompt for your own AI, or skip. Never forced, never automatic.

Pricing

Pay for build minutes. That's it.

Capgo plans include native build minutes. Start with a 14-day free trial, then pick monthly or annual billing.

Solo
$12 / mo

Best for independent developers

Billed annually at $146

$14 month-to-month

14-day free trial
  • 1 build hour
  • Capgo over-the-air updates included
Maker · Most Popular
$33 / mo

Best for small business owners

Billed annually at $396

$39 month-to-month

14-day free trial
  • 2 build hours
  • Capgo over-the-air updates included
Team
$83 / mo

Best for medium enterprises

Billed annually at $998

$99 month-to-month

14-day free trial
  • 10 build hours
  • Capgo over-the-air updates included
Enterprise
$208+ / mo

Best for Enterprise with millions of users

Billed annually from $2,490

$249+ month-to-month

14-day free trial
  • 333 build hours+
  • Capgo over-the-air updates included
How far do build minutes go?
60 build minutes / month
12 iOS builds
24 Android builds
$10 in prepaid credits

Guide: iOS ~5 build-minutes, Android ~2.5, both on M4 Macs. Typical builds take 2-3 minutes. iOS minutes bill ~2x Android. Plan minutes are free; price shows prepaid top-up cost.

Build minutes are included in every plan. Extra minutes use prepaid credits. Final tiers at capgo.app/pricing.

FAQ

Specific answers to specific worries.

Can you sign apps with widget + notification-service extensions? +
Yes. Pass --ios-provisioning-profile bundleId=path per target, including widgets, notification service, and share extensions.
Do you handle Cordova plugins in Capacitor projects? +
Yes. We parse capacitor-cordova-android-plugins/build.gradle and bundle the right plugin sources. No manual config.xml work.
Can I build Android product flavors? +
Yes. Pass --android-flavor production or any declared flavor. Keystore and Play JSON via flags.
I want internal-only iOS builds without TestFlight. How? +
Use --ios-distribution ad_hoc. Skips App Store Connect validation. IPA for MDM or token download (1h-7d TTL).
What's your retention policy on logs and artifacts? +
Logs never stay on Capgo servers. They stream to your terminal, then disappear. Artifacts default to 1-hour TTL (up to 7 days). Credentials wiped when the build ends.
Is Capgo Builder a replacement for live updates? +
No. They complement each other. Live Updates for JS, CSS, and assets. Builder when native code, plugins, permissions, icons, or SDKs need a new signed binary.

Capgo Builder
Native builds without the pain.

One command. iOS and Android, treated as equals. From any machine.

Start building →
No credit card to start 14-day free trial Cancel anytime