New Deploy straight from Claude Code

Say “ship it”.
Get a live URL.

makeitlive is a Claude Code plugin. It packages your project, builds it, fixes what breaks, and opens the finished page in a real browser before it tells you it worked.

> /plugin marketplace add makeitlive-app/makeitlive-skills

> /plugin install makeitlive@makeitlive-skills

Then open any project and say “deploy this”. No account needed, and your first app is free.

Not using Claude Code? Deploy from your browser →

claude code · ~/my-app

> ship it

analysing Next.js app with a Postgres database

building Installing dependencies

recovering Build failed, patched it, retrying

deploying Starting it on a real server

verifying Opening the page in a browser

my-app-production.up.railway.app verified live · screenshot attached

You already have an agent that writes your code. Asking it to also put that code online should not mean leaving the chat for a dashboard, a CLI and a wall of build logs.

How it works

Install it once

Two commands in Claude Code adds the plugin. There is nothing else to set up, and no account to create.

Say “ship it”

Or deploy this, put this online, give me a link to share. Claude works out that you mean this and takes it from there.

Get a verified link

A real URL anyone can open, plus a screenshot proving your app actually loaded. Say “ship it” again later and the link stays the same.

Self-healing builds

It does not hand you the error. It fixes it.

Most deploys fail the first time. A missing build script, the wrong Node version, a package that needs a system library. Normally that is where you get a stack trace and a bad afternoon.

makeitlive reads the build and runtime logs, works out the cause, patches it and retries - while the deploy is still running, up to four times. You see one line saying it hit a problem and is fixing it. Usually the next thing you see is the URL.

Building

Dependencies installed, compiling your app.

Build failed

No start command. A normal host stops here and emails you the log.

Recovering

The agent reads the log, writes the missing config and runs the build again.

Verified live

Second attempt succeeded. You never had to read the log.

Proof, not optimism

“Deployed” is not the same as working.

Every other platform tells you it succeeded the moment the build exits zero. Then you open the link and get a blank page or a 500.

makeitlive opens your app in a real browser and screenshots it. If the page does not load, that is a failure and the agent goes back to work. You only ever hear “it worked” when something actually looked at it.

https://my-app-production.up.railway.app

verified live

Why it’s different

You never leave the chat

No dashboard, no CLI, no YAML. The tool you already write code in is the tool that ships it.

Failures get fixed, not forwarded

The agent diagnoses the build itself and retries. If it truly cannot, you get one plain sentence explaining why.

Your link never changes

Redeploy as often as you like on the same URL. And if a redeploy fails, the version people are already using stays up.

Secrets stay out of your history

If your app needs an API key, you get a private page to enter it. It never touches the conversation or your repo.

Priced by what you actually deploy

Not a flat subscription - the agent looks at your project and prices it by complexity. Drag to see how.

API

~$5 Simple site

Just a static site - no backend, no database.

Simple site Web app Full-stack app

Ship your next idea today.