Manage Egress usage
What you are charged for
On the Platform API, you are charged for network data transmitted out of the system to connected clients. Egress is measured across all services and billed based on underlying AWS usage.
Egress applies to all infrastructure models:
- Silo – dedicated infrastructure per tenant
- Bridge – shared infrastructure with logically isolated resources
- Pool – fully shared multi-tenant infrastructure
Depending on the model, traffic may be routed differently, but all outbound data transfer is accounted for as egress usage.
Egress is incurred across all services, including Database, Compute, Storage, Edge Functions, Realtime, and Log Drains.
Database Egress
Data sent to the client when retrieving information from your database.
Example: A user views their order history. The client requests data from the database, and the results are returned to the client, contributing to database egress.
The Platform API supports multiple database access paths, including direct SQL connections, HTTP APIs, and connection pooling layers depending on your infrastructure model (Silo, Bridge, or Pool).
On usage dashboards, database egress may be grouped differently depending on whether traffic is routed through a shared connection layer or directly from the database.
Compute Egress
Data sent from the compute services to clients such as sign-in, sign-out, user creation, etc.
Example: A user signs in, and the system returns session tokens and identity data to the client, contributing to compute egress.
Storage Egress
Data sent from object storage to clients when downloading or retrieving assets such as files, images, or documents.
Example: A user downloads a PDF invoice from storage, generating storage egress.
Edge Functions Egress
Data returned to clients from serverless or edge-executed functions.
Example: A checkout request triggers an edge function that processes payment and returns a confirmation response.
Realtime Egress
Data pushed to clients via realtime subscriptions.
Example: A subscribed client receives live inventory updates as stock levels change, generating realtime egress.
Shared Pooler Egress (when applicable)
When using a shared connection pooler layer (available in Bridge and Pool models), database traffic passing through the pooler is measured separately.
To avoid double counting, database egress is not additionally billed for traffic already accounted for at the pooler layer.
Example: A backend query returns invoice data through a shared pooler; this traffic is billed as shared pooler egress.
Log Drain Egress
Data sent to external logging systems configured via log drains.
Example: Application logs streamed to an external observability platform are counted as log drain egress.
Cached Egress
Cached and uncached egress are billed independently under AWS-based pricing.
Cached egress typically occurs when responses are served from edge cache layers (for example, CDN-backed storage responses).
How charges are calculated
Egress is measured in gigabytes (GB) and billed based on AWS network transfer rates, plus Platform API processing and routing overhead.
Charges apply only after exceeding the included quota in your subscription plan. This quota is shared across all services and infrastructure models (Silo, Bridge, Pool) and is referred to as the Unified Egress Quota.
Usage on your invoice
Usage is shown as:
- Egress GB
- Cached Egress GB
on your invoice.
Pricing
Pricing is based on AWS data transfer rates with Platform API aggregation and billing layers applied.
| Plan | Egress Quota (Uncached / Cached) | Over-Usage per month (Uncached / Cached) |
|---|---|---|
| Pooled | 5 GB / 5 GB | AWS-based overage rates |
| Pro | 250 GB / 250 GB | AWS-based overage rates |
| Team | 250 GB / 250 GB | AWS-based overage rates |
| Enterprise | Custom | Custom |
Billing examples
Within quota
Egress usage remains within the included quota, so no additional charges apply.
| Line Item | Units | Costs |
|---|---|---|
| Pro Plan | 1 | $25 |
| Compute Hours Small | 730 hours | $15 |
| Egress | 200 GB | $0 |
| Cached Egress | 230 GB | $0 |
| Subtotal | $40 | |
| Credits | -$10 | |
| Total | $30 |
Exceeding quota
Egress usage exceeds included limits and is billed at AWS-based overage rates.
| Line Item | Units | Costs |
|---|---|---|
| Pro Plan | 1 | $25 |
| Compute Hours Small | 730 hours | $15 |
| Egress | 300 GB | $X.XX |
| Cached Egress | 800 GB | $X.XX |
| Subtotal | $61 | |
| Credits | -$10 | |
| Total | $51 |
View usage
Usage page
You can view egress usage on the organization's usage dashboard. The page aggregates usage across all projects by default, with filtering available by project and time range.
In the Total Egress section, you can inspect usage over time and break it down by service. Cached egress is shown separately for clarity.
Custom report
- Open the Observability page in project
- Click New custom report
- Add charts for Database, Storage, Compute, Realtime, or Edge Functions egress
Debug usage
To understand what drives egress usage, analyze high-throughput endpoints and queries.
Frequent database queries
Use query performance insights to identify:
- Most frequently executed queries
- Average rows returned per query
- High-volume read operations
Most requested API endpoints
Use logs explorer to identify:
- High-traffic API routes
- Frequently called edge endpoints
- Services generating the most outbound traffic
Optimize usage
- Reduce selected fields in database queries
- Avoid returning full rows when unnecessary
- Cache frequent responses where possible
- Batch API requests instead of multiple small calls
- Optimize realtime subscription granularity
- Clean up large file transfers or reduce payload sizes in storage
- Review log drain volume and disable unnecessary logging streams
Exceeding quotas
If you exceed your included quota:
- Paid plans without spend caps: overages are billed automatically based on AWS usage rates
- Paid plan with spend cap enabled: usage may be throttled or placed into a grace period with notifications
For more details, refer to billing controls and fair usage policies in your Platform API account settings.