Usage & billing

Open Settings → Account → Usage & Cost to review AI usage, hosted-AI budget state, plan limits, and billing entry points when billing is enabled.

AI Usage

Aurora tracks AI usage in two separate buckets:

• BYOK usage: calls made with provider keys you configured yourself.
• Hosted Aurora AI usage: calls made through Aurora's hosted AI gateway when your plan and workspace allow it.

Signed-in Usage & Cost history is cloud-backed, so moving between web and desktop or clearing one browser cache does not erase the account-level usage timeline.

Hosted AI Budget

Hosted AI is plan-limited and user-scoped. The hosted-AI budget is separate from your generic Usage & Cost budget controls.

Current plan contract:

Plan	Workspace limit	Storage limit	Hosted AI
Free	3 workspaces	100 MB per workspace	Not included
Plus	10 workspaces	1 GB per workspace	Included with limited monthly usage
Pro	30 workspaces	5 GB per workspace	Included with expanded monthly usage

The hosted-AI card in Settings → AI shows whether hosted AI is available, outside your plan, over budget, blocked by workspace mode/E2EE, or temporarily unavailable. The budget window resets on the first day of each UTC month.

Billing Portal And Checkout

When the billing provider is configured, Usage & Cost can expose checkout and billing-portal actions so you can review or update a paid plan from the app.

If billing is disabled, those actions may be hidden or return a clear disabled state. Existing content is not deleted by plan downgrades; enforcement blocks new work above the published limits instead.

Storage And Workspace Limits

AuroraCloud enforces workspace count and per-workspace storage limits server-side. If a workspace is above its storage limit, existing files remain available, but new uploads can be blocked until space is freed or the plan changes.

Local And Encrypted Workspaces

Browser-only and Local folders workspaces do not use hosted Aurora AI directly. Encrypted AuroraCloud workspaces also restrict hosted/server-side AI while locked, and server-side retrieval is unavailable for encrypted content unless the app explicitly supports that path.