Service Plans

Plans define customer resource allowances and portal permissions. Open Plans and choose Customer Plans for end customers or Resource Plans for organizations. Assign the plan through the owner's subscription.

Only customer plans are checked today. A Resource Plan's limits are saved and linked to the organization, but they are not enforced yet: nothing compares a reseller's total with its plan.

Configure a customer plan

Create or edit a plan's name, display name and description, then review:

• Total service count, CPU cores, memory, disk and bandwidth fields.
• Per-service CPU, memory and disk allowances.
• Portal permissions, such as viewing logs or starting and stopping services.
• Optional capabilities and their limits, such as BYOK, Metered AI, API keys and tenant MCP.
• Per-template instance quotas: absent/unlimited allows instances, zero blocks the template, and a positive number caps instances for that customer.

Plan names and quotas can be customized. Use the installed plan list rather than assuming a fixed Starter/Pro/Enterprise offering. Optional capabilities also have a global switch and per-customer overrides; a plan alone may not enable them.

What quota checks measure

The deployment quota check compares allocated CPU, memory and disk values from service records with the customer's active plan. This is not a measurement of used volume bytes. Service-count and per-template checks are separate gates; a resource picker warning is not the entire authorization or quota decision.

The check runs when a service is deployed for a customer. Changing the limits of a service that is already running is not checked against the plan. Resource Plans for organizations are not part of any check: the total across a reseller's customers is never compared with the organization's plan.

A lower plan does not automatically resize or stop existing containers. Review the allocation and the result of subsequent deployment requests. Do not rely on automatic notifications at fixed utilization percentages or on bandwidth fields as proof of a network traffic cutoff.

Billing

Plan allowances and usage displays help you operate the service. They do not collect payment or constitute an invoice. Keep your billing integration and reconciliation in your own system; store its reference on the subscription.