Skip to main content
This page is the single source of truth for limits applied at each subscription tier. Limits apply at three levels: per-organization caps on team and project counts, per-service caps on a single service, and organization-wide pools that bound total resource usage across every service in your org. For pricing, see suga.app/pricing.

​
Plan Summary

Member, project and environment counts are per organization. A Free organization has one seat, so it cannot invite anyone.

​
Per-Service Limits

Each service can be configured up to these tier-specific maximums. The floor for any service is 0.05 cores and 64 MiB. A new service starts at 0.1 cores and 128 MiB.
Replicas multiply resource usage. A service configured with 2 CPU cores and 4 replicas counts as 8 CPU cores against your organization’s pool.

​
Organization Resource Pools

Beyond per-service caps, every organization has a shared resource budget across all services in all environments. Deployments are blocked when they would exceed any pool limit. TCP proxies are a paid feature. Free organizations cannot create one. You can see current usage against these pools on the Usage page in your organization sidebar.

​
Volume Limits

Volume sizes range from 1 GB to 1000 GB and count toward your organization’s storage pool. A Free organization has a 1 GB storage pool, so it can run one 1 GB volume.

​
Free Tier Bandwidth

At 5 Mbit/s a service sends about 625 KB per second, so large responses and file downloads are noticeably slower on the Free plan than on a paid one.

​
Free Tier Request Headers

Clients connecting to a Free plan service over HTTPS must finish sending their request headers within 120 seconds. This protects shared edge infrastructure from slow or stalled clients and does not limit how long a request may take once its headers have arrived. See Connection Timeouts for the timeouts that apply on every plan.
The bandwidth limit is applied when a replica starts. Upgrading to Pro does not lift it on services that are already running. Redeploy the service to clear it.

​
Log Retention

​
Images on the Free Plan

Free organizations can deploy Suga’s approved template images, or build from a connected GitHub repository. Deploying an arbitrary image from a registry requires a paid plan. See Templates for what is available.

​
CPU and Memory Ratio

Suga Cloud requires per-service memory to fall within 1 GiB to 6.5 GiB per CPU core. This applies to every service, on every tier.
A service configured outside this ratio is rejected before it deploys. Change CPU and memory together so the pair stays in range.

​
What Happens at a Limit

To increase your limits, upgrade your plan or contact us about Enterprise pricing.