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.
This is a new way to ship software, and the catalogue is still small enough that early poppies define what the category looks like. The names people reach for first are being claimed right now.
Get started Open the developer dashboard| 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 |
That's the honest worry, and it deserves a straight answer. Opening your repository here buys you protection you don't get by keeping it closed — because the catalogue is curated, and we enforce this on your behalf:
Someone can read your repo. What they cannot do is get listed with it. A submission that is a copy or a re-skin of an existing poppy is rejected at review — that's a human reading both, not a similarity score. Your open code is not a free head start for a rival listing.
Even original code gets rejected if it simply does what a listed poppy already does. Users shouldn't have to choose between ten apps with the same feature list. A competitor is listed only when it brings real improvements — features or performance you don't have. Being early is a genuine advantage here, and it keeps working.
Closed code has no licence anyone can hold you to. A published licence does: MIT if you want reach, or copyleft (MPL, LGPL, GPL, AGPL) if you want anyone building on your work to keep their source open too. Both are accepted and neither costs you the catalogue. Pick your licence →
Your buyers are cloud admins installing software into their own AWS account. They point an AI agent at your repo and ask whether the code does anything beyond what it declares. A verifiable no is worth more than any feature list — closed source simply cannot answer that question.
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 — including source-available with a noncompete — what's rejected, and why publishing your 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.