Skip to main content
For agencies

Run every client's app releases from one Capgo login

Give each client its own organization, channels, and API keys. Ship web-layer fixes as live updates, let the client review them on staging, and transfer the app when the contract ends.

Agency release work

Each new client adds another release process

Every client is set up differently

Separate store accounts, signing keys, and release habits. The steps often live in one person's head or on one laptop.

Clients want the fix today

A small JavaScript fix still waits for a new binary and store review, often 24–48 hours, sometimes much longer. Users still have to update after that.

People move between projects

When the developer who ran a client's releases leaves, the credentials and the process can leave with them.

Maintenance eats fixed-price margins

Every small fix after launch costs a full build, submission, and review cycle.

Clients ask what is live

You need to show which build is on production, who shipped it, and when.

Handoff is manual

At the end of the contract, the client needs the app, the access, and the release setup, not a document that describes them.

How Capgo fits agency work

Separate clients, one release workflow

The same CLI and channel setup for every client, with access and billing kept apart.

One organization per client

Create an organization for each client and switch between them from the sidebar. Each one has its own members, apps, API keys, plan, and audit logs.

Organization docs
  • Plan and billing per organization
  • Roles at organization, app, or channel scope
  • Groups to add your delivery team in one step

A review lane for each client

Upload to a staging channel first. The client checks the change on their own test devices, then you link the same bundle to production. Native changes still go through the stores.

Channels docs
  • Staging and production channels per app
  • Device overrides for the client's test phones
  • Progressive rollout and channel rollback

Handoffs without lost access

Invite the client's team with their own roles, retire your CI keys, and transfer the app to the client's organization when the contract ends.

App settings and transfer docs
  • Transfer an app to another organization
  • App-scoped API keys with an expiry date
  • Audit logs of who changed what

How it works

How agencies ship client apps with Capgo

A setup you can repeat for each new client. Every command below is from the Capgo CLI docs.

  1. Create an organization for the client

    Each client gets its own organization, plan, and member list. Add your team with a group, and the client's people with their own roles.

    npx @capgo/cli@latest organization add --name "Client A" --email mobile@client-a.com
    Roles reference

  2. Give the client's CI its own API key

    Create an API key limited to that client's app, with the App Uploader role and an expiry date. Store it in the client's CI secrets.

    # In Client A's pipeline, with Client A's key
npx @capgo/cli@latest bundle upload --channel staging --apikey "$CAPGO_TOKEN"
    API key docs

  3. Let the client review, then promote

    Point the client's test phones at the staging channel with device overrides. When they approve, link the same bundle to production.

    npx @capgo/cli@latest channel set production com.client-a.app --bundle 1.4.2
    Channels docs

  4. Hand the app over

    Invite the client's admins, let your CI keys expire, and transfer the app to the client's organization from the app settings. Only a Super Admin can transfer an app.

    App settings and transfer docs

Apps built with Capacitor

Marketplace apps need client-safe release lanes

Service, marketplace, and booking apps have buyer, seller, messaging, payment, and support journeys changing at different speeds. Agencies can use Capgo channels to review each client request, ship the web-layer change, and keep rollback ready for launch day.

Freelancer: Hire & Find Jobs app icon BUSINESS

Freelancer: Hire & Find Jobs

Marketplace flows where client-requested fixes can touch hiring, messaging, and account screens.

Google Play installs
8.9M
Store rating
4.1
Cars.co.za app icon AUTO AND VEHICLES

Cars.co.za

Vehicle listings and lead flows that benefit from staged feature checks before broad rollout.

Google Play installs
1.9M
Store rating
4.4
KAI Access: Train Booking App app icon TRAVEL AND LOCAL

KAI Access: Train Booking App

Booking and ticketing journeys where operational copy and schedule surfaces change often.

Google Play installs
13.5M
Store rating
3.6

Customer proof

What teams shipping with Capgo say

5.0/5 rated by developer teams 9,400+ teams Read reviews

no-tone @ Webincode

Developer, Webincode

“Being able to add Device ID's to certain groups and push the changes to only certain groups is a life saver.”

Portrait of Sergiu S

Sergiu S

Lead Developer, drivolino GmbH

“The Capgo Capacitor Updater plugin completely transformed how we ship updates. What used to take days now takes just minutes.”

Nate van Jole

CTO, Private

“Getting set up took less than a day. Channel-based rollouts let me test on my own device before anything hits production users.”

FAQ

Agency questions

What agencies usually ask before moving client apps to Capgo.

Can I keep each client's apps and data separate?

Yes. Create one organization per client. Members, apps, API keys, plans, and audit logs belong to that organization, and you switch between organizations from the sidebar.

Organization docs

Can the client pay for their own plan?

Yes. A plan applies only to the organization it was bought for. Give the client's finance contact the Billing Manager role so they can manage payment and invoices without access to apps.

Billing docs

Can a contractor work on only one client app?

Yes. Give them an app-scoped role such as App Developer or App Uploader on that app. Their upload and device rights stay limited to that app.

Roles reference

How do we hand an app over at the end of a contract?

A Super Admin can transfer the app to another organization they belong to, such as one the client owns. You can also invite the client's admins to the existing organization and remove your team afterwards.

App settings and transfer docs

What can we change without a store release?

Live updates change the web layer: JavaScript, HTML, CSS, and assets. New native plugins, permissions, or native code need a new binary and store review. Capgo Build can produce those binaries in the cloud.

Native compatibility docs

Set up your next client on Capgo

During the trial, create an organization for one client and run a staging-to-production release on their app.