For teams without a dedicated mobile CI owner
Avoid maintaining macOS runners, Android toolchains, provisioning profiles, and store upload scripts just to produce release binaries.
Native iOS and Android builds from any machine
Capgo Builder
One command for signed iOS and Android builds, store submission, and live build logs without maintaining native toolchains on every machine.
No credit card required for the free trial.
1 command
Local, CI, or teammate laptop
0 stored
Credentials kept runtime-only
iOS + Android
Signed native builds
Stores
Submit after a clean build
Buying guide
Native builds should remove release work, not replace your whole pipeline.
Capgo Builder is positioned for teams that want the boring, failure-prone native release work handled for them while keeping source control, CI, and release ownership.
For teams already using GitHub Actions or GitLab
Keep your existing workflow and call Capgo only for the native build, signing, artifact, or submit step.
For agencies and multi-app teams
Standardize builds across client apps without rebuilding the same iOS and Android release pipeline for every project.
One command
Signed native builds, straight to the stores.
Run the same build command locally or in CI. Capgo Builder handles the native build job, streams logs, signs the artifact, and can submit it after success.
capgo-builder.log
# Build and submit a signed iOS app
bunx @capgo/cli build com.example.app \
--platform ios \
--build-mode release \
--submit
ok Creating build job
ok Uploading native project inputs
run Installing native dependencies
run Building on Mac Mini Silicon M4
run Signing IPA from runtime credentials
ok Build succeeded
ok Submitted to App Store Connect
Build infrastructure
Built on Mac Mini Silicon M4.
Capgo Builder runs native build jobs on dedicated Apple Silicon machines with the mobile SDKs already installed, so teams get repeatable iOS and Android output from any local or CI trigger.
- Machine
- Mac Mini Silicon M4
- CPU
- 10-core M4 CPU (4 performance cores, 6 efficiency cores)
- GPU
- 10-core GPU
- Neural Engine
- 16-core Neural Engine
- Memory
- 16GB of RAM
- OS image
- macOS Tahoe 26.2
Toolchain support includes Xcode 26.2, Android Studio 2025, and .NET 9/.NET 10 SDK workloads for native build pipelines.
Built for shipping
No native build babysitting.
Capgo Builder focuses on the work between a native change and a store-ready artifact.
Native builds without the native setup
Build on dedicated Mac Mini Silicon M4 machines without installing Xcode or Android Studio everywhere.
Bring your own signing
Certificates, provisioning profiles, and keystores are supplied at build time from local env vars or CI secrets.
Upload to the stores
Ship signed artifacts to App Store Connect and Google Play from the same command that produced the build.
Works in any CI
Run from GitHub Actions, GitLab CI, Jenkins, local scripts, or a teammate machine. No repo access required.
Live logs in your terminal
Stream every build step as it happens, so failures are visible where the command was started.
Clean build artifacts
Download IPA, AAB, or APK output when you need it, while keeping the build environment disposable.
Setup
Setup in 60 seconds.
Add the command to a local script or CI job, pass signing values from secrets, and keep native release builds reproducible.
bunx @capgo/cli build com.example.app --platform android
- 1
Install the Capgo CLI in your project workflow.
- 2
Point the command at your app id and target platform.
- 3
Pass signing values from your secrets manager.
- 4
Stream logs until the signed artifact is ready.
Security model
Your secrets stay your secrets.
Capgo Builder is designed for teams that already treat signing material as sensitive CI data.
Credentials stay runtime-only
Signing material is used during the build and is not kept as stored Capgo data.
Only native build inputs upload
Capgo Builder receives the platform folder and built web assets needed for the requested native target.
Ephemeral build environments
iOS and Android jobs run in isolated environments designed around short-lived build execution.
Logs stream back to you
Build output is delivered to the running command so teams can debug without a separate dashboard loop.
Comparison
Capgo Builder vs. alternatives.
Keep the native build path simple when your team mainly ships Capacitor apps.
First setup
- Capgo Builder
- One CLI command after signing values are available.
- Local native builds
- Install Xcode, Android Studio, SDKs, Ruby, Gradle, and signing files per machine.
- Generic CI
- Maintain runners, images, certificates, and store upload scripts.
iOS from any OS
- Capgo Builder
- Trigger iOS builds from macOS, Linux, Windows, or CI.
- Local native builds
- Requires macOS hardware for iOS output.
- Generic CI
- Requires macOS runners and queue management.
Credential handling
- Capgo Builder
- Use existing local or CI secrets at build time.
- Local native builds
- Each build machine needs secure local signing setup.
- Generic CI
- Secrets must be wired into every pipeline path.
Store delivery
- Capgo Builder
- Build and submit from the same workflow.
- Local native builds
- Manual export and upload steps are common.
- Generic CI
- Possible, but you own the automation.
Best fit
- Capgo Builder
- Capacitor teams that want signed native builds without babysitting native toolchains.
- Local native builds
- Native specialists working inside Xcode or Android Studio every day.
- Generic CI
- Teams with dedicated DevOps ownership for mobile runners.
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
Best for independent developers
$12 /mo
Billed annually at $146
$14 month-to-month
14-day free trial- + 30 build minutes
- + 2,000 monthly active users
- + 100 GiB bandwidth/month
- + 20 GiB storage
Most Popular
Maker
Best for small business owners
$33 /mo
Billed annually at $396
$39 month-to-month
14-day free trial- + 1 build hour
- + 10,000 monthly active users
- + 1,000 GiB bandwidth/month
- + 50 GiB storage
Team
Best for medium enterprises
$83 /mo
Billed annually at $998
$99 month-to-month
14-day free trial- + 5 build hours
- + 100,000 monthly active users
- + 2,000 GiB bandwidth/month
- + 100 GiB storage
Enterprise
Best for Enterprise with millions of users
$208+ /mo
Billed annually from $2,490
$249+ month-to-month
14-day free trial- + 16 build hours+
- + 1,000,000 monthly active users
- + 20,000 GiB bandwidth/month
- + 200 GiB storage
Extra build minutes use prepaid credits.
First 100: $0.16/min Next 400: $0.14/min Next 500: $0.12/min Next 4k: $0.1/min Next 5k: $0.09/min Over 10k: $0.08/min
FAQ
Specific answers to specific worries.
Is Capgo Builder a replacement for live updates? +
No. Use live updates for JavaScript, CSS, and asset changes that do not require store review. Use Capgo Builder when native code, plugins, permissions, icons, SDKs, or store binaries change.
Do you need access to my repository? +
No. The CLI uploads the build inputs from the machine or CI job where it runs. Private dependencies should already be installed before the build command starts.
How does signing work? +
You provide certificates, provisioning profiles, keystores, and store credentials through CLI flags or environment variables. Teams usually source them from their CI secret manager.
How does pricing work? +
Build minutes are included in paid Capgo plans, and extra minutes are available through prepaid credits. Builds run on Mac Mini Silicon M4 machines with native mobile toolchains already installed.
What platforms are supported? +
Capgo Builder supports iOS and Android builds for Capacitor apps, including store submission workflows and downloadable signed artifacts.
Capgo Builder
Native builds without the pain.
Build signed iOS and Android releases from your machine or CI while keeping Capgo's existing site header, docs, and pricing flow.