What Is Web Hosting? A Plain-English Guide for First-Time App Builders

You've built an app — maybe with an AI tool, maybe by hand — and it works on your computer. But your computer isn't always on, isn't reachable from the internet, and certainly shouldn't be serving your app to strangers. For other people to use your app, it has to run somewhere else. That somewhere is hosting.

Web hosting means renting space and computing power on a computer (a server) that's always on, always connected, and built for the job.

Why you can't just use your own computer

Technically you can serve an app from your laptop. In practice:

It goes offline whenever you close the lid, restart, or lose Wi-Fi.
Your home internet isn't designed for visitors, and your internet provider may block it.
It exposes your personal machine — with all your files and passwords — to the internet.

Hosting companies run servers in data centres with reliable power, fast connections, and security teams. You rent a slice.

First: what kind of app do you have?

The kind of hosting you need depends on one question: does your app need its own server code?

A static site

Just files — HTML, CSS, JavaScript, images — that are sent to the visitor's browser as they are. Portfolios, landing pages, documentation, simple tools that run entirely in the browser. Some apps built with AI tools are static frontends that talk to a separate backend service like Supabase.

A full app

An app with its own backend: code that runs on the server to log people in, save data to a database, take payments, send emails, or talk to AI models using secret keys. Most real products end up here eventually.

Not sure which you have? Frontend vs Backend: What's the Difference? explains how to tell.

The main kinds of hosting

1. Static hosting

For static sites. You upload files (or connect a GitHub repository) and the host serves them worldwide, usually very fast and often free for small sites. Examples include Netlify, Cloudflare Pages, GitHub Pages, and Vercel.

Good for: landing pages, portfolios, frontend-only apps. Can't do: run your own server code, keep secrets hidden, or host a database.

2. App hosting (platforms, or "PaaS")

For full apps. You connect your code, and the platform builds it, runs it, keeps it running, and gives you a URL with HTTPS. Many offer add-on databases. Examples include Render, Railway, Fly.io, Heroku, and similar.

Good for: most full apps, especially if you don't want to manage servers. Watch for: pricing per service and sometimes per usage, which can add up.

3. A server you manage (VPS)

You rent a virtual computer and install everything yourself: the runtime, the database, the web server, security updates, backups. Examples include DigitalOcean, Hetzner, Linode, and Vultr.

Good for: people who want full control and are comfortable with Linux, or want to learn. Watch for: everything is your responsibility — including security and backups.

We compare the last two in detail in VPS vs PaaS: Where Should a Small App Live?

4. Built-in hosting from your AI tool

Lovable, Bolt, v0, Replit, and others have a "Publish" or "Deploy" button that hosts your app for you. It's the fastest path, and fine for many projects — with some limits on control and some lock-in. We have guides for Lovable, Bolt, v0, and Replit.

5. Managed development platforms

A newer option: the app, its database, and the environment it's built in all live together, managed for you — so you (or an AI agent) can keep improving the live app without handling servers. We explain the idea in What Is an Autonomous Development Platform?

What good hosting should include

Whatever you choose, check for:

HTTPS (the padlock) — should be automatic and free.
Your own domain — the ability to connect yourapp.com. (New to domains? What Is a Domain Name?)
Environment variables — a safe place to put secret keys, outside your code.
A database, with backups — if your app stores data. Ask how often backups happen and how you'd restore one.
Logs — so you can see what went wrong when something breaks.
Predictable pricing — know what happens to your bill if traffic spikes.

How much does it cost?

Rough shape, not exact prices:

Static sites: often free at small scale.
Small full app: typically somewhere between a few dollars and a few tens of dollars a month, plus the database.
Domain name: a separate yearly fee, usually modest.

Costs grow with traffic, storage, and add-ons. For small apps, the bigger cost is often your time if you choose to manage everything yourself.

The short version

Static site? Use static hosting.
Full app and don't want to manage servers? Use an app platform or a managed platform.
Want full control and don't mind the work? Rent a server.
Just validating an idea? Your AI tool's publish button is fine for now.

EasySpawn hosts the whole app — server code, managed Postgres with daily backups, automatic HTTPS, and your own domain — on flat monthly pricing, with Claude Code working on the live app. See how it works for AI-built apps or join the waitlist.