Billing & pricing
The plan ladder, per-project pricing, the seat pool, addons, and when changes take effect.
The plan ladder
CloudWady's plan ladder is project-level: each project picks its own plan. Higher plans unlock more environments, larger seat allocations, and access to plan-gated features like white labelling.
| Plan | Best for | Includes |
|---|---|---|
| Free | Single production app, getting started | 1 production env, no staging, basic seats |
| Essential | Small teams, single delivery project | Production + staging, baseline seat allocation |
| Pro | Multi-environment delivery | Prod + staging + dev, larger seat pool, plan-gated features |
| Premium | Multi-tenancy at scale (agencies) | Highest seat allocation, all features, priority support |
The live numbers (price, seat allocations, environment counts) are published on the /pricing page. The docs above describe what the plans shape; the pricing page is the canonical source for current rates.
How the seat pool works
"Seats" are the per-company headcount of users that can access CloudWady. Two rules apply:
- MAX across projects, not SUM. If a company has two projects on different plans, the seat pool is the LARGEST plan's seat allocation — not the two added together.
- Zero means zero. A plan listing 0 seats means 0 — not unlimited. A company on Free with 0 plan seats has only the seats it has purchased explicitly as addons.
The total pool is MAX(plan seats across projects) + sum(seat addons purchased).
Addons
Addons are line-items the company purchases independently of a project plan. Today's catalogue:
- Extra seats — additive on top of
MAX(plan seats). Priced per seat. - White label — replace CloudWady branding with your own across the dashboard: a custom logo (with separate light and dark variants), favicon, brand colour palette, custom title, and a website URL the sidebar logo links to. Available on a Pro plan or higher; a single subscription covers the whole company.
Addons appear as separate lines on the invoice with their own start/end dates. They survive plan changes — switching a project from Pro to Essential doesn't auto-cancel addons; you cancel them explicitly when you don't need them.
Addon displacement
When you activate a new addon of the same type as an existing one (e.g. switching white-label tier), the prior active subscription is automatically marked as superseded with an end-date one day before the new one starts. No double-charging.
When plan changes take effect
Two flavours:
Immediate change
For when a customer needs a new plan now — typically an upgrade ahead of a launch. CloudWady clips the current pricing's end-date to today and starts the new pricing tomorrow. The next invoice prorates.
Next-period change
For planned moves at renewal. The new pricing's start-date is the current pricing's end-date + 1 day; no overlap, no proration. The current invoice cycle finishes uninterrupted.
Invoicing
Invoices are generated by the Odoo accounting module against the company partner. Each invoice line comes from one of:
- A project's active pricing window (one line per project).
- An active addon subscription (one line per addon).
- Usage charges if the plan includes consumption-based components (storage, bandwidth) — not yet on the catalogue.
Subscriptions renew automatically on the configured cadence (monthly or annual). The first invoice in a window is the only place proration appears; subsequent renewals are full-cycle amounts.