A note on timing
The tiers
| Limit | Free | Starter | Pro | Team | Business |
|---|---|---|---|---|---|
| Price / mo | $0 | $25 | $50 | $100 | $250 |
| Records per app | 1,000 | 25,000 | 100,000 | 250,000 | 500,000 |
| Tables per app | 5 | 15 | 30 | 60 | 100 |
| Fields per table | 30 | 60 | 100 | 150 | 200 |
| Storage | 1 GB | 5 GB | 20 GB | 100 GB | 250 GB |
| Published apps | 1 | 3 | 10 | 25 | 50 |
| Builder seats | 1 | 1 | 3 | 10 | 25 |
| End users | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
| Monthly credits | 5 / day | 1,000 | 2,500 | 5,000 | 12,500 |
What's actually enforced today
Some limits block an action the moment you cross them; others are shown for planning but not yet gated. Knowing the difference saves a support ticket.
- Records, tables, and fields per app — enforced. A create that would exceed your plan is refused with a "plan limit reached" message.
- API access, custom domains, workflows and workflow steps — enforced from your plan.
- Storage — shown and tracked, but not currently a hard block. Treat it as guidance, not a wall.
- Credits, spending caps, and published-app slots — part of the new credit system that is rolling out; see the rest of this section.