ExportYourSite
PricingSupported Sites
Export now

BlogHow to

How to self-host a no-code portfolio for a few dollars a month

Export a portfolio from Framer, Webflow, or any other no-code builder, make it deployable with an AI agent and Docker, then host it cheaply.

Published 2026-09-23Updated 2026-09-295 min read

Hosting your portfolio on Framer or Webflow can easily cost around $120 a year, even when you barely change anything. Here is how to move it off the builder, host it for as little as $1 a month, and own the files yourself.

TL;DR

  1. Export the published portfolio.
  2. Make the ZIP deployable with an agent.
  3. Host it.
  4. Edit by prompting.

Step 1. Export the published portfolio

Most no-code builders will not hand you a clean self-host package. You need a copy of the live published pages as files.

  1. Open the live portfolio and note the pages you need. Write down the homepage, case studies, about, and contact.
  2. Make a copy of those published pages as files. Export Your Site is one way to create that copy.
  3. Open the copy on your computer and click through it. Check the homepage, a few case studies, photos, and the menu.

There are many website downloaders if you prefer a desktop or command-line tool.

Step 2. Make the ZIP deployable with an agent

Put the ZIP in Git, add a tiny static server, and ship it with Docker so later edits are normal commits.

Prompt:

Take this website ZIP, extract it into a repo, and make it deployable with Docker using a minimal Node static server. Preserve the exported site and its asset paths, support page routes, and listen on port 3000.

Have the agent push the repo to GitHub. Confirm it serves on port 3000 and pages load.

Step 3. Host it

A cheap Hetzner VPS works well for static portfolios. Servers start around $6 a month and can hold many sites, so the cost per portfolio is often a few dollars a month. Coolify is a free open-source panel that simplifies deploys: install it, connect GitHub, deploy to a temporary hostname, click through, then change DNS last. Keep the builder site live until the new host looks right.

Managed options also work: Netlify, Vercel, Cloudflare Pages, GitHub Pages, or a DigitalOcean droplet.

If the agent can use the computer, create the account, sign in once, and let it handle the boring setup clicks.

Put Cloudflare in front when possible for TLS, caching, and basic bot noise.

Step 4. Edit by prompting

For a new case study, give the agent the copy and assets, review the diff, and push to GitHub. If Coolify or the host watches the branch, it deploys on its own.

The first pass usually takes an evening. After that the files are yours, the bill stays small, and updates are a prompt plus a push.

A published-page copy can start from the homepage.