Get started
Cahaves Cloud
Run applications and databases on servers you never provision or maintain, charged by the hour.
Updated
Cahaves Cloud runs your applications and databases on servers you never provision or maintain. You give it a GitHub repository, a public Docker image or a compose file. Cloud builds what comes from a repository, runs each service at the size you choose, and bills the hours it runs once a month. An application gets an HTTPS address on the platform's domain after it deploys, and you can point a domain you own at it.
Everything happens in the console at https://cloud.cahaves.com. Cloud's API answers on the same host under /api.
What you can run
An application from GitHub
Cloud builds the branch you choose, and can deploy again on every push to it.
A Docker image
Run a public image by tag or by digest. Nothing is built.
A compose stack
Paste a compose file and run its containers together, charged at the dedicated rate.
A database
PostgreSQL, MySQL, MariaDB, MongoDB or Redis, at the version you pick.
An application from the catalogue
n8n, Hermes Agent or OpenClaw, created with its storage and secrets in place.
/
How the pieces fit
An organization holds your projects and has its own bill, so one sign-in can keep several companies apart. A project holds the services that make up one product: its web application, its worker, its database. Each of those is a service. Releasing a service is a deployment, and each service numbers its deployments and keeps their logs. How Cloud is organised explains each part and what belongs to which.
Creating a service never deploys it. You read what was made, change what needs changing, and press Deploy when you are ready, so a wrong port or a missing variable is fixed before anything runs.
Two things are not given automatically. An image is run as it is, with no build step. A compose stack gets no generated address: it is reachable once you add a domain to one of its services.
Before you start
Sign in with GitHub or Google. Those are the only two buttons on Cloud's sign-in screen, and the first press creates your account. The console then asks you to name your first organization. Sign in and your Cahaves account covers the rest, and Organizations what an organization holds.
Cloud prepares each organization's workspace once the organization is created. The console says so while it is being prepared, and shows New project once it is ready.
Running services are charged by the hour, an application at the rate of its size and a database by the data it holds, and your first nano service runs free. Each organization's month is charged on the 1st, to its card or by invoice. Billing explains the free allowance, the monthly limit and paying.
To deploy from GitHub, connect an account under Settings, Git providers, which installs the Cahaves GitHub App on the repositories you choose. Deploy from GitHub walks through it.
Start here
Tutorials
Next.js and PostgreSQL from GitHub
A repository, a database beside it and a domain of your own.
A static site
Build a site from a repository and serve its output directory.
Run n8n
Workflow automation from the catalogue, with its data kept on a volume.
Connect with SSH
Add a key and open a shell in a running service from your own terminal.
Back up a database
Schedule dumps, take one now and download it.
Add a card and read your bill
Add a card, follow the month and read its statement.
When something goes wrong
Every failure in the console comes with one sentence saying what happened. The troubleshooting pages are organised by that sentence: start with a deployment failed, Deploy is greyed out or refused or sign-in problems. For anything else, Support says how to reach Cahaves.