Deploying
When your project is ready, publish it to the edge in one click — or export the code and run it yourself.
One-click deploy
From File → Deploy (or the Deploy button), pick a host:
- Cloudflare — our recommended target.
- Vercel
- Netlify
- Harper — for a project that needs its own database, real-time collaboration, or file uploads running on a cluster you control (see Deploying to Harper below).
You'll get a live URL in seconds, styled exactly as you designed it. Re-deploying updates the same site.
Connect a host
The first time, connect the host with an API token — stored encrypted, never shown again. After that, deploying is one click.
Harper is the exception: instead of a token, you give it your cluster's URL plus a username and password. See below.
Deploying to Harper
Harper (harper.fast) is the only host besides Cloudflare with full backend support — your project's data operations, real-time/live updates, and file uploads all run ON the cluster, not just the static front-end. Pick Harper when your app needs those and you'd rather run them on your own infrastructure (or a Harper Fabric cluster) than Cloudflare's.
- Have a cluster ready — either a Harper Fabric cluster, or a self-hosted Harper instance reachable from the internet.
- From File → Deploy, choose Harper and click Connect token.
- Enter the cluster's URL (e.g.
https://<cluster>.<org>.harperfabric.com), plus a username and password for that cluster. - Click Deploy. Your app appears at
<cluster-url>/<project-name>/.
Likeable uses your credentials once, at connect time, to create a separate, minimal-privilege user just for this app — your own username and password are never baked into the deployed site. Re-deploying replaces the same app in place; it doesn't create a new one.
If your app has its own database connections or secrets, Harper loads them for the whole cluster, not just this app. Use a cluster dedicated to this project rather than one shared with other deployed apps.
What ships
A fast static site plus an interactive runtime, with only the bricks your project uses, so pages stay light. Data behaves per the runtime: public URLs fetch live; authed sources use a server function or a baked snapshot.
After deploying
- Put it on your own domain.
- Push live updates without a full redeploy.
- Or export the code and host it yourself.
Deploys count toward your plan's monthly limit — see Plans & pricing.