Skip to content

docs: update pricing for free-plan credit limit stop behavior #706

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tembo wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: update pricing for free-plan credit limit stop behavior #706

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions resources/pricing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,11 +99,11 @@ Tembo Gateway and VM compute are metered while Tembo runs work such as:

What happens when your balance reaches zero depends on your plan and overage setting:

- **Free**: new sessions are blocked until you upgrade or add prepaid balance.
- **Free**: new sessions are blocked until you upgrade or add prepaid balance. A running session is also stopped immediately if it exceeds the free allowance mid-session, with a message in the chat explaining why.
- **Pro or Max with overages enabled**: sessions continue and are billed as overage after the included allowance and prepaid balance are used, up to the maximum overage limit you set. Once that limit is reached, new sessions are blocked.
- **Pro or Max with overages disabled**: new sessions are blocked as soon as the included allowance and prepaid balance are exhausted.

When work is blocked, the request is rejected immediately rather than queued. Work that has already started can continue its current session so its compute and inference are accounted for correctly.
When work is blocked, the request is rejected immediately rather than queued. On Pro and Max, work that has already started can continue its current session so its compute and inference are accounted for correctly. On Free, a running session is stopped as soon as it exceeds the allowance, rather than continuing to completion.

## Usage bursts

Expand Down