Publish and grow
Hosting
Where your published app runs, what running it costs in credits, what happens if you run low, and how Buildliy watches your live site.
When you publish, Buildliy hosts your app for you. There's no server to rent, nothing to configure and no separate hosting bill. Your live site and its database run on Buildliy, with a secure (HTTPS) connection included.
Running your app is paid from the same credits you build with, and every plan includes free hosting credits each month.
What's included
Every published app comes with:
- A live website at your free
buildliy.appaddress, or your own domain on Pro. See Publish your app. - HTTPS on every address, set up automatically.
- A private database of its own, if your app saves data. See Database.
- Your pictures, built in. Images the AI makes for your app, and pictures you attach in the chat, are saved with your app's code and go live with it.
- A place to keep files in Manage → Storage, including files visitors upload through your app. See File storage.
If you connected your own Supabase or Neon project, your app's data lives there instead, and that provider bills you for it. See Use your own backend.
What running your app costs
Once your app is live, what it uses is paid from your credits. Idle apps use almost nothing. A busy app uses more, because more visitors means more traffic and more database time.
| What's measured | What it covers |
|---|---|
| Database | Storing and reading your app's data (awake time, stored data, restore history and data transfer). |
| Server & traffic | Your app's pages, files and server code reaching visitors. |
| File storage | Files kept in your app's storage, such as videos or music made for it, and visitors downloading them. |
| AI in your apps | AI features your visitors use, like a chatbot. See AI in your app. |
Publishing and re-publishing don't use credits.
Free hosting credits every month
Every plan includes credits just for running your apps. They're used before your other credits, cover all your apps, and refresh each month. Unused ones don't roll over.
| Plan | Hosting credits | App AI credits |
|---|---|---|
| Free | 10 a month | 2 a month |
| Pro | 25 a month | 5 a month |
App AI credits pay for AI inside your apps, like a chatbot your visitors use, not for building.
See what your app uses
- In the app: open the Manage tab. The Overview shows Usage · last 30 days with a small daily chart and how many free hosting credits are left this month. Click See usage, or choose Usage in the left list, for the full breakdown by category.
- Across all your apps: click Usage in the left sidebar of your dashboard.
Running usage can take up to a day to appear, because some of it is measured hourly or daily.
If you run low or run out
You get an email when your balance runs low while you have live apps. The Manage tab also warns you when you're low or out.
If you run out, nothing is deleted. Here's what pauses, step by step:
AI in your apps pauses
AI features inside your apps, like a chatbot, stop working until you add credits.
Your app's database pauses
On Free, this happens as soon as the month's free hosting credits and your balance are used up. On Pro, databases get a small cushion first: they keep running until you owe more than 10 credits. While a database is paused, anything that needs it, like signing in, saving a form or loading saved data, doesn't work. Your pages stay online for now.
Your published pages pause
If credits still aren't added 2 days after that, your published pages pause too, and visitors see a short "paused" notice instead of your site. Pages can also pause sooner if an account owes more than a set limit.
We email you when your databases or pages pause.
Getting back online
Add credits (enough to cover anything you owe) and everything comes back by itself, usually within the hour. There's nothing to restart, and your apps, data and web addresses are just as you left them. Publishing after you've added credits also brings paused pages straight back. We email you when your pages are back online.
To avoid pauses, go to Settings → Spending and use Save credits to keep my apps running. Building stops when your balance gets down to that number, so your live apps always have credits left. You can also turn on auto top-up. See Credits and usage.
If you set a Stop usage spending limit for running your apps in Settings → Spending, reaching it pauses AI and databases in your apps until the limit resets. Published pages stay online.
Live-site health checks
Buildliy checks your published app every hour, the way a visitor would: it opens your home page and up to two other pages and looks for errors, missing pages and blank screens.
- If two checks in a row fail, a Your live site has a problem card appears above the chat box in your project, and we email you once for that problem. The card says what went wrong and when it started.
- See details shows the address, the page that failed, the pages checked and when it was last checked.
- Fix it asks the AI to find and fix the problem. It's a normal build and uses credits. If your site is paused, the card says so instead of offering a fix.
- When it recovers, you see "Your live site is back up." If we emailed you about the problem, we email you again.
The Launch tab (Workspace menu → Launch) shows the latest result in one line, like "Live site: working · checked 12 minutes ago".
Health checks tell you when something breaks. They don't keep your site from going down, and some sites can't be checked, for example when a page asks visitors for a password first.
Related
Still stuck? Read the FAQ or contact us.
