Vibe-code the next generation of user-owned cloud apps.
What took a funded team yesterday, you ship this afternoon. Describe it in plain language; your AI agent builds it — on your users' own AWS. No servers to fund, no data honeypot to guard: every user brings their own cloud.
The app is free — no licence, no seat, no trial clock. Every poppy in the catalogue is open source, so you can read it before it runs.
you ▸ Create a private photo-sharing app for families — encrypted storage, each family on their own AWS agent ▸ designing the stack… provisioning in the user's account… sealing storage with their keys… agent ▸ ✓ live — scoped to its own resources, every change visible, one-click teardown.
Apps that run in your cloud — not ours.
AgentsPoppy is the first platform for user-owned cloud apps. A developer vibe-codes an app; you install it, and its backend takes root in your own AWS — there are no company servers behind it, and nothing to lock you in. And because it's your cloud, every app is auditable before you trust it and yours to pause or tear down in one click.
For twenty years, the cloud belonged to a priesthood.
It turns out the mystery was just money.
The reformation is a desktop app.
Infrastructure as an app.
The hard part of software was never the idea — it was standing up the cloud to run it. How you do that has changed exactly twice. A poppy is the third way.
The console
You built your cloud by clicking through dashboards. Standing up one real service — a database, a queue, permissions, networking — was a careful ritual that took hours, and got subtly wrong.
Infrastructure as code
Then you could describe it — Terraform, CloudFormation, CDK — and deploy the whole stack with one command. Powerful, but the description was itself software: making it correct, secure and reusable could take days, and a single wrong line still shipped a broken stack.
Infrastructure as an app
A poppy arrives as an app. You don't open a console or write a line of Terraform — you install it, and it designs, deploys, monitors and tears down its own backend for you, in a friendly flow, often in seconds. Infrastructure as code made the cloud programmable; a poppy makes it installable.
Installable is the word that matters. Standing up real infrastructure no longer takes a cloud engineer — it takes a click, which is what puts a cloud you own within reach of everyone, and lets a new kind of app exist: one where every user brings their own. We don't know of another platform doing this — an app whose backend takes root in your own cloud, supervised from your own machine, and legible to your AI agent before you trust it. If one exists, we genuinely want to hear about it.
Install an app. Watch it take root — in soil you own.
A poppy is an ordinary app with an extraordinary property: its backend doesn't run on the developer's servers, because there aren't any. It runs in your AWS account, planted and supervised by AgentsPoppy on your own computer. Prefer pictures? The guide shows every screen →
Connect your cloud, once
AgentsPoppy runs on your machine and holds your AWS keys locally — they never leave your computer. One scoped policy, never admin.
The poppy plants its backend
Each app gets its own narrow credentials and builds only its own tagged resources in your account. One poppy can't touch another.
You stay in charge
A live map of everything it created, a feed of every change, a pause switch — and a teardown that verifiably removes every trace.
One architecture. Two liberations.
Centralised clouds forced a trade: developers carried the infrastructure, so users surrendered the data. Put the backend in each user's own cloud and both sides get free.
All idea. No infrastructure bill.
- Focus on the idea and how to monetise it — there is nothing else to run. No fleet, no pager, no DevOps week.
- Zero infrastructure cost to you — each user's backend runs in their own AWS account, paid by them at raw cloud cost, typically pennies.
- No fundraising to scale. Your app ships with a backend that's ready for millions of users — because every new user arrives with their own datacenter attached.
- Your agent does the building. The SDK and onboarding docs are written for AI coding agents; one person directing an agent ships what took a funded team.
Your data. Your cloud. Your final say.
- Full control of your privacy and data — it lives in your account, not a company database. There is no honeypot, because there is no middle.
- Everything is visible: a live map of what each app built, a feed of every change, drawn from your own cloud's audit trail.
- Your AI agent audits every app and every update — open source is mandatory for approval, and each update arrives explained, diffable, and verifiable before you apply it.
- Leaving means actually deleting. One click tears out every trace — then verifies nothing was left behind.
The apps nobody could afford to build honestly.
Whole categories of software were impossible to build in a privacy-respecting way — because someone had to own a giant database in the middle, and pay for it. Remove the middle, and they become one-person projects.
A social network with no company in the middle
Every member's posts, photos and follows live in their own cloud slice. The network has no centre to breach, buy, or shut down — because there is no centre.
A dating app that can't leak your life
Your photos, preferences and messages never sit in a startup's database waiting for the breach headline. Profiles talk cloud-to-cloud — and leaving means actually deleting.
An IoT hub without the vendor subscription
Your sensors stream to your own bucket. No monthly fee standing between you and your own house, no company reselling your patterns.
Journals for what you'd never upload
Health records, money, therapy notes, family archives — data too sensitive for a startup's database finally gets great software, because there is no startup database at all.
A large global marketplace where no one holds the world's wallets
Every seller's storefront, inventory and order history runs in their own cloud; every buyer keeps their own purchase record. The platform coordinates trades instead of hoarding them — and because each new member arrives with their own infrastructure attached, it can grow to global scale on an indie budget.
None of these exist yet. All of them are now buildable — by one person.
Trust isn't a promise here. It's a map.
Narrow keys instead of broad ones. A live map instead of a mystery.
A delete button that actually deletes.
Don't trust the app. Watch it.
Most software asks for faith. A poppy runs where you can see it — and AgentsPoppy is built so that seeing is the default, not a feature. We won't tell you it's "more secure than the cloud"; we'll show you everything, visibly. This is what MailPoppy's footprint looks like on the live infrastructure map — every sphere a service, every pulse a dependency, every resource one click from its AWS console page:
A living screenshot, not a diagram: in the app this map is drawn from your account's verified state — and after a teardown it doubles as the proof that nothing was left behind.
Keys stay home
Your AWS credentials live on your computer, held by a local broker. No poppy ever sees them — each gets its own scoped, revocable credentials.
Keys to its own room, never the house
One canonical, published IAM policy — never admin. A poppy can only touch resources it created and tagged, and the broker keeps poppies out of each other's gardens.
A live map, not a mystery
Every resource a poppy creates appears on an infrastructure map, with an activity feed of every change pulled from your own cloud's audit trail.
Pause means pause
One switch stops a poppy's backend cold. One report button flags a bad actor. A local blocklist keeps it from ever running again.
Uninstall means uninstall
Removal isn't "we deactivated your account." One click deletes every tagged resource from your cloud — and then verifies nothing was left behind.
Open by rule
No poppy will ever be approved without an open repository. Not open-ish. Open — so anyone, or anyone's AI agent, can read exactly what it does.
The update asks. Your agent audits. You decide.
An update to a poppy isn't an app refresh — it changes infrastructure in your account. So it doesn't just happen. It arrives as a proposal, with the receipts attached — through an agent-ready audit pipeline we haven't found anywhere else.
- Read what it is. Every update names its source commit in the poppy's open repository — the full diff is one click away.
- Let your own AI agent audit it. One button copies a self-contained prompt. Your agent — not ours — reads the public diff and tells you if the code matches the description, and flags anything that touches your data, your permissions, or the network.
- Verify the bytes. The backend build is reproducible: anyone can rebuild it from the open source and confirm the exact hashes of what will be deployed. Nothing auto-applies. A human clicks Apply — and that human is you.
Honest scope: today the backend build — the code that runs in your cloud — is reproducibly verifiable; making the desktop app binary reproducible too is on the public roadmap. And an honest superlative: we don't know of another consumer app platform where every update to your own infrastructure arrives explained, diffable, and verifiable by your own AI agent before you choose to apply it. If you find one, tell us — we'd genuinely like to meet them.
Open code is not the same as an auditable update.
Here, your own AI agent reads every diff before it touches your cloud.
Go looking for a second platform that works this way. We couldn't find one.
MailPoppy: your email, growing in your own cloud.
A full email service — your own domains, mailboxes with end-to-end-encrypted storage, an iOS app and a desktop client — with no company server behind it. That's not the pitch. That's MailPoppy, shipped.
Your mail sits in your bucket, sealed with keys only your devices hold. No provider reads it, mines it, or holds it hostage — there is no provider.
Grow one. Your coding agent already knows how.
Poppies are built to be built fast — by you, or by the coding agent you direct. The SDK, the agent-onboarding docs and the design kit exist precisely so an idea can become a polished poppy in hours to a few days, not quarters. Start in the developer hub — tutorial, docs, and the marketplace policies in one place.
- AGENTS.md + SDKHand your coding agent the onboarding doc; it scaffolds a poppy that speaks the broker's protocol from the first commit.
- Design kitA ready-made visual language so your poppy looks like it belongs, from day one.
- Open repo ruleNo poppy will ever be approved without an open repository. Write code you're proud to be audited on — your users' own AI agents can read every diff before an update touches their cloud.
- MarketplaceThe curated catalogue is live, and sideloading stays free forever. Monetise however you like: free, open source, your own checkout — or the optional in-app checkout through your own Stripe, where you stay the merchant of record and the platform takes a flat, transparent 5% only on sales it processes. Selling outside it costs nothing. Submit your poppy →
What we're for. And what we refuse.
I. The cloud belongs to the people who use it.
Software should answer to the person it serves. We build so that apps run in their users' own clouds — legible, pausable, removable — and so that no company database has to exist in the middle of anyone's private life.
II. Privacy for people. Not impunity.
Privacy here means your data answers to you — it does not mean darkness. We will not let this platform shelter criminal activity, child exploitation, or illegal trade behind the word "privacy". Our architecture is the enforcement: every approved poppy's code is open, so what an app does is public even when your data is private; the directory is curated, reports are acted on, and a bad poppy can be blocked and torn out of every cloud it touched — by the very users it betrayed.
III. A future for the builders AI displaces.
AI is about to displace millions of developers and white-collar workers from corporations that will no longer need them. We refuse to treat that as someone else's problem. AgentsPoppy is built to be their next serious opportunity: a place where one person with an idea and an AI agent can ship — and own — what once required a funded team and millions in infrastructure. We didn't build this to accelerate the loss of livelihoods. We built it to hand the means of shipping software to the people automation displaces.
IV. Claims you can check.
Every promise on this page is designed to be verifiable: open source by rule, updates you can diff and rebuild, a map of everything an app does in your account. Where we haven't earned a claim yet, we say so. Trust that can't be checked is just marketing.