diff --git a/src/docs/src/user-pays-model.md b/src/docs/src/user-pays-model.md index ceb5bdf28..7563721f0 100644 --- a/src/docs/src/user-pays-model.md +++ b/src/docs/src/user-pays-model.md @@ -3,68 +3,32 @@ title: User-Pays Model description: Discover Puter.js User-Pays Model and how it allows you to build applications without worrying about infrastructure costs. --- -The User-Pays Model means your users cover their own cloud and AI usage. Instead of you, as a developer, paying for servers and APIs, users bring and pay for their own AI, storage and other features you've built into your application, making your app practically free to run! +The User-Pays Model means your users cover their own cloud and AI usage, instead of you, the developer. Each user pays for the resources they consume in your app through their own Puter account. Whether you have 1 or 1 million users, your infrastructure cost stays at $0. -When users interact with your Puter.js-powered apps, they handle their own resource consumption. This means you can include powerful features without worrying about the costs; whether you have 1 or 1 million users, you pay nothing for the infrastructure to run your application. +## How it works + +- Users sign in to your app with their Puter account, and that account covers the AI, storage, and other resources they use. Their usage never touches your bill. +- Every user starts with a free monthly allowance, enough to test out the platform and use apps built with Puter.js. They can track their usage in the [usage dashboard](https://puter.com/dashboard#usage). +- If a user runs out of their allowance, Puter prompts them to upgrade for more, or they can do it themselves in their [billing settings](https://puter.com/dashboard#billing). + +
When you, as a developer, use your own app, you are also subject to the User-Pays Model: you cover your own usage like any other user.
## User-Pays Model vs. Traditional Model -With traditional model of building applications, you have to set up servers, databases, and cloud services before you even launch. If you use cloud services like AWS or Google Cloud, you have to configure those, manage API keys, and set up billing. +| | Traditional | Puter.js | +| --- | --- | --- | +| **Servers & databases** | You set up and pay | None needed | +| **API keys** | You manage and secure them | No API keys at all | +| **Billing** | You pay for all users' usage | Each user pays their own | +| **Scaling** | Costs grow with users | Zero cost at any scale | +| **Abuse protection** | Rate limits, CAPTCHAs, quotas | Not needed; abusers pay for themselves | -Puter.js with user-pays model solves this, so you can build applications without worrying about server bills, scaling costs, or usage spikes. +## Advantages -## Advantages of the User-Pays Model - -**1. Zero Server, AI, and APIs Costs** - -The most significant advantage is that, as a developer, you don't pay any infrastructure costs when using Puter.js. Whether your app serves one user or one million users, your costs remain the same: zero. Practically infinite scalability at no cost. - -**2. No API Keys Needed** - -The User-Pays Model makes true serverless architecture a reality. You don't need to: - -- Manage various AI and cloud services -- Worry about securing your API keys usage -- Ask users to bring their own API keys - -**3. Built-in Security** - -The authentication and authorization are handled by Puter's infrastructure: - -- Users authenticate directly with Puter -- Your app operates within the permissions granted by the user -- Data is protected through Puter's security mechanisms - -**4. No Anti-Abuse Implementation Required** - -You don't need to implement: - -- Rate limiting -- CAPTCHA verification -- IP blocking -- Usage quotas -- Fraud detection - -Bad actors have no incentive to abuse the system because they are paying for their own usage. - -**5. Simpler Codebase** - -Since cloud, AI, and other APIs are all handled through Puter.js: - -- Your codebase is significantly simpler -- You can focus entirely on your application's unique functionality -- Frontend-only development is possible for many applications - -**6. Simplified User Experience** - -For your users: - -- Single sign-on through Puter -- Unified billing through their existing Puter account -- No need to create accounts with multiple service providers - -
- -## Everybody wins! - -The User-Pays Model enables you to build advanced applications with AI, cloud storage, and auth, all from the frontend, without worrying about infrastructure, security, or scaling. It's a win-win situation where developers can ship without the cloud services costs, and users only covering for what they use. +- **Zero infrastructure costs**: no server, AI, or API bills, at any scale. +- **Perfect for vibe coding**: build and ship apps with AI without fear of a surprise bill. If your app goes viral overnight, each user still covers their own usage. +- **No API keys**: no keys to buy, secure, or ask your users to bring. +- **Built-in auth & security**: users sign in with Puter; your app runs within the permissions they grant. +- **No anti-abuse code**: bad actors pay for their own usage, so there's no incentive to abuse your app. +- **Simpler codebase**: cloud and AI are handled by Puter.js, so many apps can be frontend-only. +- **Better UX**: single sign-on and unified billing through the user's existing Puter account.