Plans and limits
Plans and limits control access to costly Atlas actions such as source processing, chat, map generation, attachments, and account-level billing operations.
What limits can affect
| Area | Examples of affected actions |
|---|---|
| Sources | Uploading files, importing URLs, processing PDFs, transcript extraction. |
| Chat | Grounded answers, long context requests, attached files. |
| Maps | Knowledge map generation, refresh, or export behavior. |
| Summaries | Source or project summary generation. |
| Attachments | File size, file type, or number of attachments. |
| Account | Subscription state, payment method, invoice access, cancellation. |
Free and paid plans
Atlas may provide limited free usage for evaluation and paid plans for heavier research. The exact limits shown in the product or billing flow are the source of truth.
Public docs should describe categories of limits and expected behavior, not hard-code numbers that can drift from pricing or billing configuration.
What happens at a limit
When a limit is reached, Atlas should block the action or ask for an upgrade before starting expensive work. A clear limit message is better than a silent partial result.
After a limit message:
- read the message
- check which action was blocked
- reduce scope if possible
- open billing if the action requires a different plan
- retry only after changing the plan, account state, file, or request.
Billing state
Subscription and payment method changes happen through the billing flow. Atlas may need a refresh or short sync period before the new billing state appears in the app.
Documentation rule
When changing pricing, quotas, trial policy, or paywall copy, update this reference and Troubleshoot billing and limits in the same change.