How should you organize personal and shared projects?
Your login is your identity; an organization holds its billing and members. You can own or join several organizations. Within an organization, workspaces group projects and control access. You do not need a new paid plan for every project.
For example, keep your portfolio in a restricted workspace and a collaborative product in another workspace. Each app has its own project, with production and staging environments inside it. Owners and admins retain access; a restricted workspace is not hidden from the organization's administrators. This is a suggested layout, not a customer case study.
| Boundary | Use it for |
|---|---|
| Organization | Separate billing, membership and plan capacity. |
| Workspace | A group of projects shared with selected members or the whole organization. |
| Project | One app or product with its own environments. |
| Environment | A production, staging or preview version with its own services and data. |
Does “up to 50 services” mean 50 full-sized apps?
No. A service count is a ceiling on how many services you can configure, not a separate CPU and memory allowance for each one. Runtime capacity is shared by running services, replicas and environments. A database and a staging copy need capacity too.
Start with the actual memory and CPU needs of your workloads, then leave room for traffic and background work. The table below uses the same plan data as the pricing page. Monthly prices are before tax; annual billing and the full set of limits are listed on the pricing page.
| Plan | Price / month | 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 |
How do you check whether your projects fit?
Make a resource budget for every workload that must run at the same time. Include each replica and the environments you keep online. Compare that total with the plan's runtime allowance, and check the per-service cap separately. Storage and build-start allowances are additional limits, not replacements for runtime capacity.
As arithmetic only: three processes budgeted at 300 MiB each plus a database budgeted at 600 MiB total 1,500 MiB. That is below the current Standard 2,048 MiB allowance, leaving 548 MiB before the limit. It is not a sizing recommendation: database growth, workload spikes and CPU requirements still need measurement.
Cost saver can let an idle HTTP service sleep and wake on the next request to its codara.cloud address. Requests to a custom domain do not wake it, so keep those services Always on. Use it where waiting for a wake-up is acceptable. It does not turn disk space into memory or remove the need to budget for services when they are awake.
Do invited teammates need their own subscription?
No. An invited teammate signs in and joins the organization without buying a personal hosting plan or supplying a beta access code. Standard includes up to 25 members and Pro up to 50, counting the owner. Those members share the organization's existing hosting capacity; adding someone does not add compute.
New workspaces start restricted. Owners and admins choose which members can access them or share them with everyone in the organization. Someone who also wants their own separate hosting can create another organization and complete its access and billing setup.
When should projects use separate organizations?
Use a separate organization when another customer or business needs its own billing owner, membership boundary and capacity budget. Use workspaces when projects should share a bill but have different collaborators. Several organizations under one login have separate plans; they do not pool their allowances.
Test one project first, record its resource needs, then add the next. That makes it easier to see which app caused a change in usage and when a larger plan is justified. Codara Cloud is in beta: we review every access request and invite builders when we can offer a place.