Passer au contenu

đŸ—ïž Construction

đŸ—ïž Construction Natif mobile apps in the cloud and automatically Soumettre them to the Application Store and Play Store.

The build command allows you to build your Capacitor app for iOS and Android in Capgo’s cloud infrastructure, similar to how Expo handles builds. Your app is built on dedicated infrastructure and can be automatically submitted to the app stores.

Current Status: Public Beta

Construction Natif mobile apps traditionally requires:

  • Mac hardware for iOS builds ($1000+ or expensive CI minutes)
  • Complex CI/CD Configuration with caching and credentials
  • Maintenance overhead for Xcode, Android Studio, and SDKs

With Capgo Cloud Construction, you get:

  • ✅ No Mac required - Construction iOS apps from any machine
  • ✅ Zero Configuration - No CI/CD Configuration needed
  • ✅ Battle-tested - Built on 3 years of internal Production use
  • ✅ Secure - No Journal storage, automatic cleanup
  • ✅ Natif-only - Your JavaScript stays private
Terminal window
npx @capgo/cli@latest build com.example.app

That’s it! Your Application will be built in the cloud and you’ll see real-time Journaux.

Terminal window
npx @capgo/cli@latest build [appId] [options]

Construction for both platforms:

Terminal window
npx @capgo/cli@latest build com.example.app

Construction for iOS only:

Terminal window
npx @capgo/cli@latest build com.example.app --platform ios

Construction for Android in Débogage mode:

Terminal window
npx @capgo/cli@latest build com.example.app --platform android --build-mode debug

Construction from a specific directory:

Terminal window
npx @capgo/cli@latest build com.example.app --path ./my-app
OptionTypeDefaultDescription
appIdstringcapacitor.configApplication ID (e.g., com.example.app)
--path <path>stringCurrent directoryPath to your project directory
--platform <platform>stringbothTarget platform: ios, android, or both
--build-mode <mode>stringreleaseBuild mode: debug or release
--build-config <config>string-Additional build configuration as JSON string
-a, --apikey <apikey>string-API key (or use CAPGO_TOKEN env var)
--supa-host <url>stringhttps://api.capgo.appCustom Supabase host URL
--supa-anon <key>string-Custom Supabase anon key
sequenceDiagram
participant Dev as Developer
participant CLI as Capgo CLI
participant Cloud as Capgo Cloud
participant iOS as Mac Builder
participant Android as Android Builder
Dev->>CLI: build com.example.app
CLI->>CLI: Zip project locally
CLI->>Cloud: Upload to R2
Cloud->>iOS: Provision Mac (iOS)
Cloud->>Android: Start sandbox (Android)
iOS-->>CLI: Stream logs (SSE)
Android-->>CLI: Stream logs (SSE)
iOS->>Cloud: Build complete
Android->>Cloud: Build complete
Cloud->>iOS: Cleanup (24h later)
Cloud->>Android: Cleanup (instant)
CLI->>Dev: Build succeeded
  1. Local Preparation - Your project is zipped locally (excluding node_modules, dotfiles)
  2. Télécharger - Zip file uploaded to secure cloud storage (Cloudflare R2)
  3. Construction Execution:
    • iOS: Dedicated Mac machine provisioned, Fastlane builds and signs
    • Android: Secure sandbox created, Gradle compiles and signs
  4. Journal Streaming - Real-time Journaux via Server-Sent Events (not stored!)
  5. Automatic Cleanup:
    • iOS: Files deleted after 24 hours when machine is dismissed
    • Android: Everything deleted instantly after Construction

Capgo Cloud Construction isn’t Nouveau infrastructure - we’ve been using it internally for 3 years:

  • ✅ Custom Fastlane - Built specifically for Capacitor apps
  • ✅ Thousands of builds - Battle-tested in Production
  • ✅ Capacitor experts - Deep knowledge of what matters
  • ✅ Natif-only focus - Your JavaScript never touches our servers
  • No Journal storage - Journaux only stream to your Terminal, never saved
  • No artifact storage - Apps sent directly to Application Store/Play Store, we keep nothing
  • Credentials auto-deleted - Used only during Construction, deleted after
  • Isolated builds - Each Construction runs in isolation
  • Your code stays yours - We only Construction Natif parts, JavaScript stays local

Works everywhere - GitHub Actions, GitLab CI, or any CI/CD platform:

- name: Build native app
env:
CAPGO_TOKEN: ${{ secrets.CAPGO_TOKEN }}
run: |
npm run build
npx cap sync
npx @capgo/cli@latest build com.example.app \
--platform both \
--build-mode release

No need for:

  • Mac runners
  • Android SDK Installation
  • Xcode Installation
  • Complex caching
  • Credential management

Construction time is billed based on actual Utilisation:

  • Android: 1× multiplier (~$0.XX per minute)
  • iOS: 2× multiplier (~$0.XX per minute, due to Mac hardware)

Typical costs:

  • Android DĂ©bogage: 3 min × 1× = ~$X.XX
  • iOS LibĂ©ration: 7 min × 2× = ~$X.XX

Only pay for what you use. No minimums, no surprises.

FonctionnalitéCapgo Cloud ConstructionGitHub Actions (Mac)Expo EAS
Mac required locally❌ No✅ Yes❌ No
Configuration complexity⭐ Single Commande⭐⭐⭐ Complex YAML⭐⭐ Config files
Capacitor Natif✅ Optimized⚠ Generic❌ Expo only
Your code privacy✅ Never stored⚠ In runners⚠ Uploaded
Cost (iOS)💰 2× base💰💰💰 10× expensive💰💰 Premium

Important: Capgo builds native parts only.

✅ We Construction:

  • iOS Natif code (Swift, Objective-C, Xcode projects)
  • Android Natif code (Java, Kotlin, Gradle projects)
  • Code signing and Application Store submission

❌ You Construction (locally):

  • JavaScript, HTML, CSS (npm run build)
  • Capacitor sync (npx cap sync)
  • Your web assets

This separation ensures:

  • Better SĂ©curitĂ© - Your Application logic stays private
  • Faster builds - No duplicate web builds
  • Clear responsibility - You control your code

Current limitations during public BĂȘta:

  • Construction timeout: 10 minutes maximum
  • TĂ©lĂ©charger timeout: 1 hour for TĂ©lĂ©charger URL
  • iOS machine: 24-hour lease requirement, Construction on Mac will enqueue to ensure optimal Utilisation
  • Access: Public BĂȘta only

Ready to Construction without the hassle?

Create Your First Build

Step-by-step Guide to your first cloud Construction.

Commencer →

Join Public Beta

Cloud Construction is in public BĂȘta. Join our CommunautĂ© to get access.

Join Discord →