Usage & Quotas

OEC.sh tracks how much of your organization's resources are in use. The Usage tab in Settings shows your current allocations, plan limits, and how close you are to hitting them.

Resource Quotas

Your organization has three resource quotas that are tracked across all active environments:

These are allocations, not real-time utilization. When you create an environment and assign it 2 CPU cores and 4 GB of RAM, those resources count against your quota whether the environment is busy or idle.

How Quotas Are Calculated

The platform sums up the resource allocations from every active environment in your organization.

Example:

If your server has 8 CPU cores and 16 GB of RAM, you have 1 core and 2 GB of RAM remaining for new environments.

What Counts Toward Quota

• Active environments (running or stopped but not destroyed)
• Read replicas count at 30% of the primary environment's CPU and RAM, and 100% of its disk

What Does Not Count

• Destroyed environments (resources are released immediately)
• The platform's own overhead (monitoring, routing, etc.)

Viewing Your Usage

1. Go to Settings in the sidebar
2. Click the Usage tab
3. Review the resource breakdown

The Usage tab shows:

• Current allocation for CPU, RAM, and Disk
• Available capacity based on your connected servers
• Per-environment breakdown so you can see which environments are using the most
• Plan limits for projects, environments, servers, and team members

Plan Limits

Each subscription plan caps certain resources:

These are hard limits. You cannot create a 6th project on the Starter plan or add a 3rd team member on the Free plan.

What Happens When You Hit a Limit

Plan Limits (projects, environments, servers, members)

When you reach a plan limit:

• The Create button is disabled for that resource type
• A message tells you that you have reached the limit for your current plan
• Existing resources continue to work normally -- nothing gets stopped or deleted

You have two options: delete a resource you no longer need, or upgrade your plan.

Resource Quotas (CPU, RAM, disk)

When your servers do not have enough remaining capacity:

• You cannot create new environments with resource requirements that exceed availability
• The environment creation form shows how much capacity is available
• Existing environments are not affected

You can free up quota by reducing resource allocations on existing environments, destroying environments you no longer need, or adding another server.

Freeing Up Quota

Reduce Environment Resources

If an environment is over-provisioned:

1. Go to the Environment > Settings
2. Lower the CPU, RAM, or disk allocation
3. Redeploy the environment

This immediately frees the difference. An environment that was using 4 cores and now uses 2 releases 2 cores back to the pool.

Destroy Unused Environments

Environments that are no longer needed should be destroyed, not just stopped. A stopped environment still holds its resource allocation. A destroyed environment releases everything.

1. Go to the environment you want to remove
2. Click Destroy
3. Confirm the action (you can create a final backup first)

Add More Servers

Connecting additional servers increases your total available capacity. Each server's CPU, RAM, and disk add to the pool. This is the right approach when all your environments genuinely need their current allocations.

Quota and Replicas

PostgreSQL read replicas (available on Pro and Agency plans for Odoo 18 and 19) consume additional resources:

So an environment with 4 CPU cores and 8 GB RAM that adds a replica will consume an additional 1.2 cores and 2.4 GB RAM from your quota. Disk allocation doubles because the replica maintains a full copy of the data.

Troubleshooting

Usage numbers do not match what I expect

The Usage tab shows allocations, not actual utilization. An idle environment still counts its full allocation. Check whether you have stopped environments that are holding resources without being used.

I cannot create a new environment but my plan allows more

Your plan limit on environments might not be the issue. Check whether your servers have enough remaining CPU, RAM, or disk to accommodate the new environment's resource requirements.

Quota did not decrease after destroying an environment

It should update within a few seconds. Refresh the page. If it still looks wrong, the environment's destruction may not have completed -- check its status.