Questions

On the computer where you work, in the app's folder: curl -fsSL https://ploa.dev/install.sh | sh, then ploa login, then ploa mcp install. Restart your agent and ask it: "Ship this app to the App Store and Google Play with Ploa." It links the folder, tells you the steps that are yours, and asks you before anything goes to App Review or production. See Getting started.

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. You need an Apple Developer account, a Google Play developer account, or both. An app already in the stores comes in as it is: see Stores and apps.

Any agent that speaks MCP. ploa mcp install sets up Claude Code, Cursor, VS Code (Copilot) and Codex for you; Windsurf, Claude Desktop and others take a few lines of settings; Claude on the web connects to https://ploa.dev/mcp. See Connect your agent.

No. The store text, translations, screenshots and privacy answers are written by your agent, from your app's code, with the model you already use. Ploa checks them against each store's rules, does the store work, and asks you before anything people will see goes out.

No. Everything an agent does you can do on the dashboard or with the CLI. The agent is just faster at the writing: store text, translations, screenshots and privacy answers.

Yes. Add https://ploa.dev/mcp as a connector in Claude on the web (or any agent that can't run a command), and approve it on ploa.dev. It has every tool that needs no computer; builds then run on GitHub. See Connect your agent.

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.

Not for Android: on your own computer it needs only Java and the Android SDK, and GitHub or your Google Cloud can build it for you. iOS needs a Mac with Xcode: your own, as it is or as a runner for your GitHub Actions, GitHub's Macs if you allow it, or Apple's Xcode Cloud.

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 Linux minute counts as one and a Mac minute as ten, so an iOS build there uses about 150 to 200. Builds on your own Mac as a runner use none.

Not to ship to the stores. Builds run on your machine, your GitHub or your Google Cloud, and send Ploa only what needs signing (and on Pro and Team, an Android build can go to Google Play through Ploa); preflight runs where your code is. With GitHub linked, Ploa reads the repositories you chose. What you send to be hosted reaches Ploa: a web version's built files, and a server's folder as git keeps it, never .env files or keys.

No. A build is deleted from Ploa as soon as the store has it.

Yes, while it's still building, wherever it runs: from the dashboard (Stop, then a second confirmation) or by asking your agent. On Xcode Cloud, Apple's API can't stop a run, so it goes on until you stop it in App Store Connect or Xcode. See Starting and stopping a build.

Not unless you say so. App Review, production, prices, testers who get an email, replies under reviews and a web version going live wait for your approval. You can make an agent autonomous, in Ploa, and everything it does is still logged under its name. See Access and approvals.

It never sees a store key or a secret, can't approve its own requests, make another token, or do more than you may. It can't turn on autonomy for itself or allow iOS builds on GitHub's Macs, and it can't accept a store's agreements: those are yours, in the store's console. And it can't fill the store forms that have no API (below): it tells you what to enter instead.

Sealed in Ploa's vault, on its server, and encrypted at Google with Ploa's key in Google Cloud HSM (or your own key in Google Cloud KMS or AWS KMS, on any plan). They never reach your computer or your agent; the calls to Apple and Google leave from the server. See Security and keys.

It reads the repositories you choose. It changes something only once you turn it on, and then only through a pull request, a check, an issue, a comment or a tag. It runs only its own workflow and never pushes to your branches. See GitHub.

A few things only you can do, in the stores' consoles: creating the app in App Store Connect and Play Console, Apple's App Privacy form, and most of Play Console's App content forms. Ploa tells you exactly what to enter and where, with links, and checks them off when you say they're done.

Every part of Ploa is on the Free plan: App Review and production, the store page, purchases and sales, autonomous agents, product pages and tests, TestFlight and internal testing, preflight, the CLI and MCP. Free is for you alone, with one app (its iPhone, Android and web) and a basic showcase site at a free ploa.app address. Builds on your own Mac, GitHub or Google Cloud are free and unlimited on every plan. Paid plans add apps, members, hosting room, your own domains, the web app's server side in Ploa's cloud, and support. See Plans.

No. Every site has a free address on ploa.app, such as myapp.ploa.app, and on Starter, Pro and Team you can connect a domain you already own. See The address, and a domain you own.

See the refund policy, or write to us on the support page.