What changed in Cahaves Cloud.

A new account can create one organization by default. After your first sign-in, including GitHub or Google, Name your organization asks you to name it before opening the dashboard. To add another organization, choose Contact us in the organization switcher. Once Cahaves enables additional organizations, New organization becomes available, up to the existing limit of 10. Staff can also create an organization for you and assign its invoicing client. If additional creation is later turned off, every organization you already have stays available, with its projects and billing unchanged.

More in Organizations.

One sign-in can now hold up to 10 organizations, so a person who runs more than one company keeps each apart. Each organization has its own projects, its own workspace and its own bill: its card or invoices, its monthly limit and its statements, with its invoices addressed to it. The switcher at the top of the sidebar moves between them and makes another with New organization, and Settings, Organization renames the one you are in. Your sign-in, SSH keys, git providers, notification channels and backup destinations serve all of them, and the free allowance is yours rather than each organization's. An existing account already has one organization, named after you, with everything it had in it, and a new account names its first at its first sign-in. A billing email names the organization it is about and opens its billing. Members, moving a project between organizations and deleting an organization are not offered yet.

More in Organizations and Billing.

Cloud no longer takes payment in advance. Each hour is counted as before, and on the 1st of each month the month before is added up and charged to the card Paddle keeps for your account, or sent as an invoice if Cahaves bills your account that way. Billing shows your card under Payment method, the month so far under This month, and every closed month under Statements, with its document and Pay now when something is owed. Your first nano service, and your first nano database's free data, still need no card. Every account has a monthly limit, which refuses new paid work that would take the month past it and never stops what is running. Top-ups, the wallet, low-balance warnings and the grace period are gone, and credit you paid for and had not spent is refunded through Paddle.

More in Billing and Add a card and read your bill.

A database is no longer charged by the hour for its size. For each hour it runs, it is charged by the data it holds, at a rate per GB-month for its size and pool, and a stopped database costs nothing. Cloud measures what each database holds once an hour, and its page shows the figure and when it was measured. The size still sets its CPU and memory. Applications and compose stacks are charged by the hour as before.

More in Billing and Databases.

Each account's first nano application in the shared pool now runs free, and its first nano database holds 0.5 GB of data free, with each GB past that charged at the nano database rate. The console marks both Free. If you delete the free one, or change its size, your next oldest nano service or database takes its place from the next hourly count. Compose stacks are not included.

More in Billing.

From 8 October 2026, 05:00 UTC, Nano costs $1.50 for a month of running, up from $1.00, and Small, Medium, Large and Extra large cost 29 percent less: $2.99, $5.99, $12.01 and $24.02 a month on shared capacity, and dedicated capacity lower by the same share. Hours already charged keep the rate they were charged at. The Size menu and the Order summary show each rate, and the pricing section of this site lists them all.

More in Sizes and replicas.

The first time you open the dashboard, Cloud offers a short tour: a step for each section of the rail, from Dashboard to Support, saying what it holds, with the section highlighted. Each screen has a tour of its own too, which opens the first time you open it and points at its controls, such as Deploy on a service or Add credits on Billing. Skip tour ends any of them at any step. Finishing or skipping a tour is remembered on your account, and Take the tour in the account menu starts the one for the screen you are on again.

More in A tour of the console.

A Paddle payment that did not match its checkout, in another currency or for another amount, reads Held for review in the Top-ups table and credits nothing until support checks it. Support can now credit it from the top-up itself: it turns Paid, and the wallet history reads "Held payment credited after review by Cahaves support." If Paddle refunds that payment later, the refund takes the same credits back. Support can still refund it at Paddle instead.

More in Billing.

A database deployment whose image took longer than half a minute to pull could stay Deploying for two hours with "The engine has not confirmed this deployment's outcome", though the database was up. Cloud now reads the platform's own status for the database and the container it started, and ends the deployment Done or Failed as soon as the platform does. A build waiting behind other builds shows as waiting rather than in doubt, and one the platform dropped from its queue ends Failed at once instead of after two hours. A read the platform misses once no longer raises the warning. A database deployment's page now shows the Database log, since a database has no build log.

More in Deployments and Logs.

In the dark theme, the labels of the payment form, such as Name on card and Card details, came out dark grey on the dark page. The form now sits on a light panel in the dark theme, so every label and field reads as it does in the light one.

More in Billing.