# Put a template live yourself

> The order of operations, the hosts that will take a Next.js export, and the four jobs that become yours the moment you host it yourself.

Templates you buy · noboringsites documentation · https://noboringsites.com/docs/templates/put-a-template-live-yourself/

---

Without a plan, hosting is yours to arrange. What you get is a standard Next.js project that runs anywhere serving static files.

## The order of operations

Five steps, and only the last one is public.

1. Unzip the download and open the project folder.
2. Install its dependencies with Node.
3. Replace the demo content, then run it locally and click through every page.
4. Build it, and upload the built output to your host.
5. Point your domain at that host.

## Where it will run

Anywhere that serves static files.

- **Cloudflare Pages**, which is what we use ourselves.
- **Netlify or Vercel**, both of which take a Next.js project directly.
- **Any static host at all**, including one you already pay for.
- **Your own server**, if that is what your business runs.

## Nothing is locked to us

The files do not phone home.

- **No licence key** has to be checked at runtime.
- **No account with us** is needed to serve the site.
- **No plugin marketplace**, so nothing has to be kept updated on our schedule.

## What stays yours to do

Self-hosting means these are yours.

- **SSL** - most hosts issue and renew a certificate for you, but it is your host's job, not ours.
- **Updates** - security patches on your dependencies are yours.
- **Backups** - whatever your host offers, plus your own copy of the files.
- **Uptime** - your host's, and their status page is the one to watch.

## If you would rather not

There is a supported way out of all of that.

- **Start a plan** and we host the site, renew the SSL and answer when it breaks.
- **Buying a template does not commit you** either way, in either direction.