Pixetric DocsPricing & quotas
Understand how Pixetric meters usage and which limits apply
Pixetric follows a usage-based model: you pay for the compute seconds you consume, while storage and data transfer remain predictable.
Plans
| Plan | Designed for | Included features |
|---|---|---|
| Developer | Side projects, hackathons, CI branches | 1 always-on branch, 10 preview branches, 5 GB storage, community chat |
| Scale | Production SaaS workloads | Unlimited branches, autoscaling compute up to 16 vCPU, PITR, metrics/alerts, global reads |
| Dedicated control plane | Regulated or high-volume customers | Single-tenant storage fabric, private networking, custom SLOs, Slack support, migration assistance |
Metering
- Compute – billed per-second while a pool is running. Autosuspend prevents surprise bills when branches go idle.
- Storage – charged per GB per month, aggregated across all branches (copy-on-write keeps it efficient).
- Data transfer – outbound traffic over the free allowance is billed per GB. Traffic between Pixetric regions is included.
Free allowances
- First 5 GB of storage per project.
- 100 compute hours per month for preview branches.
- One free read replica in a secondary region for 30 days after onboarding.
Hard limits
- Maximum 100 concurrent branches per project (contact sales to raise).
- Up to 500 concurrent connections per compute pool; pooling is recommended for serverless workloads.
- PITR retention defaults to 7 days on Developer, 30 days on Scale, configurable to 90+ on Dedicated.
Use the dashboard billing view to monitor spend in real time. When you are ready for enterprise features—private networking, custom regions, or longer retention—reach out to sales and we will tailor a plan.