For agencies, startups & public sector teams
CapWrapp puts a Fastlane + GitHub Actions pipeline in each repo, keeps certificates and keystores in a vault, and gives your team one dashboard to preview, ship to TestFlight and Play, and submit to review — for every app you maintain.
A Atlas Labs Apps
Repositories connected through the CapWrapp GitHub App.
atlas-labs/harbor
Updated 2 minutes ago
atlas-labs/fitloop
2 packages can be updated
Updated 1 hour ago
atlas-labs/pawpal
Updated 3 hours ago
atlas-health/meridian
1 package can be updated
Updated yesterday
atlas-labs/tavola
Updated yesterday
atlas-labs/kiddo-web
Updated 3 days ago
Who it’s for
Ship every client’s app with its own store keys and its own Slack channel, from one dashboard your whole team shares.
Run several apps or brands from GitHub without a dedicated mobile release engineer.
Many public-facing apps, admin and member roles, and builds that run on your own GitHub runners.
The fleet tax
Capacitor shares your code across iOS and Android. Shipping it is still per-app work — and it multiplies with every app you add.
Distribution certificates, provisioning profiles, and Apple’s cap on certificates per team.
One per Android app. Lose one and you are asking Google for an upload key reset.
They must go up on every upload, for every app, on both stores.
Fastlane lanes and workflow YAML copied between repos, slowly diverging.
Repos stuck on different majors, each with its own set of plugins.
“Who has the .p8 for this app?” — asked in Slack, again.
Name, subtitle, description and what’s new, per store and per locale.
App Store Connect and Play Console tabs for every review submission.
How it works
CapWrapp writes standard files to your repos and orchestrates GitHub, Apple and Google. Nothing runs on a black-box build farm.
capwrapp/native-pipeline adds the workflow and Fastlane lanes. iOS builds on macos-latest, Android on ubuntu-latest — your runners, your minutes.name: CapWrapp native
on:
workflow_dispatch:
inputs:
sha: # commit to ship (required)
version: # CFBundleShortVersionString / versionName
ios: # TestFlight: 'true' | 'false'
android: # Play Internal: 'true' | 'false'
report_url: # where step reports go
report_token: # short-lived, one per run
concurrency:
group: capwrapp-native-${{ github.repository }}
cancel-in-progress: false
jobs:
prepare: # checkout, install, secrets, web build, cap sync
runs-on: ubuntu-latest
ios: # pods, signed IPA, fastlane → TestFlight
runs-on: macos-latest
android: # keystore, versionCode, AAB, fastlane → Play
runs-on: ubuntu-latest
finish:
runs-on: ubuntu-latest
Step reports
Built for fleets
One place for the parts of a release that don’t live in your code — per app, per team, per store.
App Store Connect key, Distribution certificate, Play service account, upload keystore and build-time env live server-side. Copy keys between apps on the same team; settings sit behind a PIN.
Harbor Reuse from another app
Give each app its own Slack webhook, so every team or client follows its own channel. Telegram and email too: started, failed, ready to test, new commit on the default branch.
#harbor-releases CapWrapp 🧪 Harbor is ready to test on TestFlight / Play Internal, version 1.4.0!
Any commit becomes a hosted web build with a QR code and a signed link that expires after 7 days. Revoke it whenever you like.
preview.capwr.app/p/7f3a…c91e
Fitloop · 9f2c1ab
expires in 7 days
Edit store copy per locale with live character limits and AI translation, push copy and screenshots, then submit to App Review or promote to Play production.
App Store
In review
Google Play
ENFRDEESITPTJA
Capacitor status, packages behind npm and last activity for each repo. Search, pin, switch organizations.
Organizations with email invites. Members ship and edit listings; admins also manage settings and people.
Official packages, plugins and @capgo/* are checked against npm daily. Upgrades land on capwrapp/capacitor-deps.
CapWrapp reads the Actions log and tells you which step broke and what to change.
RevenueCat, OneSignal, Sentry, Firebase and Capacitor plugins, added with a PR and keys in the vault.
Still a website? CapWrapp commits Capacitor and a CI job that generates the iOS and Android projects.
Under the hood
Your code and your builds stay in GitHub. CapWrapp holds the keys, dispatches the workflow, and listens to what happens.
Your GitHub
CapWrapp
Apple & Google
Every build is a GitHub Actions run in your org. macOS minutes are billed to you by GitHub, at GitHub’s price.
The job pulls signing keys and env with a short-lived token. Nothing is written to GitHub secrets, and it all leaves with the runner.
Installation tokens are minted server-side. Webhooks for pushes, workflow runs and pull requests keep the desk live.
Capacitor config, native projects, GitHub Actions workflows and a .capwrapp folder. Close the PR or revert the commit to walk away.
GitHub App permissions
| Metadata Know the repo exists | Read | Know the repo exists |
|---|---|---|
| Contents Read commits, add Capacitor and pipeline files | Read & write | Read commits, add Capacitor and pipeline files |
| Actions Dispatch the native and preview workflows | Read & write | Dispatch the native and preview workflows |
| Pull requests Open pipeline, upgrade and integration PRs | Read & write | Open pipeline, upgrade and integration PRs |
| Workflows Add the job that generates ios/ and android/ | Read & write · optional | Add the job that generates ios/ and android/ |
Build it yourself?
For every app
Fastlane + Actions, by hand
With CapWrapp
Pipeline
Copy and adapt lanes and YAML, then keep them in sync
Installed by PR; reinstall to refresh every helper
iOS signing
Match repo or manual certificates, until the team cap bites
Created from the API key; unused CI certificates revoked at the cap
Android signing
Keystores in someone’s Drive
Minted or uploaded once, vaulted, downloadable
Build numbers
Scripted per app
Latest TestFlight build + 1; highest Play versionCode + 1
Secrets
GitHub secrets per repo, rotated by hand
One vault per app, fetched per run
Listings
Two consoles × every language
One editor, AI translation, push to both stores
Review
Submit in App Store Connect and Play Console
Submit or promote from the release board
Visibility
A tab of Actions runs per repo
One dashboard; per-app Slack alerts
Moving off Ionic Appflow?
Appflow sunsets on December 31, 2027. Our guide maps the move: store builds from GitHub with CapWrapp, live updates with a dedicated OTA service.
Pricing
Every plan includes everything CapWrapp does. Plans only differ by how many apps you’re actively shipping.
For founders shipping their own apps
$29/mo
Up to 3 active apps
Start free trialNo credit card needed
For makers and small teams
$99/mo
Up to 10 active apps
Start free trialNo credit card needed
For agencies shipping apps for clients
$249/mo
Up to 50 active apps
Start free trialNo credit card needed
An app counts as active for 30 days after you ship it: a test build, a store release, an update or a listing change. Connected projects and previews never count, and an app’s iPhone and Android versions count as one.
Cancel anytime — your apps stay live on the stores, and your code stays in your project.
Need more than 50 apps?
FAQ
Straight answers, including what CapWrapp doesn’t do yet.
Read the technical docs
GitHub Actions, in your own repositories. CapWrapp dispatches the capwrapp-native.yml workflow with the commit SHA and version; iOS jobs run on macOS runners and Android on Linux. You can point CapWrapp at your own workflow if it accepts the same inputs.
No. CapWrapp builds, signs, uploads and tracks releases. Keep your tests in GitHub Actions and ship the commits that pass — the pipeline is a normal workflow file you can read.
Not today. Every store build starts from a confirmed click in CapWrapp, so nothing reaches TestFlight or App Review by accident. CapWrapp tells you on Slack, Telegram or email when a new commit lands on the default branch.
Not yet. CapWrapp expects one Capacitor app at the root of each repository.
GitHub only, for now.
Anything whose build outputs a static folder with an index.html — Vite, Ionic (www), static Next.js exports and similar — installed with npm, pnpm, Yarn or Bun. A server-only bundle needs a static build output.
CapWrapp doesn’t use Fastlane Match. It creates an Apple Distribution certificate from your App Store Connect API key, or you upload a .p12. On Android, upload the keystore you registered with Play, or let CapWrapp mint one.
In CapWrapp’s server-side vault, never in your repositories or GitHub secrets. Each run fetches what it needs with a short-lived token, and the files disappear with the runner.
CapWrapp ships store builds today and doesn’t offer live updates yet. Keep your OTA provider for web-only changes.
Yes, with organizations. Invite product owners, QA or clients by email as admins or members. Members can ship versions and edit listings; admins also manage settings and invites.
Repository and app metadata, store listing drafts and screenshots, run history, and — in the vault — signing keys and build-time env. Store builds run on your own GitHub runners; commit previews host the built web files behind a link that expires.
With a Google or GitHub account. Screens that touch signing keys sit behind an extra 4-digit PIN.
You pay for active apps, not seats, and teammates and clients are free: Founder is $29 a month for up to 3 apps, Pro $99 for 10, Agency $249 for 50. Every plan starts with a 14-day free trial, no credit card needed. Rolling out many apps? Chat with the founder and plan the first ones together.
Connect your first repos, vault the keys, and send your first TestFlight build from your own GitHub Actions.