Cloud onboarding
Create a Cloud account, connect your first server, and deploy.
Purpose — Get from a new Notploy Cloud account to a running deployment, with your workloads on your own servers.
Scope
This page applies to Notploy Cloud. On Self-Hosted, you install the control plane yourself — see Get started.
1. Create an account
Register at app.notploy.com. The account provisions a managed control plane for you — dashboard, database and orchestration — so there is nothing to install.
2. Connect a server
Cloud deploys to your servers, so it needs at least one:
- Add a server by providing SSH connection details (host, port, user and SSH key).
- Cloud connects and prepares the server — Docker, Traefik and a lightweight monitoring agent.
- Confirm the server shows as reachable.
The server can be from any provider (AWS, GCP, Azure, DigitalOcean, Hetzner…) and must be reachable over SSH.
Your code and data stay on your servers. Cloud manages orchestration, not your workloads' data.
3. Deploy
From here the workflow matches Self-Hosted: connect a source, create a project and an application, then add a domain.
4. Understand what is managed
| Component | Managed by |
|---|---|
| Control plane (dashboard, database, orchestration) | Notploy — updates and uptime handled for you. |
| Your workloads, data, Traefik on your servers | You. |
If the Cloud control plane is briefly unavailable, your applications keep running — Traefik serves them independently. Only management is interrupted. See Architecture.