Guides
Plans and capacity
Your organization has one hosting plan. Its projects, environments and services share finite capacity; adding traffic does not trigger an automatic usage overage.
What you pay for
Starter, Standard, Pro and Scale have fixed base subscription prices. The table shows monthly billing before tax. Annual billing, member allowances and the full plan limits are on the pricing page. Beta or promotional terms are shown with your invitation and checkout; they do not change the normal published price.
| Plan | Monthly base | Service ceiling | Shared runtime | Persistent storage |
|---|---|---|---|---|
| Starter | €5 | 10 | 0.5 vCPU / 512 MiB RAM | Up to 10 GiB persistent storage |
| Standard | €20 | 50 | 1 vCPU / 2 GiB RAM | Up to 20 GiB persistent storage |
| Pro | €50 | 100 | 2 vCPU / 4 GiB RAM | Up to 50 GiB persistent storage |
| Scale | €100 | 250 | 6 vCPU / 12 GiB RAM | Up to 150 GiB persistent storage |
Service count is not a compute allowance per service
What happens at a capacity limit
The platform checks plan allowances when allocating resources. An operation that would exceed an enforced allowance is blocked rather than converted into an automatic overage charge. A workload can also run out of its available CPU or memory: fixed billing does not guarantee unlimited throughput or that an undersized application remains healthy.
If an action is refused, read its quota error, check existing workloads and then reduce the allocation, remove resources you no longer need, or choose a plan with enough capacity. An invited member shares the same allowance; inviting more people does not add resources.
- Runtime: budget CPU and memory for the services and replicas that run concurrently.
- Storage: persistent volumes and database disks consume the storage allowance even when an app sleeps. A detached volume still holds data until you explicitly remove it.
- Builds: plans have a build-start allowance separate from their runtime limits.
- Environments: staging and previews run real workloads and share the organization’s capacity.
Add storage without changing plans
Open your organization’s Billing & usage → Extra capacity to choose extra storage, review the price and continue to Stripe. Payment must be confirmed before extra capacity is granted.
Extra storage costs €0.12 per GiB per month before tax, from 10 to 1,000 GiB, and is sold on every current self-service plan (catalogue version 5 or later). It counts only while your base plan is active. Once your base plan is scheduled to end, extra storage stops renewing, and you are warned before a purchase that would run past the plan’s end. It adds no CPU or RAM and does not include backups or object storage. Fixed disk packs and protected storage packs are no longer offered. Outgoing transfer is included in every plan under fair use, with nothing extra to buy.
Extra storage renews monthly from the purchase date, including with annual base plans. It is paid separately: a base-plan trial or promotional discount does not apply, and buying extra capacity does not consume a first discounted base-plan payment. Review the final tax, total and renewal date before paying.
Under Your extra capacity, choose Stop renewal to cancel future storage payments. Paid capacity continues through its confirmed end date. Existing data is preserved; if allocated storage exceeds your remaining allowance, new storage growth is blocked until you free capacity or add capacity. Disks never shrink automatically.
Which costs are separate
Your hosting subscription does not include third-party AI inference, coding-agent subscriptions, domain registration, email delivery or payment-processing fees. Those providers charge under their own terms. Object storage on Codara is available by separate agreement and is not an included self-serve bucket allowance.
Enterprise capacity and commercial terms are agreed with Codara separately. Do not use a self-serve plan table to estimate an Enterprise contract.
Capacity metrics are different from an invoice
Use logs and resource metrics to see whether a workload fits. The organization’s subscription and billing records describe what it pays. Infrastructure allocation estimates and legacy operator cost or spend-cap views are operational figures, not the formula for a Starter, Standard, Pro or Scale subscription.
Sleeping changes resource demand, not the fixed base price
Plan several projects together
Start with the workloads that must run at the same time, leave headroom, and review their actual CPU, memory and restart metrics. Keep production and preview needs separate in your budget. Follow the multiple-project hosting guide for an example of organizations, workspaces and shared capacity.
Comparing this model with usage-based or per-instance billing? See how Codara Cloud compares with Railway, Render, Vercel and Heroku, including what a small app costs on each.
Last updated
