---
title: Stay inside the Free Allowance
description: Check whether a small database app fits the account's Free Allowance, using current rates, remaining balance and expected activity.
slug: /guides/stay-inside-the-monthly-free-usage
order: 46
visibility: public
redirects_from: [/guides/stay-inside-the-free-allowance]
---

# Stay inside the Free Allowance

Prompt:

> Can this small app with a database run for free? Tell me what would make it cost more.

Yes, a small app with a shared database can fit within your account's [Free Allowance](/cloud/concepts/glossary/#free-allowance). A server that stays awake all month, more storage or traffic, and paid extras can take the account over its Free Allowance.

Use this guide to compare the app's expected use with the current rates and what the account has left. Your applications and paid options share the account's Free Allowance, with no plan to choose. An app that stays within it needs no card and does not expire.

Free Allowance is enough for most static websites and for a small app with a shared database on Shared 0.5 GB that sleeps when idle. The **Static website** and **Small app** examples in the [calculator](https://turnzero.ai/pricing#estimate) fit without the introduction bonus. A server that stays awake all month can exceed the Free Allowance. Other apps and paid options share the same Free Allowance.

For a static website, open the [pricing calculator](https://turnzero.ai/pricing?example=static#estimate). Static hosting has no server, per-request or file storage charge; data transfer still counts against the account's Free Allowance. A custom domain, where available, is a separate monthly item.

## Before your AI starts

**For the AI tool:** Check these prerequisites before estimating.

- Check that your connection is signed in to the account that will hold the app ([Connect your AI assistant](/cloud/getting-started/connect-your-tool/)).
- Identify the existing app with `list_applications`, or ask which proposed app to estimate.
- Ask about expected use: how long production and development will stay awake, how much data and how many files will be stored, and what traffic, email and AI calls to expect. Mark unknowns explicitly.
- For an app that does not exist yet, read the `cost-estimate` skill with `read_context`, id `skill:cost-estimate`. For a live app, read `cost-review` with `read_context`, id `skill:cost-review`. This task reads and estimates; change settings or add services only when the person asks.

## Steps

**For the AI tool:** Read and estimate without changing the application.

### 1. Read the current amount and rates

Call `read_balance` for this UTC month's Free Allowance, what was drawn, what is left, the charged lines and any pause. Call `read_rate_card` for the current rates and units. The [pricing page](https://turnzero.ai/pricing) also lists them.

Use these readings for the estimate. A rate marked `unset` is unknown, not zero. If a required reading fails or an amount is unset, report what could not be read and stop short of saying the app fits.

Each UTC month brings the account's Free Allowance, including the introduction bonus while it runs. Free Allowance is available in full in the month the account is created and does not roll over. Read the pricing page for the bonus's terms.

### 2. Count what the app will use

For an existing app, read its size and `production_sleep` through `read_status`. Size alone does not tell you whether production sleeps. Read `read_usage` for measured quantities and its freshness information; recent activity may not be included yet. This read reports traffic and stored data, not server awake time. State awake time as a workload assumption rather than a measurement from this read.

| Item | What to count |
| --- | --- |
| Shared database | One monthly item for the app, covering production and development together. It stays charged while servers sleep, until the app is deleted. The bytes stored in the database are charged separately. |
| Production server | The seconds it is awake, each charged its share of the size's monthly rate. Divide awake seconds by the number of seconds in that actual UTC calendar month to estimate the share. Sleeping time draws nothing for that server. |
| Development server | Its awake time as a separate line, at the Shared 0.5 GB rate. Development always sleeps when idle. |
| Database and file storage | A day's share for the bytes held. |
| Data transfer | Bytes sent to clients, downloaded from storage, and sent out through the egress gateway. |
| Other use | Email recipients, including sign-in codes emailed to the app's users; platform AI calls; and account options or images that draw the same balance. |

A request to the server has no charge of its own. Storage and transfer still count.

A shared database, a custom domain once it has served, the 30-day log option and tzTrack AI reviews are [monthly items](/cloud/concepts/glossary/#monthly-item). Charged at the start of the month, or for the days left if added later. Removing an item returns nothing.

Shared 0.5 GB starts with production sleeping when idle, which can reduce awake time. Shared 1 GB starts with production's sleep setting off; count its continuous awake time in the estimate. Development's use counts too. Before deciding whether production may sleep, read [Start after idle and response time](/cloud/concepts/how-the-plans-differ-technically/#start-after-idle-and-response-time) for the idle period and the next request's delay. Follow [Size and usage](/cloud/guides/plan-and-usage/) for setting changes, and [Add a database](/cloud/guides/add-a-database/) for database setup.

### 3. Compare the estimate with what is available

Give two comparisons:

- **A full month:** add the database's monthly charge, production and development awake time, storage, transfer and other expected use. Include the account's other apps and options before comparing the total with its Free Allowance.
- **The rest of this month:** estimate only charges still to come across the account and compare them with the amount left. Do not count a database or another monthly item already charged this month a second time.

State the workload assumptions, the date of the rate and balance reads, and what remains unknown. Leave room for activity above the estimate. A low traffic count alone does not establish that the app fits: an awake server and the database's monthly item can draw usage without client requests.

If the estimate does not fit, identify which items account for it and what lower usage or requested setting changes would alter the result. Do not create the app, add an option or change its settings merely to complete this estimate.

### 4. Check actual usage as the app runs

Read `read_balance` again after the app has run and compare its charged lines with the estimate. **Balance & usage** on the signed-in site also shows the account's balance. Recheck when traffic, stored data, development use or options change.

Warnings arrive by email at 50% and 80% of the month's Free Allowance. When it is used up and the account has no live credit, the account's apps pause. A credit grant with credit left that has started and has not expired is live credit. A live operator's grant counts even while prepaid credit is not sold. Requests and deploy, promote, restart and resume are refused; management reads, settings, the deploy's check, export and deletion remain available. [Size and usage](/cloud/guides/plan-and-usage/#when-the-account-pauses) explains the pause.

The pause ends automatically at the first instant of the next UTC month. Monthly items are charged at the month's first daily pass, so a warning or pause can arrive on its first day. The renewed amount does not guarantee that the app will fit for the whole month.

## Expected result

Your AI tool reports whether the expected use fits, with the current readings, assumptions and uncertain items beside its conclusion. It distinguishes the whole month's budget from the amount left now and names when to recheck. This is an estimate, not a guarantee of future use.

If it cannot establish that the app fits, it says why and what reading or workload decision is needed next. Prepaid credit is not yet sold; buying prepaid credit is not a recovery step.

## Refusals

This table covers common refusals from the task's reads. See the [refusals reference](/cloud/reference/refusals/) for the full list.

| Refusal | Status | Cause | Remedy |
| --- | --- | --- | --- |
| `authentication_required` | 401 | The connection presented no accepted credential. | Ask the person to [sign in through the connected tool](/cloud/getting-started/connect-your-tool/), then repeat the read. |
| `application_other_account` | 403 | The app belongs to a different account from the connection's. | Compare `read_account` through the connection with the account that holds the app. Use that account's connection and an identifier from `list_applications`. |
| `no_such_application` | 404 | The identifier names no live app. | Read `list_applications` again and use an identifier it returns. If the app was deleted, stop estimating it. |
| `token_scope_refused` | 403 | The token's app scope does not admit this read. | Name the token's own app where the read accepts one, or use a signed-in account session or a token with the required reach. |
| `invalid_request` | 400 | A read received an invalid or unsupported argument. | Correct the argument named in `detail`, using the [action reference](/cloud/reference/action-catalog/). |
| `context_not_found` | 404 | The requested context identifier is not visible to the connection. | Call `read_context` without an `id` and copy the skill's identifier from its catalog. If the required skill is absent, report that and stop. |
| `context_changed` | 409 | The context changed while its chunks were being read. | Restart `read_context` at offset zero without a stamp, then continue with the new answer's stamp and `next_offset`. |
| `context_unavailable` | 503 | The context source could not be read. | Retry later. If it persists, report the refusal and its `detail`; do not claim the required skill was read. |

## Related

- [Size and usage](/cloud/guides/plan-and-usage/) covers usage readings, sleep settings, limits and pauses.
- [Add a database](/cloud/guides/add-a-database/) covers the database's declaration and setup.
- [Free Allowance](/cloud/concepts/glossary/#free-allowance) explains the account's Free Allowance and the static website estimate.
- The [action reference](/cloud/reference/action-catalog/) describes the balance, rate and usage reads.
