# Understand plans and usage

Learn what's included in your Rumata plan, how usage is measured, and what happens when you reach your limits.

Source: https://docs.rumata.dev/guides/billing
Reviewed: 2026-09-29

## Before you start

- Access to [Usage](https://app.rumata.dev/usage) in your Rumata account.

<a id="account"></a>

## 1. Choose your plan

Rumata offers three standard plans — **Builder, Pro, and Team** — as well as Custom plans for businesses with specialized requirements.

Each standard plan is available in two configurations:

- **Building (Infrastructure + AI):** Includes infrastructure, AI credits, and development-machine hours.
- **Infrastructure-only:** Includes the same infrastructure allowances without bundled AI credits or development-machine hours. These can be added separately.

Compare plan allowances

| Resource | Builder | Pro | Team |
| --- | --- | --- | --- |
| Factories | 5 | 11 | 24 |
| Development-machine hours* | 80 | 160 | 320 |
| Concurrent development machines | 1 | 3 | 7 |
| Database storage | 5 GiB | 11 GiB | 24 GiB |
| File storage | 10 GiB | 22 GiB | 48 GiB |
| Published frontend sites | 2 | 5 | 11 |
| Frontend requests / month | 200K | 440K | 960K |
| Workflow executions / month | 2,500 | 5,500 | 12,000 |

Development-machine allowances are included in Building plans and available as an add-on for Infrastructure-only plans.

All standard plans include one project and a hosted PostgreSQL database. Resources and allowances are shared across the Billing Account.

Custom plans offer tailored infrastructure capacity and additional capabilities based on your requirements.

Visit [Pricing](https://app.rumata.dev/pricing) for the complete plan details.

<a id="measurement"></a>

## 2. How usage works

Different resources are measured differently:

- **Development machines:** Count the time your machine is running.
- **Databases and storage:** Use a fixed storage capacity, rather than a monthly allowance that accumulates.
- **Workflows:** Count executions, including failed or cancelled runs.
- **Frontend:** Count published sites, deployments, and application requests.
- **AI:** Uses your available AI credits according to the models and operations you choose.

Monthly allowances reset each billing period. Unused allowances do not roll over.

<a id="usage"></a>

## 3. Check your usage

1. Open [Usage](https://app.rumata.dev/usage) from the sidebar.
2. Review how much of each resource you've used.
3. Compare your usage against your plan's allowances.
4. Check when your monthly allowances reset.

Some resources also have limits on how many can run simultaneously, even when monthly allowance remains.

<a id="limits"></a>

## 4. What happens when you reach a limit?

Rumata does not automatically charge for additional resource usage on standard plans.

When you reach a limit, the affected operation may be paused or blocked until additional capacity becomes available.

You can:

1. Wait for your monthly allowance to reset.
2. Stop or remove unused resources to free capacity, where applicable.
3. Upgrade your plan or add available resources.

**Your data is not immediately deleted when a limit is reached.** Available read, export, and recovery operations can remain accessible.

<a id="more-resources"></a>

## 5. Need more resources?

You can upgrade from Builder to Pro or Team as your application grows.

For specialized requirements, higher infrastructure capacity, or dedicated deployment configurations, contact Rumata about a Custom plan.

Visit [Pricing](https://app.rumata.dev/pricing) to explore your options.

## Related guides

- [Usage & pricing controls](https://docs.rumata.dev/guides/controls-billing)
- [Code and development machines](https://docs.rumata.dev/guides/development)
- [Workflows](https://docs.rumata.dev/guides/system-explorer-workflows)
- [Storage](https://docs.rumata.dev/guides/system-explorer-storage)
- [Troubleshoot with a clear next step](https://docs.rumata.dev/guides/troubleshooting)