Monetisation
The model is deliberately simple: your users' infrastructure costs are theirs, your revenue is yours, and the platform takes a flat 5% only on sales its checkout processes. You are the merchant of record, on your own Stripe account. Sell outside the platform and we take nothing.
On sales processed by the in-app checkout (Stripe Connect). No listing fee, no annual fee, no tiers, no thresholds.
Distribute and sell however you like off-platform — your site, your invoicing, your customers. Not our business, not our cut.
Backends run in each user's own cloud account, on their bill. Your marginal cost per user is zero.
Stripe Connect verifies your identity and routes payouts straight to you. You keep your own Stripe relationship; the 5% application fee is deducted per sale.
A whole-poppy unlock or named premium features — one-time or subscription. The proven pattern across first-party poppies: free core forever + one premium feature. Prices are server-authoritative; what the catalogue shows is display-only.
The host renders a standard purchase element (<agentspoppy-purchase
product="pro">) with the live price; checkout runs in the platform. Your poppy never
touches card details.
Entitlement is verified server-side — isPurchased(id) via the
bridge, or for a companion app outside the container,
GET /api/entitlement?poppyId=…&productId=…&target=….
The target lets one purchase entitle a domain, a user, or a
license key in your own product. A signed webhook can notify your service on every sale.
No in-poppy paywalls, no steering. A listed poppy can't gate its own features behind an external checkout or steer users off-platform to unlock them. One checkout, one set of rules, for everyone — it's what lets users trust the buy button in any poppy.
“Manage billing” must always be visible when you sell. The standard button includes it; if you build custom UI, you must surface subscription management. Users can always see and cancel what they pay for.
Selling a genuinely separate product off-platform (your SaaS, your consultancy, your mobile app) is fine — the line is only about unlocking the poppy's own functionality. If your monetisation involves an external service that receives user data, declare it — see Data & privacy.