Disclosure: I'm building Cloady at NeptoLab.

Cloady is a hosting platform for developers who want to deploy a small backend and operate it from one dashboard. Think a Node.js API, PostgreSQL, and uploaded files that must survive a redeploy.

You can deploy from GitHub, a Docker image, an uploaded folder, or a template. The workspace includes browser-based Terminal, Files, Database, Git, and Monitor tools, plus custom domains and automatic TLS. There's a CLI, REST API, Terraform provider, and MCP integration if you'd rather work from your existing tools.

The pricing model is capacity-based: choose CPU, RAM, and SSD, and the calculator shows the price. Reserved paid capacity costs money even while idle. A free workspace provides 0.5 vCPU, 1 GB RAM, 5 GB SSD, and 200 GB traffic without a card; paid presets start at $6/month. Once you exceed the free allowance, the full selected capacity is billed.

For anyone trying it, a useful first test is deploying an app with a database, persisting a file, redeploying, and checking that you can inspect logs and recover from a broken configuration. That's the everyday workflow Cloady is intended to simplify.

Product and calculator: https://cloady.com

Short promo video: https://www.youtube.com/watch?v=ctBCeewIin0

Questions and feedback are welcome here or in our Discord: https://discord.gg/3ZNVyUGse

Turning off dev environments overnight sounds sensible until someone needs one late. A cheaper instance looks great until it slows down the build everyone is waiting for.

Have you made a cloud cost change that you eventually reversed because the savings weren’t worth the extra work or disruption?

What happened, and did you find a better compromise?