Skip to main content
Capgo logo
14-day free trial · no credit card

Capgo Builder Signed iOS & Android builds · one command · from any machine

Capgo Builder takes your Capacitor project and ships a signed, store-ready iOS or Android build with one command. No Mac mini in a closet, no Android SDK installs, no Xcode tantrums, no lost keystores late on a Friday night.

Start 14-day free trial See how it works ↓
✓ iOS · Apple Silicon ✓ Android · Docker ✓ No Mac, no Android SDK ✓ Avg build 2–3 min
Capgo Builder

One command, signed iOS and Android builds — straight to the stores, from any machine.

capgo build request --platform ios
Switch between iOS and Android · Replay to watch again
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. iOS and Android, treated as equals. Apple Silicon for iOS, Docker for Android. App-Store + Play-Store-ready output. Zero credentials stored. Streaming logs. QR-code APK download.
$ 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.

Right hardware per platform

Apple Silicon for iOS. Linux Docker for Android.

iOS jobs run on M4 Mac runners — fast Xcode + Fastlane. Android jobs run on Linux Docker — fast Gradle, roughly half the cost of iOS, no Mac required. 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 straight to your terminal — 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

Product flavors, keystores, Cordova plugins — auto-handled.

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

One .p8 for iOS. One Google sign-in for Android. That's it.

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 the keyboard: Tab, then Enter.

60 seconds, both platforms

Setup in 60 seconds.

Run it once for iOS, once for Android. Drop one .p8 for Apple, sign in once with Google for Play. Capgo handles certs, profiles, keystores and service accounts — everything you would normally do by hand in two consoles.

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

Your secrets stay your secrets.

We are a build service, not a credential store. Here is exactly what we do — and don't — touch.

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 are streamed to a per-build ephemeral environment, used for that build, and wiped at job end.

Logs

Logs never touch Capgo servers.

Build output streams straight to your terminal — nothing written to our disks, nothing retained, nothing searchable by us.

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 Capawesome Cloud
Setup time ~60 seconds. capgo build init takes one .p8 and creates the CSR, distribution certificate, P12, bundle ID and provisioning profile for you. Days. Write the Fastlane lane, manage signing yourself, wire up secrets, debug runner failures. You generate certs and profiles in Apple Developer Portal, upload .p12 + .mobileprovision via their dashboard, 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. Capawesome connects to GitHub / GitLab / Bitbucket / Azure DevOps and clones your entire repository on every build.
Credential storage Never persisted on our servers. Credentials live on your machine, are sent only to the active build environment, and are deleted within 24 hours — even if the build fails. Stored in your CI provider's secret store (GitHub Secrets, GitLab CI Variables). One more vault to audit. Stored on Capawesome's servers, encrypted at rest. You are trusting their key management indefinitely.
Build log storage Not stored. Logs stream live to your terminal over WebSocket and disappear when the build ends. Sensitive output never lands in a database. 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, ship — plans start at $14/mo with native builds and over-the-air updates included. "Free" until you exceed your runner minutes — then macOS gets expensive fast. $19/mo minimum — and over-the-air updates are a separate paid add-on. Free tier only by applying to their open-source program.
Cost per build Plan minutes, then credits. Build minutes are included in your plan; when you need more, top up with prepaid credits priced in volume tiers — no surprise per-minute bills. ~$4–5 in macOS minutes alone on GitHub-hosted runners (macOS-large at $0.08/min × 10× multiplier × ~6 min). Before you count engineer time. Metered against monthly build minutes on your tier; overage policy not publicly listed.
Live (OTA) updates Included. Over-the-air JS, CSS and asset updates ship with every Capgo plan — same account, no add-on. Not included — OTA is a separate system you would build or buy yourself. 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 per month, every month. Cert renewals, Apple API changes, runner image drift, Gradle plugin updates — all yours forever. Zero. They maintain the platform.
AI build debugging Right in the CLI. When a build fails, the CLI offers to run Capgo AI on the spot — it reads the log and hands you the cause and the fix, without leaving your terminal. You read the raw logs yourself and search the errors. Capawesome's 'Ask AI' does this too — but as a manual button in the web dashboard, not inline in the CLI where you build.

Comparison reflects publicly published Capawesome documentation and pricing. GitHub Actions macOS pricing per github.com/pricing. Agent tooling per each project’s public skills / MCP repositories.

When a build breaks

Build fails? AI tells you why — and how to fix it.

Native builds fail in cryptic ways — a missing entitlement, a Gradle clash, an expired profile. So when a Capgo build fails it simply asks: want Capgo AI to read the log and point you to the likely cause and fix? Or hand the prompt to your own AI, or skip it. 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

    What actually went wrong — 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.

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

Solo
$12 / mo

Best for independent developers

Billed annually at $146

$14 month-to-month

14-day free trial
  • 30 build minutes
  • 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
  • 1 build hour
  • 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
  • 5 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
  • 16 build hours+
  • Capgo over-the-air updates included
How far do build minutes go?
60 build minutes / month
12iOS builds
24Android builds
≈ $10 in prepaid credits

Rough guide: an iOS build uses about 5 build-minutes (Apple Silicon), Android about 2.5 (Linux Docker). Real builds run 2–3 minutes; iOS minutes bill roughly 2× Android. Plan minutes are included free — the price shows what the same minutes would cost as prepaid top-up credits.

Build minutes are included in every plan; extra minutes are prepaid credits with volume pricing. Final tiers live 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 for each target. We support multi-target signing as a first-class flag, including the main app, widget extensions, notification service and share extensions.
Do you handle Cordova plugins in Capacitor projects? +
Yes, automatically. We parse capacitor-cordova-android-plugins/build.gradle and bundle the right plugin sources into the Android build — no manual config.xml wrangling.
Can I build Android product flavors? +
Yes — pass --android-flavor production (or any other flavor your build.gradle declares). Keystores and the Play service-account JSON are passed via flags.
I want internal-only iOS builds without TestFlight. How? +
Use --ios-distribution ad_hoc. We skip App Store Connect validation and produce an IPA you can distribute through your own MDM or a token-protected download link with a 1h–7d TTL.
What's your retention policy on logs and artifacts? +
Logs are never stored on Capgo servers — they stream directly from the runner to your terminal, then disappear. Build artifacts default to a 1-hour TTL (extendable to 7 days). Credentials are wiped from the build environment the moment the build ends.
Is Capgo Builder a replacement for live updates? +
No — they are complementary. Use Capgo Live Updates for JavaScript, CSS and asset changes you can ship instantly over the air. Use Capgo Builder when you change native code, plugins, permissions, icons or SDKs and need a fresh signed binary for the stores.

Capgo Builder
Native builds without the pain.

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

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