Deploy by conversation.
consostack plugs into your AI coding assistant. Tell it what to put online — a git repo, a plan, maybe a database — and it sets up the hosting, builds your app, and hands back a live URL. No Dockerfiles, no dashboard to learn.
You talk. Your AI ships it. You never touch a server.
Whether it's your first deploy or your hundredth, it's the same single move: tell your assistant what you want live, and it handles the account, the build, and the URL on consostack — no Dockerfile, no pipeline to babysit.
- Ask in plain language — it creates your account and picks a plan
- Your framework is detected from the repo; nothing to configure
- Managed Postgres & Redis, attached with one instruction
- A real URL with HTTPS, ready to share the moment it's up
- Drive it from MCP, the REST API, or a web console
- If a build breaks, you get told in a sentence — not a stack trace
Your assistant does the hosting. You just ask.
Here's the whole idea: consostack is a service your AI assistant can operate on your behalf, over MCP — the open standard that lets AI tools take real actions, not just chat. You connect it once. After that, putting something online is a sentence in the same chat you already code in.
Connect it once
Add one endpoint to any MCP-capable assistant — Claude, Cursor, and others. That's the entire setup, and you never repeat it.
Ask for a deploy
Point it at a public git repo and name a plan: “Deploy this on Pro, with a Postgres.” It shows you the price, creates your account, and takes the key — you fill in nothing.
It goes live
consostack clones the repo, detects the framework, builds it, and serves it behind HTTPS on your own subdomain — usually under a minute.
To start you need an AI assistant that speaks MCP (like Claude or Cursor) and a public git repo — or pick a ready-made template and skip the repo entirely. Once it's live, the same conversation keeps managing it: add a database, read the build logs, roll back, or point a custom domain at it.
Start free. Upgrade when it matters.
- 3 projects
- 256 MB · 0.5 vCPU
- 1 database
- 20 projects
- 1 GB · 1 vCPU
- 5 databases · 10 domains
- 50 projects
- 2 GB · 2 vCPU
- 20 databases · 50 domains
- 200 projects
- 8 GB · 4 vCPU
- 100 databases
Prices are indicative during preview. Prefer clicking to talking? A web console for manual setup is on the way.