Why I built Clever Deploy

Source: Dev.to

Why I built Clever Deploy

I built Clever Deploy because every time I wanted to ship a small side project, the deploy story turned into a project of its own.

• Surprise bills – I’d push a side project to a “free tier” and end up with unexpected charges.
• Complexity – I’ve set up Jenkins in Kubernetes for clients; you don’t want that level of complexity for a simple project.

What I wanted was simplicity and no unexpected bills.

Core principles

1. One‑click deploy – Click Deploy, pick a repo, get a live HTTPS URL. The defaults work for 95 % of projects; you can override them later if you’re in the remaining 5 %.
2. Predictable pricing – A flat rate shown before you click. No metered surprises hidden behind “fair use” footnotes. If a project will cost money, you know exactly how much before it runs.

Pricing

• A single, flat number that you see up front.
• No hidden fees or usage‑based charges.

If a project is going to cost you money, you’ll know the exact amount before it’s running.

Features

• End‑to‑end live workflow: GitHub authentication, build pipeline, live deploys, build logs, and an admin dashboard.
• Defaults that work for most projects, with the ability to customize when needed.

Availability

Clever Deploy is not open to the public yet. I’m inviting people from a waitlist as I work out edge cases.

If predictable costs and one‑click deploys sound like your kind of solution, check out https://cleverdeploy.com/ – I’ll make sure you get 50 % off your first year if you decide to use us for real.

— Wasim