All in one app: iPhone, Android and the web
One project for iPhone, Android and the web. Ploa takes it to the App Store and Google Play, puts its website or web app online at a free ploa.app address, and runs its server and database. Your agent works through the CLI and MCP, and anything that can't be undone waits for you.
ploa release ios --submit
› Preflight (iOS)
✓ nothing to fix
› Signing: app.favey
✓ identity for team 7Q2FK3, 1 App Store profile(s)
› Xcode: archive Favey (build 42)
› Upload 1.4.0 (42) straight to App Store Connect · 38.2 MB
✓ 1.4.0 (42) is on TestFlight.
› Waiting for approval: 1.4.0 (42) to App Review
https://ploa.dev/app/approvals
✓ Submitted to App Review
ploa web build
✓ 1.4.0 (13): 214 files (6.8 MB), checked
✓ With testers at favey--13.ploa.app
Works with the agent you already use
Ploa Aio · All in one app
Build it once with your agent, for iPhone, Android and the browser. The mobile apps go to the App Store and Google Play. The web goes up on Ploa: a showcase site for the app, the app itself as a web app, or both, with a server and a database when it needs them.
/app.Platforms
Ploa builds these itself, on your Mac, on GitHub or in your Google Cloud, then signs and ships them:
Unity, .NET MAUI and anything else ship as they're built: an .ipa, .app or .xcarchive, or an .aab, and Ploa signs it for the stores.
Built with the framework's own command, then sent up as a version:
Or any build script. Sites are served as files; a project set to run its own server is told how to export it, and its back end runs as the app's server.
The app's own API, from a Dockerfile or as it is:
With Postgres 16, scheduled jobs, secrets and logs, run on Google Cloud in Tel Aviv, or in your own Google Cloud.
One core, three ways in
A web dashboard for people, a CLI for developers and CI, and an MCP server for agents. All three act on the same data under the same rules, so whatever your agent starts, you see live, and whatever needs you waits in one place.
ploa builds on your Mac, checks the project and sends it. Built for CI too.A release, start to finish
Checks the project against what the stores reject: icons, permissions' wording, versions, privacy manifests, signing. Each finding with its fix.
iOS builds on your Mac with a certificate Ploa hands over for minutes. Android is signed on the server; the upload key never leaves it.
Straight to TestFlight and Play's internal testing, with testers, groups and what to test. The web gets a testing address of its own.
Submitted to App Review with one tap of yours. If a store says no, Ploa shows why and what to fix.
Production, staged rollouts, halts and promotions, each one approved by you. The web goes live at its address, and back in one step.
ploa preflight
Preflight · Favey 1.4.0 (iOS build 42 · Android 42)
! NSCameraUsageDescription still uses Expo's default text; App Review asks for a specific reason (Guideline 5.1.1)
Explain what the app does with it, e.g. "Favey uses the camera to scan a receipt"
Ready, with 1 to look at
ploa release android --version-code auto
› Gradle: bundleRelease
› Signed with the upload key on Ploa
✓ 1.4.0 (42) is on internal testing
ploa release android --release r_8f2 --promote production --rollout 10
› Waiting for approval: production, 10% rollout
✓ Approved by Dana · rolling out to 10%
Versions on every platform
Every upload of the website or web app is a version, numbered like your store builds: the version from your project and a build number Ploa counts. So 1.4.1 is 1.4.1 on iPhone, Android and the web, and the dashboard shows the app's web beside its iOS and Android, with the same steps and approvals.
ploa.json: redirects, rewrites and headers, kept with each version.ploa web build
i Building it (Expo (web)): expo export -p web
i Sending the built files from dist to favey
✓ 1.4.1 (13): 214 files (6.8 MB), checked
✓ With testers at favey--13.ploa.app
ploa web release
› Asked for your approval to release 1.4.1 (13): approve it in Approvals on ploa.dev
✓ Approved by Dana · going live at https://favey.ploa.app
ploa web rollback
✓ favey goes back to 1.4.0 (12)
Server and database
When the web app or the mobile apps need a back end, it's part of the same app in Ploa: send the server's folder, and Ploa builds it, runs it on Google Cloud and gives it its database. There's no machine to look after and nothing to buy on its own: it comes with Pro and Team, for each app.
ploa server create
✓ The server is being made. ploa server shows where it stands.
ploa server deploy
Sending server (0.4 MB)…
Version 7 is building.
✓ Version 7 is live.
On GitHub
Connect your repository once. Ploa checks every pull request against the stores' rules, builds on your GitHub Actions, and puts the build on TestFlight and Google Play's testing, with an install link on the PR. No key in your repo.
Builds use your GitHub minutes, not Ploa's: free on a public repository, and none at all on your own Mac. How minutes count
Keys stay home
App Store Connect keys, Play service accounts, upload keystores and distribution certificates live encrypted on Ploa's server. Every call to the stores leaves from there. An agent's token can draft and ask; it can't see a secret, approve, or make another token.
You stay in charge
Sending a version to App Review, going to production, a rollout, a new price, putting the web live: the agent asks, you approve in one tap, from the dashboard or a push notification on your phone. Or make an agent autonomous, and it's still recorded under its name.
The store page
Name, subtitle, description, keywords and what's new, in every language, checked against each store's limits as they're written. Screenshots and app previews checked against Apple's and Google's exact sizes before anything is uploaded.
Everything around the release
Answer once. Ploa sends Google Play's Data safety for you and walks you through Apple's App Privacy, with hints read from your code.
Subscriptions and one-time products in both stores in one shape: names per language, prices, trials, offer codes, sent to review with the version.
Downloads, proceeds and the store page's funnel from both stores, per app, by day.
Every rejection in one view with its reasons and guideline numbers, and next steps your agent can take.
The App Store's custom product pages and product page optimization tests, with their own screenshots and previews.
Events on the App Store with their media, sent to review when they're ready.
Install the dashboard from the Home Screen and approve from a notification.
A workspace per team, members by invite, passkeys for everyone, and the app's stores reached only through its own workspace's accounts.
Three commands
Sign in and give your agent Ploa: it links the app by itself. From then on, "send it to TestFlight" is a sentence, not a weekend.
$ curl -fsSL https://ploa.dev/install.sh | sh
ploa login
Confirm this code in your browser: QXWT-7HKM
✓ Signed in to https://ploa.dev as dana@studio.dev (allowed up to submit)
ploa mcp install
✓ Claude Code added .mcp.json
✓ Cursor added .cursor/mcp.json
✓ Codex added ~/.codex/config.toml
Restart the agent to pick up Ploa. The project files hold no secrets.
Security
Every action by you, your team and every agent goes into an append-only log where each row's hash covers the one before. Once a day its head is anchored where the server itself can't change it.
Pricing
$0
One app on iPhone, Android and the web, with all of Ploa.
$9/ month
One app with room to grow, on a domain of your own.
Most popular
$29/ month
For a developer or a small team with a few apps.
$99/ month
For a team or studio, with agents doing the work.
Prices in US dollars. Where prices usually include VAT or GST (the EU, the UK, Australia and others), it's included; elsewhere, like the US and Canada, sales tax is added at checkout. Every part of Ploa is on every plan, Free too: plans differ in apps, members, the web's room, the server side and support. Builds on your own Mac, on GitHub or in your Google Cloud are free on every plan, on your own account there. Every site gets a free address on ploa.app; Ploa doesn't sell domains, you connect one you already own. Past its room, a site on Free or Starter stops until next month; on Pro and Team you choose: stop there, or turn on extra usage at $0.10 a GB of traffic and $0.20 a GB of storage a month. The server side (an app's own API, scheduled jobs and Postgres) comes with Pro and Team for each app, in Ploa's cloud in Tel Aviv; on any plan, Free too, it can run in your own Google Cloud instead, billed to you by Google. Paid plans open soon; until then every account starts free.
Questions
Any iOS or Android app, and its web. Ploa builds Expo, Flutter, React Native, Capacitor and native Swift or Kotlin apps itself; an app made with Unity, .NET MAUI or anything else ships as it's built (an .ipa, .app or .xcarchive, or an .aab), and Ploa signs it for the stores. For the web, any framework that builds to files: Expo, Next.js, Vite, Astro and many more. The stores need an Apple Developer account, a Google Play developer account, or both; the web needs neither.
Not for Android: it builds in your own Google Cloud or on GitHub's Linux, and on your own machine it needs only Java and the Android SDK. iOS needs a Mac with Xcode: your own, as it is or as a runner for your GitHub Actions, or GitHub's Macs if you allow it. An app built another way needs a Mac only when its .ipa isn't signed for the App Store yet, since Ploa signs it there.
No. Builds on your own Mac, on your GitHub or in your Google Cloud are free on every plan, Free too, with no count: they run on your own account there, so GitHub's minutes and Google Cloud's build time are yours.
Not from Ploa. GitHub counts their minutes on your own GitHub account: free on a public repository, and on a private one they come out of your plan's free monthly minutes, where a minute on GitHub's Linux counts as one and a minute on GitHub's Macs as ten, so an iOS build there uses about 150 to 200. Builds on your own Mac as a runner use none. Past the free minutes, GitHub charges only if you've set it a budget; otherwise the builds wait for next month. You can see the minutes in GitHub's billing settings.
It reads the repositories you choose when you install it. It changes something there only once you turn it on, and then only through a pull request, a check, an issue or a tag: preflight's findings on their lines, the next version and the store page as pull requests you merge, a tag and a GitHub Release when a version goes live, and issues for what the stores say. It runs only its own workflow and never pushes to your branches. You can remove it on GitHub at any time.
Yes. An app can be on the web alone, with no store apps: Ploa builds it, gives it a free address on ploa.app, keeps every version with its testers and releases, and on Pro and Team runs its server and database too. Add iPhone and Android later from the same project.
No. Every site gets a free address on ploa.app. On Starter you can connect one domain you already own, on Pro up to three and on Team any number: Ploa gives the DNS records to add, checks them, and gets the certificate by itself.
In Postgres 16 on Google Cloud: in Ploa's cloud in Tel Aviv, or in your own Google Cloud if you choose. It's reached over SSL only, backed up every day, and can be restored to any point in the last 7 days.
Not unless you say so. App Review, production and anything else that can't be undone wait for your approval. You can make an agent autonomous, and everything it does is still logged under its name.
Encrypted in Ploa's vault, on its server. They never reach your machine or your agent; the calls to Apple and Google leave from the server.
It covers the same road, from build to store, with the store page and approvals built in and made for agents. It calls the stores' own APIs directly.
No. A build is deleted from Ploa as soon as the store has it.
Get an account, link your app, and ask your agent.
ploa commented
Install Favey (iOS) from this pull request
1.4.0 (52), built from
a1b2c3d. Join on TestFlight, or scan: