Skip to main content
Stop Manual Native Builds

Still Building iOS & Android
Apps Manually?

Hours wasted on manual builds. Different environments causing bugs. Team members waiting for builds. Your productivity suffers with every manual deployment.

What if builds happened automatically on every commit?

Capgo Build lets your CI/CD pipeline trigger signed iOS and Android builds in the cloud, then download artifacts or submit them to the stores.

Capgo Build • iOS & Android CI/CD • GitHub Actions-ready

The Native Build Nightmare

Every mobile developer knows the pain of manual builds. Here's how Capgo Build fits into CI/CD.

Without CI/CD

Hours of manual building

Developers waste time on repetitive build processes

Environment inconsistencies

"Works on my machine" bugs from different build environments

Certificate & signing chaos

Manual certificate management causes expired builds

No build history

Can't track what was built when or reproduce past builds

Result: Slow releases, team bottlenecks, wasted developer time

With Capgo Build CI/CD

Build iOS without a Mac

Cloud-based builds mean your whole team can build iOS apps

Automated signing & certificates

Never deal with expired certificates or provisioning profiles again

Consistent builds every time

Same environment, same results - no more "works on my machine"

Automatic store submission

Upload to TestFlight and Play Console automatically

Result: Efficient team, reliable builds, faster release cycles

Works with your existing CI/CD setup

GitHub Actions
GitLab CI
Jenkins Jenkins
CircleCI CircleCI
+ Any CI/CD platform

From Code to App Stores Automatically

Stop manual builds and certificate management. Here's how CI/CD transforms your workflow:

1

Prepare Build Credentials

Run Capgo Build locally once, then export your iOS and Android signing credentials as CI secrets. Your pipeline gets the credentials it needs without committing them to git.

✓ Credentials stay in your CI secret store
2

Push Code, Trigger Capgo Build

GitHub Actions, GitLab CI, Jenkins, or any runner can call the Capgo CLI after your web build and Capacitor sync. No Mac runner is required for iOS builds.

✓ Repeatable builds from the same workflow
3

Download or Submit Artifacts

Use debug builds for testing, upload artifacts for QA, or let release builds submit to TestFlight and Play Store. Your CI/CD workflow controls when each path runs.

✓ Same CLI for manual and release workflows

How much time are you wasting on manual builds?

Every manual build is hours of developer time lost. Inconsistent environments cause bugs that take days to debug. Your team's productivity is suffering.

Watch Your Apps Build Automatically

Push code and watch as CI/CD handles everything - from building to signing to deployment

iOS Build - GitHub Actions
Running
$ git push origin main
Triggered workflow: Build & Deploy iOS
[Build iOS] Setting up build environment...
macOS-latest runner provisioned
Xcode 15.0 selected
[Fastlane] 🚀 Running lane: ios build
Syncing certificates with match...
Installing provisioning profiles...
[Xcode Build] Building MyApp.xcworkspace
▸ Compiling AppDelegate.swift
▸ Compiling ViewController.swift
▸ Linking MyApp
Build Succeeded (2m 34s)
[TestFlight] Uploading to App Store Connect...
Successfully uploaded build 1.2.45
iOS deployment complete!
Android Build - GitLab CI
Running
$ git push origin main
Pipeline #1847 started
[Build Android] Preparing Docker image...
Using image: cimg/android:2023.11
[Gradle] Starting build...
> Task :app:preBuild UP-TO-DATE
> Task :app:preReleaseBuild UP-TO-DATE
> Task :app:compileReleaseJavaWithJavac
> Task :app:bundleRelease
BUILD SUCCESSFUL in 1m 42s
Generated app-release.aab
[Play Console] Uploading to Google Play...
AAB uploaded to internal testing track
Release 1.2.45 created
Android deployment complete!
0
Manual Steps Required
100%
Build Success Rate
5 min
Average Build Time

Why Automate with CI/CD?

Transform your mobile deployment workflow with these powerful benefits

Automated Native Builds

Push code and get native iOS and Android builds automatically. No manual Xcode or Android Studio required - builds run in the cloud.

Build iOS apps without owning a Mac

Zero Downtime Updates

Updates happen in the background while your app is running. Users never experience interruptions or forced updates.

Seamless background installation

Automated Quality Gates

Only deploy when tests pass. Integrate with your existing test suites and quality checks for bulletproof releases.

Deploy only when tests pass

Instant Rollback Safety

Build artifacts are automatically versioned and stored. Revert to any previous build instantly if issues are discovered after deployment.

Complete build history and artifact storage

Advanced CI/CD Features

Take your deployment strategy to the next level with these powerful features

Multi-Environment Deployment

Deploy to different channels based on branch, environment, or custom conditions. Perfect for staging, beta, and production workflows.

  • Branch-based deployments
  • Environment-specific channels
  • Conditional deployments

Gradual Rollouts

Start with a small percentage of users and gradually increase. Monitor metrics and automatically halt problematic deployments.

  • Percentage-based rollouts
  • Automatic halt on errors
  • Metrics-based decisions

REST API Integration

Full API access for custom integrations. Build your own deployment tools or integrate with existing systems.

  • Complete REST API
  • Custom integrations
  • Webhook notifications
Capgo Build in CI/CD

Ship Native Builds From Your Pipeline

Capgo Build plugs into your existing CI/CD flow: install dependencies, build web assets, sync Capacitor, then call the Capgo CLI to compile signed native apps in the cloud.

Pricing

One Capgo plan includes OTA updates, about 15 native builds/month, and credit-based billing for extra build minutes.

Starts at

$12/mo

Included usage

OTA + ~15 builds

per month

Credit usage

By minute

for extra build minutes

1

Initialize Build

Register the app in Capgo and run the build wizard locally once so iOS certificates, provisioning profiles, Android keystores, and store credentials are validated.

2

Export Secrets

Use the credentials manager to export a local .env.capgo.* file, then push it into GitHub Actions secrets with gh secret set -f.

3

Add Workflow

Your workflow installs dependencies, runs your web build, syncs Capacitor, and triggers @capgo/cli build for iOS, Android, or both.

4

Release or Test

Trigger debug builds from a button, release builds from tags, or smoke builds on main. Upload artifacts for QA or submit release builds to stores.

Core CI Commands

Run setup locally, export the credentials, then let CI call Capgo Build after your project build and Capacitor sync.

npx @capgo/cli@latest build init
npx @capgo/cli@latest build credentials manage --appId com.example.app
gh secret set CAPGO_TOKEN --body "your_capgo_api_key_here"
gh secret set -f .env.capgo.com.example.app

npm ci
npm run build
npx cap sync
npx @capgo/cli@latest build com.example.app --platform android --build-mode release

What Goes Into CI Secrets

  • Capgo API key: CAPGO_TOKEN with build permissions.
  • iOS signing: certificate, password, provisioning map, App Store Connect key, issuer, and team ID.
  • Android signing: keystore, alias, key passwords, and Play Console service account JSON.
  • Optional artifact output: add output upload flags for QA download links and QR codes.

Ready to Automate Your Native Builds?

Use Capgo Build from your CI/CD pipeline to compile, sign, test, and release native iOS and Android builds.

Capgo Build • GitHub Actions examples • Credentials stay in CI secrets

Keep going from Capgo CI/CD

If you are setting up CI/CD for Capacitor releases, connect this page with CI/CD Integration for the baseline, GitHub Actions for live updates, Capgo Native Builds for signed binaries, PR Preview Solution for review builds, and Common CI/CD Bottlenecks in OTA Pipelines for avoiding slow releases.