Deploy your apps.
We run the servers.

An application built from a GitHub repository or run from a public Docker image, a compose stack, or a database: PostgreSQL, MySQL, MariaDB, MongoDB or Redis. The catalogue also creates n8n, Hermes Agent and OpenClaw with their storage and settings in place.

In the docs: How Cloud is organised

No. Cloud reads the top directory of a repository and picks how to build it: with its Dockerfile when it has one, and otherwise with a builder that needs none, or as a static site. For a Node project it fills in the commands from package.json and the package manager from the lock file. The build runs on Cloud's shared build server, and every choice can be changed on the service's Source card.

In the docs: Build settings

With GitHub or Google, through your Cahaves account. The first press of either button creates the account, and Cloud keeps no password of its own. An account is one person, who holds one or more organizations, each with its own projects and its own bill. An organization has no members yet.

In the docs: Sign in and your Cahaves account

Yes. One sign-in holds up to 10 organizations, and each has its own projects and its own bill: its card or its invoices, its monthly limit and its statements, with its invoices addressed to it. The switcher at the top of the console's sidebar moves between them. Your SSH keys, git providers, notification channels and backup destinations serve all of them. The free allowance is yours rather than each organization's, counted once across all of them. Members, moving a project between organizations and deleting an organization are not offered yet.

In the docs: Organizations

By the hour, and once a month. At the start of every hour Cloud counts what is running. An application or a stack is charged that hour at the rate of its size, so an application with three replicas running costs three times its rate. A database is charged by the data it holds, at a rate per GB-month for its size. Your first nano service runs free, and your first nano database holds 0.5 GB free, with no card needed. On the 1st, Cloud adds up each organization's month before and charges it to the card Paddle keeps for that organization, with tax added where it applies, or sends an invoice if Cahaves has agreed to bill it that way. A stopped service costs nothing, and volumes, backups and domains carry no charge of their own. The rates are in Pricing, above.

In the docs: Billing

Cloud emails you, naming the organization, and its Billing offers Pay now, where you can pay with the same card or another. Until the month is paid, Cloud refuses new paid work in that organization: creating, deploying, starting, restoring or resizing a paid service, and opening a paid database's public access or choosing its settings before its first start. If the month is still unpaid on the date in Cloud's email, the organization's paid services stop until it is paid. A month closed with no card and an invoice past its due date count the same way, and so do paid services run with no card on file. The free service and database keep running and are never refused, and your other organizations carry on. If the paid services stay stopped for 30 days, Cloud archives them: it takes a final backup of each one's data, deletes the service, and keeps the backups for 30 days for you to download from Storage before deleting them. Paying before the archive date keeps everything; paying after it restores nothing. Each organization also has its own monthly limit, which refuses new paid work that would take its month past it, and stops its paid services once what the month has been charged reaches it, until the next month begins or the limit is raised. A stop for the limit is never archived.

In the docs: Billing

Yes. An application gets an HTTPS address on the platform's domain after its first successful deploy, and you can add a hostname of your own to an application or a compose stack. The console lists the records to create at your DNS provider: a TXT record that proves the hostname is yours, and an A or AAAA record for each address it shows. Cloud checks DNS every five minutes, and the certificate is issued and renewed for you. Keep the hostname on DNS-only routing, not behind a proxy, until it reads HTTPS active.

In the docs: Domains

Databases and application volumes can be, on a schedule that is daily unless you choose otherwise: PostgreSQL, MySQL, MariaDB and MongoDB as dumps, and a volume as an archive of all of it. Redis and the volumes of a compose stack are not backed up. Every backup is kept, apart from the final backups of a service archived for billing, which are deleted after their date, and a database dump can be downloaded. Restoring from the console is not available yet, so today a database is recovered by loading its dump with the engine's own tools.

In the docs: Backups

An operator acts on your workspace only through a support session, which every screen of the console shows while it is open. During it they can see your projects, your services and each service's recent deployments, and deploy, start or stop a service. They cannot see environment variables, compose files or database passwords, cannot open a terminal, change a service's settings or delete anything, and never sign in as you.

In the docs: Getting help