Skip to content

Clarify PCC usage and billing #471

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
markbackman wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −5
Open

Clarify PCC usage and billing #471

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
11 changes: 6 additions & 5 deletions deployment/pipecat-cloud/fundamentals/scaling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -241,13 +241,14 @@ Pipecat Cloud auto-scales your agents. For most cases, the only action you need

Pipecat Cloud bills based on:

- Active session minutes
- Reserved session minutes
- **Active session minutes**: Time your agents spend handling live sessions
- **Reserved session minutes**: Time your warm agent instances are kept running, even when idle

An active session starts when you call the `/start` endpoint (or CLI or SDK equivalent). The active session ends when your pipeline shuts down.
An active session starts when you call the `/start` endpoint (or CLI or SDK equivalent) and ends when your agent's pipeline shuts down.

Reserved session minutes are the time your warm agent instances are kept running, even if they are not handling active sessions. When active sessions start, the auto-scaler may provision further warm agent instances to support the next incoming request. Reserved session minutes are optional and controlled by setting `--min-agents` in your deployment configuration.
Reserved session minutes are optional and controlled by setting `--min-agents` in your deployment configuration.

<Note>
Both active and reserved session minutes are rounded up to the nearest minute.
Both active and reserved session time is measured to the second and billed in
minutes.
</Note>