How do I get my Claude Code app off my laptop?
To get a Claude Code app off your laptop you need five things that do not exist yet: a copy of the code in a repository, a host that runs it, a database that lives somewhere other than a file on your machine, the secrets (API keys and passwords) placed where the host can read them, and a domain name pointed at the host. Claude Code can write the configuration for all five and walk you through each one. It cannot create the accounts, and each account should be yours.
"Localhost" is the version that runs only on your computer. Everything worked there because the files, the database and the keys were all in one place. Deploying is mostly splitting those apart and giving each a home.
Below is the order to do it in, what each piece is for, and the three things most deploy guides leave out, which decide whether the app stays up once people use it.
In founders’ words
“The part thats tripping me up is deployment because the advice starts sounding simple and then suddenly I'm creating accounts in three places, connecting GitHub, figuring out where the database lives, dealing with environment variables and trying to understand which service is responsible for what.”
“I'd like the rest to be easy to running the project, setting up a database, deploying it and keeping it online without needing much server knowledge.”
“I had zero safety nets in place. I had no alerts to wake me up. Worse, I had no fallback.”
The five pieces, in the order to set them up
- A repository on GitHub. A saved, versioned copy of the code outside your laptop. Hosts deploy from it, and every later change is a commit you can roll back. Ask Claude Code to create it and to check for keys in the files first.
- A database provider. If Claude Code used SQLite, your data is a file on your laptop, and it will not survive a host that restarts. Move to a managed Postgres (Supabase and Neon are common examples) and have Claude Code write the migration, the script that creates the tables there.
- A host that deploys from GitHub. A front end alone fits a static host such as Vercel or Netlify. A backend with a database fits Railway, Render or Fly. One host for every project, so you learn one.
- Secrets in the host's environment settings, never in the repository. Ask Claude Code for a .env.example file listing every setting with the values blank; that is your checklist.
- A domain, pointed at the host. Hosts handle the HTTPS certificate. Email from your app needs its own setup.
What Claude Code can do, and what you have to do yourself
Claude Code writes files. It can produce the deploy configuration, the database migration, a health-check page the host can watch, a .env.example, and a short DEPLOY.md that records every step in plain words so you can repeat it. Ask for all of these by name.
You create the accounts, paste the keys, press deploy, and point the domain. Those steps are yours because the accounts should be in your name and on your card. Services exist that deploy from inside Claude Code in one command. They are fine for showing someone a demo. Before customers use one, read who owns the hosting account, where the database lives, and how you would leave.
The three things deploy guides leave out
- Backups, and one restore. Turn on the database provider's automatic backups, then restore one into a separate database once, so you know the backup works before you need it. An untested backup is a guess.
- Alerts. An error-tracking service that emails or messages you when the live app throws errors, and a check that pings the health page every few minutes. Without these, the first person to notice an outage is a customer.
- A staging copy with its own database. Claude Code works there. The live app only changes after staging works. Never run the agent against the live database; a migration it writes to "tidy up" is a migration on your customers' data.
Add a spending cap or billing alert on every service while you are there. A bug in a loop, or a bot, can run up a bill overnight.
Mistakes that show up in the first week
- A .env file committed to the repository, with real keys in it. Ask Claude Code to search the whole history, not only the current files, and rotate anything it finds.
- Addresses hard-coded to localhost: the front end calling http://localhost:3000 for its backend, which works on your laptop and nowhere else.
- Migrations never run on the server, so the database has no tables and every page errors.
- Uploaded files saved to the host's disk, which many hosts wipe on each deploy. Files belong in object storage.
- No rule for which environment the agent edits. Put it in the rules file Claude Code reads each session: staging only, and never the live database.
Do you need help with this?
For a small app with no customers, no. Claude Code and the steps above will get it online in an afternoon, and the five accounts are yours from the start. Do it yourself; you will understand your own product better for it.
The part that needs experience is not the deploy. It is what happens after: the backup that was never restored, the error nobody saw, the agent that ran a migration on live data. If people will pay for the app, or it holds data about other people, that is where a second pair of eyes earns its place. We start with a free call and will say if you do not need us.
| Piece | Claude Code can | You have to |
|---|---|---|
| Repository | Create it, write the .gitignore, check for committed keys | Make the GitHub account and keep it in your name |
| Database | Write the migration and the connection code | Create the provider account, copy the connection string into the host, turn on backups |
| Host | Write the build and start configuration and a health-check page | Create the account, connect GitHub, press deploy |
| Secrets | Produce .env.example and remove keys from the code | Paste each real value into the host's environment settings |
| Domain | Tell you which records to set | Buy it and set the records at your registrar |
| Backups, alerts, staging | Write the scripts and config for each | Turn them on, restore one backup, and receive the alerts |
Questions
Can Claude Code deploy the app for me?
It can write every configuration file and run the deploy command once the accounts exist. It cannot sign up for a host, enter a card, or set DNS. Services that deploy from inside Claude Code in one step exist; check who owns the account before customers depend on it.
Which host should I use?
It depends on whether the app is only a front end or has a backend and database, and the choice matters less than using the same one for every project. Pick a host that deploys from GitHub, has a fixed low tier, and gives you environment settings, logs and a rollback button.
What about the database I was using locally?
If it is SQLite, it is a file on your laptop and needs to become a managed Postgres before anyone else uses the app. If it is already Postgres running locally, export it, create the same tables on the provider with the migration, and import. Test the login flow against the new database before you point the domain.
Is my app safe to put online?
Three quick checks before you do: no keys in the repository, every page that shows a user's data checks who is logged in, and a second test account cannot see the first account's records. Our page on whether a vibe-coded app is secure goes through the rest.
What will it cost to run?
For a small app, the fixed tiers of a host and a database provider, plus whatever AI or email services the app calls. The variable part is the AI calls, which scale with use. Set a billing alert on each service on day one.
First look, $750. After a free call, we read your whole product and tell you what is finished, what is not, and what to do first.
Setup, $3,000 fixed. We make it ready for real customers, in accounts you own.
Partner, $2,500 a month. We review what your coding agent writes and keep the checks and tests current. Month to month.