How to deploy an AI-generated app when you've never touched a terminal

Your AI tool built an app that runs on its preview screen. Now you want it live on the internet at your own address, and every tutorial jumps straight to commands you’ve never seen. You’ve never opened a terminal. You’re not even sure what “deploy” means. Let’s fix that.

Why this feels harder than it should

The preview inside a tool like Lovable or Bolt is a rented room. It’s convenient, but it’s their room, with their rules, their limits, and their bill. “Deploying” just means moving your app out of that rented room and onto a place you control, so you get your own web address, your own database, and no surprise shutoff.

The reason it feels hard is vocabulary, not difficulty. Terminal, SSH, deploy, build: these are four words for fairly simple things. Once you have the words, the steps are short.

Quick glossary before we start:

• Terminal: a text window where you type commands instead of clicking buttons.
• Build: turning your source code into the finished files a browser can run.
• Deploy: copying those finished files to a server that’s online 24/7.
• Server: a computer that stays on and serves your app to visitors.

How to fix it

We’ll use the simplest real path: export your code, then push it to a host that builds and deploys it for you. You’ll type a few commands, but not many.

Step 1: get your code out of the AI tool

Most AI builders have an “Export” or “Connect to GitHub” button. GitHub is a free website that stores code. Click connect, sign up for GitHub if you don’t have an account, and let the tool push your project there. Now your code lives somewhere you own.

Step 2: install the terminal basics

You need two free tools: git (moves code around) and node (runs JavaScript apps). On a Mac, open the app called Terminal and paste this to check what you already have:

git --version
node --version

If either says “command not found,” install them. The easiest way on a Mac is Homebrew:

# install Homebrew (a tool that installs other tools)
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

# then install git and node
brew install git node

On Windows, download the installers from git-scm.com and nodejs.org, click through them, then reopen your terminal.

Step 3: get the code onto your computer

“Clone” means download a copy of your GitHub project. Copy the green “Code” button’s HTTPS link from your GitHub page, then:

git clone https://github.com/yourname/your-app.git
cd your-app

cd means “change directory,” so now your terminal is sitting inside the project folder.

Step 4: run it locally first

Before going live, prove it runs on your own machine. Almost every AI-built app uses these two commands:

npm install    # download the pieces your app depends on
npm run dev    # start the app on your computer

The second command prints a local address like http://localhost:3000. Open that in your browser. If your app shows up, you’re ready to go live.

Step 5: deploy to a host

For a first deploy, pick a host that builds from GitHub automatically. You connect your GitHub account, pick the repo, and it does the build and deploy for you. Every push to GitHub triggers a fresh deploy.

If your app needs a database and background work, the platform will ask for environment variables, the secret values from Step 2 of our security checklist. Paste them into the host’s settings panel, never into the code.

To push a change and trigger a deploy later, the loop is always the same three commands:

git add .
git commit -m "describe what you changed"
git push

add stages your changes, commit saves them with a note, push sends them to GitHub, which tells your host to redeploy. That’s the whole cycle.

Step 6: point your domain at it

Buy a domain from any registrar, then in your host’s dashboard add the domain and follow their DNS instructions (usually copying two records into your registrar). SSL, the padlock that makes it https://, turns on automatically on most hosts. Give it up to an hour to take effect.

Or, we do it for you

If the terminal steps still feel like a foreign language, that’s exactly the gap we fill. We take your GitHub repo and stand up a real deploy with a database, backups, and monitoring, then hand you the keys. Book a free audit and we’ll walk your app through it.

FAQ

Do I have to use the terminal at all?

For a basic static app, some hosts let you deploy entirely by clicking through GitHub, no terminal needed. The moment your app has a database or a build step that misbehaves, the terminal is how you see what’s actually happening. Learning the six commands above is worth an afternoon.

What if npm install throws a wall of red errors?

Read the first error, not the last. Most first-deploy failures are a missing environment variable or a Node version mismatch. Search the exact first line of the error, and check that your Node version matches what the AI tool used. If you’re stuck, that’s a normal place to ask for help.

Is it safe to put my code on GitHub?

Yes, as long as no secrets are in the code itself. Make the repo private if you want, but the real rule is that API keys and passwords live in environment variables, never in files you push. Run the grep from our security checklist before your first push.

How much does hosting cost for a small app?

A small app with light traffic runs from free to about 20 euros a month on most hosts, plus roughly 10 to 15 euros a year for a domain. Costs climb when you add a real database and steady traffic, which is the point where a managed setup starts to pay for itself.