Cloady Docs

App and database hosting on Cloady

Choose a deployment source, size your app and database, understand resource pricing, and plan a migration to Cloady.

Cloady is a platform-as-a-service operated by NeptoLab. It runs your applications, databases and persistent storage on managed infrastructure. You choose the resources your apps need and manage deployments, logs, terminals and domains in one workspace. Cloady is currently in public beta.

Choose a deployment source

What you haveWhere to startWhat to check
A GitHub repositoryPaste the repository URL in Deploy. Cloady builds it using Railpack or your Dockerfile.Build and start commands, the listening port, and required environment variables.
A Docker imageUse the image as a service in your application.Image access, ports, variables, and persistent volume paths.
A local projectUpload a folder or zip in Deploy.Include the files needed to build and run it; configure secrets as variables.
An app or database from the catalogPick a template.Services, resource requirements, volumes and published endpoints.

A multi-service application can keep a website and its database together, such as WordPress and MariaDB. A database can also run as a separate application. See services and endpoints before deciding which ports should be public.

Understand free and paid capacity

The free allowance per workspace is 0.5 vCPU, 1 GB of RAM and 5 GB of SSD. The free tier includes 200 GB of traffic and does not require a payment card to start.

All applications in a workspace count toward its resource total. The free allowance is a threshold: if any resource exceeds it, the full total becomes billable. It is not subtracted from paid capacity.

The calculator uses these paid resource presets:

PlanvCPURAMSSDPrice / month
Small1 vCPU2 GB50 GB$6.00
Medium4 vCPU8 GB200 GB$20.00
Large10 vCPU44 GB600 GB$65.00
Max16 vCPU92 GB1 TB$120.00

The presets are reference points, not mandatory bundles. Cloady prices the workspace's declared CPU, RAM and SSD between them. Paid capacity includes unlimited network traffic. Optional managed backups add 20% to the resource price of the apps with backups enabled.

For an app with a database, account for both services' memory and CPU, plus the persistent disk. An idle database still reserves resources. Use the pricing calculator for your resource total, and the billing rules for upgrade and renewal behavior.

Domains and persistent data

Web apps receive a cloady.io hostname and automatic HTTPS. You can attach a custom domain and point its DNS at the deployed app. Store data that must survive deployments in persistent volumes and decide whether to enable managed backups.

Choose the region when deploying. Moving an app with volumes can involve downtime while its data copies. Separate deployments in different regions are separate apps; Cloady does not automatically fail an app over between regions.

Moving an existing application

Cloady can import supported configuration from Railway, Render and Vercel. The importer prepares a deployment for review; it does not migrate database contents, uploaded files or volume data.

  1. Import the service and review its repository, variables, resources and ports.
  2. Re-enter secrets that the source provider could not return.
  3. Deploy and migrate persistent data separately using the relevant database or file tools.
  4. Test the new application before changing the production domain's DNS.

Vercel imports run as long-lived servers. Applications relying on serverless or edge features may need changes. The import guide describes the supported configuration and limitations for each provider.

Automating deployment

Use the CLI for terminal workflows, the REST API for integrations, or the Terraform provider for infrastructure as code. The MCP server makes platform tools available to compatible AI clients using an authenticated Cloady API token.

Ready to try it? Follow Getting Started, browse templates, or contact Cloady about your requirements.

On this page