For developers
A poppy is an app whose backend runs in each user's own AWS account — installed, powered, and supervised by AgentsPoppy. You carry zero infrastructure cost, your users keep their data, and the SDK and onboarding docs are written so your AI coding agent does the building. A fully polished poppy ships in hours to a few days, not quarters.
Get started Open the developer dashboardEvery poppy in the catalogue ships from an open repository. That's not a tax — it's the deal that makes the whole ecosystem work in your favour:
Copy-paste clones of your poppy are rejected from the catalogue. Competition must bring genuinely new functionality — nobody gets listed by re-skinning your code.
An open repository is a hard requirement for listing. It's what lets us verify your packages, review your updates, and vouch for you to users.
Users point their AI agent at your repo and verify the code does exactly what it declares. That audit is what turns a wary cloud admin into a paying, loyal customer.
| You get | You give |
|---|---|
| Zero infrastructure cost — backends run in each user's cloud, on their bill | An open repository — required for every catalogue listing |
| 95% of platform sales — flat 5% only on sales our checkout processes; you're the merchant of record | Real originality — bring something new, not a re-skin of an existing poppy |
| Freedom to leave — distribute outside the catalogue any time, 0% to us | Honest declarations — permissions, data flows, age rating, and licensing, all reviewable |
Install AgentsPoppy, run the hello-poppy example, and learn the dev loop — validate, install, certify.
Hand one prompt to your AI coding agent and take a poppy from idea to a packaged, listable zip.
The permission broker: manifests, risk ratings, scoped short-lived credentials, attribution, teardown.
Sign in, connect Stripe, submit your poppy, track review status, and publish updates.
The flat 5%, the purchase button, server-side entitlements — and the rules that keep checkout fair.
Exactly what review checks: the listing rules, originality, quality bar, age rating, and data declarations.
MIT is encouraged and featured; what else is accepted, what's rejected, and why open source wins here.
The default is simple: user data never leaves the user's cloud. If yours does, here's what you must declare.
The catalogue is curated, not rubber-stamped. A human reviews every submission and every update. If that's not for you, you can always distribute your poppy yourself — sideloading from disk is supported forever, with no revenue share to us.
Signing up to the dashboard means accepting the Developer Agreement.