Why your own accounts
While you build, Piye provides sign-in, email, payments and the rest, so your app works from the first minute. A live app is different: your customers, your money, your data. So it runs on your accounts, and you stay in charge of them.
Piye only asks for what your app really uses, one account at a time, with the steps to get each key. Under Your accounts in Publish, each row says what it's for and whether it's connected.
Every account an app may need
| For | What you need | Piye's help |
|---|---|---|
| The database | Nothing | Piye makes the live database for you, on Piye's database account, at no cost to you. Whenever you want it in your own account (at Neon, the database company), Claim your database: the app keeps working, nothing to change. |
| Payments | A Stripe account | Paste a test key first, a live key once Stripe has checked your business. Piye sets up Stripe's payment notices. See Payments. |
| A Resend account and a domain you own | Add the domain in Resend, paste the key and your From address. Piye checks that your app can send. See Email. | |
| Google sign-in | Your own Google sign-in app | Piye shows the two addresses to add and takes the Client ID and secret. Email sign-in works until it's added. See Sign-in. |
| Phone verification | A Twilio account | Paste the Account SID and Auth Token; Piye makes the verification service. See Phone verification. |
| AI in your app | A key from Anthropic, OpenAI or Google | Sign in to their console, add a payment method, create a key, paste it. Until then, the live app answers through your host with a basic model. |
| The host | An account at Vercel (or Cloudflare Pages, Railway, Hostinger) | You sign in once from Piye. |
If your app connects to something else, its own code says so, and Piye lists it under Your app's own code reads these: give each the value it has online.
If your app needs none of this, Piye says: Your app doesn't need any accounts of yours to go live.
Where your keys are kept
Your keys are kept in your computer's secure storage (the Keychain on a Mac), never in your app's files. Piye sends them only to your host, when you publish, so your live app can use them. Piye's own AI never reads them.
Test first, then real
Most services have a test mode. Connect test keys first, publish, and try everything on the live site. When it all works, replace the key with the live one in Your accounts (Replace the key) and publish again.
Tip
Set a spending limit in each paid service's own dashboard (your AI provider and Twilio especially), so a surprise never becomes a big bill.