How to Deploy an App with InstaPods

Updated

InstaPods deploys your app to a real server in seconds using one command, and it can also be driven from inside an AI assistant like Claude. The fastest path is the install script: curl -fsSL https://instapods.com/install.sh | sh. If you already work in Claude, Cursor, or another MCP-capable client, you can connect InstaPods once and then just say "deploy this" — the assistant creates the pod, uploads your code, adds a database, and returns a live HTTPS URL. This guide covers both routes, what you get after deploying, and where people typically get stuck.

What you need before you start

  • An app that currently runs on localhost (the source material frames the problem exactly this way: "You built the app. Now it's stuck on localhost.")
  • A terminal, or an AI client that supports MCP connections
  • A card on file if you want the $10 credit — the site states $10 credit when you add a card, described as about 3 months on the Launch plan, cancel anytime
  • A domain only if you want a custom one; HTTPS is automatic either way

Option 1: Deploy from the terminal

  1. Run the install command:
    curl -fsSL https://instapods.com/install.sh | sh
  2. The script sets up the InstaPods tooling on your machine. From there you deploy your app to a pod — a single unit that includes the runtime, database options, domain handling, and SSL.
  3. Expected result: your app is reachable at a live URL over HTTPS, running on a real server rather than localhost.

The pitch behind this route is "one command, real servers" — the goal is to skip stitching together separate hosting, database, CDN, DNS, and environment-variable services.

Option 2: Deploy from your AI assistant

This is the route InstaPods leans into hardest: "Your AI can ship it for you."

Using the Claude connector

InstaPods is a published connector in Claude's connector directory. The flow:

  1. Add the InstaPods connector in Claude.
  2. Ask for a deploy in plain language — the site's example is saying "deploy this."
  3. Claude creates the pod, uploads the code, adds a database, and hands back a live URL.

The stated benefit is no tab switching and no terminal. If you've been in the situation one Reddit user described — "Just accepted Claude Code's all the way to a working app on localhost. Now have to figure out how to deploy it" — this collapses that gap into a single request.

Using ChatGPT, Cursor, Windsurf, or any MCP client

A ChatGPT app is listed as "coming soon" and submitted to OpenAI's app directory, but you don't have to wait. Point any MCP client at:

https://app.instapods.com/api/mcp

The site names Cursor, Claude Code, Lovable, Bolt, ChatGPT, and Windsurf as compatible tools, and says it works with "any tool."

What you get after deploying

Feature What it means
One pod Runtime, database, domain, and SSL in one unit instead of five services
Always On No sleeping or cold starts; runs 24/7 even on the $3 plan
Databases included MySQL, PostgreSQL, Redis — one command to add on Build ($7/mo) and above, no separate database bill
Domains + Auto SSL Point your domain and HTTPS is automatic for every pod and domain
SSH Access Full shell access if you need it

The pricing signal from the site: from $3/mo, with $10 credit when you add a card (about 3 months on Launch). Database add-ons are tied to the Build plan and above.

Common sticking points

  • Assuming the database is always free. The site ties one-command database adds to Build ($7/mo) and above, so check your plan before expecting MySQL, PostgreSQL, or Redis.
  • Waiting for the ChatGPT app. It's submitted but not live; use the MCP endpoint directly instead.
  • Overcomplicating the domain step. You don't configure certificates manually — point the domain and HTTPS is handled.
  • Treating it like a five-service stack. The whole point is consolidation; if you're still wiring up separate DNS and env-var services, you're working against the tool.

Which route to pick

  • Terminal install script — best if you're comfortable in a shell and want the deploy to happen outside any AI client.
  • Claude connector — best if you already build in Claude and want to stay in the chat.
  • MCP endpoint — best if you use Cursor, Windsurf, ChatGPT, or another MCP client and want the same in-chat deploy behavior.

All three end in the same place: a live HTTPS URL on a real server.