What happens when my app's free tier runs out?

Because an app you built with AI is several services joined together. Your hosting keeps it online, your database stores users and their data, and other services send email, take payments or answer AI requests. Each has its own free tier, its own limit and its own rule for what happens next.

So "the free tier ran out" is rarely one event. Usually one service hits its limit first, and the part of the app that depends on it stops behaving.

In our reading of common pricing pages, these are the usual outcomes:

• It stops. The service refuses new requests until the next billing period or until you upgrade. Sign-ups may fail, emails may not send, or AI answers may stop.
• It slows down. The service lets requests through more slowly, or turns some away with a rate limit. Users see errors that come and go.
• It starts charging. The service keeps running and bills you for what you used above the limit, often only if you added a payment card.
• It pauses the project. Some services pause a free project after a period with no activity, or when it passes a limit. A paused database can take the whole app down with it.

None of these is always good or always bad. A hard stop protects your wallet but breaks the app for users. Automatic charging keeps the app up but can surprise you. What matters is that you choose, instead of finding out from a user.

Usually by email, sent to whatever address you signed up with. That is often a personal inbox you rarely check, or the address your app builder created for you.

Other signs: users say they cannot sign up or log in, pages load with errors, or a feature that worked yesterday returns nothing. If several things break at once, check the database first, because most of the app reads from it.

1. Find which service hit its limit. Open each service's dashboard and look for a usage or billing warning.
2. Decide: pay, wait or cut. Upgrade if real users are waiting. Wait if the limit resets soon and nobody is affected. Cut the cause if one feature or one visitor is using far more than expected.
3. Check your data. Make sure nothing was deleted and that you can export it. Do this before you change plans.
4. Tell your users. One short, honest message beats silence.

• List every service your app uses, with its free limit, what happens at the limit and its next paid step. How much it costs to run an app shows how to build that list.
• Send every warning to an inbox you read. Change the account email where you can.
• Set a spending alert or limit on every service that offers one, so a busy week cannot become an expensive one.
• Close the open doors. If anyone can use an AI feature without signing in, strangers can use up your limit.
• Keep a copy of your data. Export it now and then, so a paused or locked account does not take your users with it.

With only a few testers, you may never reach a limit, and your time is better spent finding users. That is mostly right. But the work above is short, and it decides whether your first good day ends with new users or with an app that stopped working.

Stack Picker suggests one set of tools you can build and run on your own, one for each layer, each with a reason. It does not quote exact limits or prices, so you still check each pricing page. If your app only works on your own computer so far, start with why your app works on your laptop but not for your friends.

Open the dashboard of every service your app uses. For each, write down three things: the free limit, what happens when you pass it, and which inbox gets the warning. Fix the inbox first.