Right now only you can open it, on localhost. Paste one prompt into Claude Code and it comes back with a link you can text to anyone. A database, logins and file storage are there if your app needs them.
No card, no password. We email you a sign-in link.
We sent a sign-in link to .
Open it on the computer your app is on, then copy the prompt for Claude.
No surprise bill. Free accounts have no card on file. If your apps use more than the free $10 in a month, they pause.
Ask Claude how to go live and you get a to-do list of other companies' products. NukeBase replaces the list with one command Claude runs.
You need Claude Code and Node.js. If Claude says npx isn't found, ask it to install Node.js first.
Claude creates the NukeBase project in a new subfolder, so nothing of yours is overwritten.
Put this app online with NukeBase. 1. Run: npx --yes nukebase start my-app A browser window opens. I'll click Confirm. 2. Read my-app/CLAUDE.md. It explains how NukeBase apps work. 3. Copy this app into the my-app folder. Leave my original files as they are. Pages and assets go in public/. If the app is only static files, that's all. If it has a server, saved data or logins, move those to server/app.js, the built-in database and NukeBase sign-in. Don't add anything the app doesn't already have. 4. Inside my-app, run: npx --yes nukebase push --yes 5. Give me the live link and tell me anything that didn't carry over.
Your only step. It signs this computer in to your NukeBase account so Claude can deploy. This sign-in can deploy and manage your projects but can't change billing. It is saved in ~/.nukebase/credentials.json, never in your project, and you can end it under Signed-in devices on your dashboard.
$ npx --yes nukebase start my-app Welcome to NukeBase. Confirm your Claude session: click Confirm in the browser window that opens Signed in as you@example.com ✅ Your app "my-app" is live at https://my-app.usw4.nukebase.com
Claude copies your app into the project, pushes it and gives you the address, along with anything that didn't carry over.
Swap the last line for your own idea. Claude builds for the place the app will run, so there's nothing to move later.
Run: npx --yes nukebase start my-app A browser window opens. I'll click Confirm. Then read CLAUDE.md in the project folder. It explains how NukeBase apps work. Build this, put it live with npx --yes nukebase push --yes, and give me the link: A booking page for my studio. Clients sign in with their email, pick a time, and I see every booking in an admin page.
It signs this computer in to your NukeBase account so Claude can deploy. This sign-in can deploy and manage your projects but can't change billing, and you can end it under Signed-in devices on your dashboard.
Claude builds the app, pushes it and gives you the address. Keep talking to it to change anything.
npx nukebase push --yes and the new version goes online. If you don't like it, "roll that back" undoes the push and keeps your data.
A NukeBase project is a Node.js app with a public/ folder and a built-in database. Not sure what Claude used? Ask it: "What is this app built with?"
public/ as they are. So does the built output of a React or Vite app.server/app.js. The CLAUDE.md in your project tells Claude how.Three things other hosts leave to you.
Every project includes the file Claude Code reads first. It explains the data calls, the rules and the gotchas, so Claude isn't guessing.
The web server, database, sign-in and file store run together, so there is nothing to wire up and no keys to pass between services.
nukebase logs shows the live app's errors, so Claude can read what went wrong and fix it. nukebase rollback undoes a bad push.
All of it comes with the project. Use what your app needs.
server/app.js: routes, scheduled jobs, calls to other services..env and go up with nukebase env push, never with your code.nukebase domain walks through it. SSL is included.Your plan adds credit each month and your apps use it as they run. The smallest app size is $3 a month plus what it uses. Most small apps come to about $4 to $6 a month, so the free $10 covers one or two.
On Free, going over pauses your apps. There is no card on file to charge. They start again with next month's credit, or when you upgrade. On a paid plan, a monthly spending cap sets the most you'll ever pay. App sizes and usage rates
Open Claude Code in your app's folder and ask it to run npx --yes nukebase start my-app. Click Confirm in the browser once. Claude gets a NukeBase project with hosting, a database, sign-in and file storage, moves your app into it and runs nukebase push to put it live on a real web address.
The nukebase command-line tool, published on npm. start signs you in, creates the project and downloads a starter app into a new folder. push uploads that project folder. The --yes flags skip the confirmation questions so Claude isn't left waiting. Leave --yes off push and it lists every file it will upload or remove, then asks first.
No. Claude Code runs them. You paste one prompt and click Confirm in your browser once so the session can deploy to your account. After that, you say "push it live" whenever you want an update online.
No. NukeBase is an independent hosting platform. It works with Claude Code because setup and deploys are plain terminal commands, and every project includes a CLAUDE.md file that explains the system to Claude.
No. Any coding agent that can run a terminal command can run nukebase start and nukebase push, and so can you. Claude Code is the one the project's instructions file is written for.
In a .env file in your project. nukebase env push sends it to the server, where it is kept outside the project folder. It is never uploaded by an ordinary push, so keys stay out of your code.
Run nukebase rollback, or ask Claude to. It undoes the last push and keeps your data. Claude can also run nukebase logs to read the error and fix it.
Yes. The code is in a folder on your computer the whole time, and nukebase pull --data copies the app's data down too. The engine is one file inside your project, so the same app runs on your laptop or your own server with node server/database.js.
The free plan's $10 of monthly credit covers a small app or two. If your apps use more than your credit, they pause until next month's credit arrives or you upgrade from the dashboard. On a paid plan you can top up or turn on auto-refill so apps keep running, and a monthly spending cap sets the most you'll ever pay.
The database runs in memory and is written to disk every few seconds. A normal restart saves everything first. A crash can lose the last few seconds of ordinary writes, so a write marked { durable: true } replies only once it is on disk. Off-site backups run every 4 hours and are kept 30 days.
App sizes run from 128 MB to 1 GB of memory. The database lives in memory, so NukeBase suits apps with up to about 1 GB of data, with large files kept in file storage. Each app is one process in one region. It is not built for video processing or very large datasets.
Free plan. If it isn't for you, your code never left your computer.
Create my free account →