Other hosts

A Jx site doesn't need a special host. The build turns your project into an ordinary folder of web files, so any host that can run one build command and serve a folder can serve your site — and a host that also runs a small server can carry a site with a database or sign-ins. Studio's built-in flow covers Cloudflare Pages ; for everything else, the recipe below is the whole story.

The recipe

1. Pick the deployment adapter. In Settings > General , set Platform Adapter for your target. Static is the choice for a site made only of pages and content — it works on any host that serves files. If the project has a database, sign-ins, or timing: "server" functions, pick Node , Bun , Cloudflare Workers , or Cloudflare Pages instead: those also package the worker that serves your /_jx/* routes. A database or sign-ins make that mandatory — the build stops with an error on Static . Server functions don't stop the build, but on Static nothing ends up serving them, so they need an adapter just the same. See Project settings .

2. Put the project on GitHub (or another repository host) so your host can see it — GitHub does this from inside Studio.

3. Tell the host two things : the build command is bunx jx build , and the folder to publish is dist .

That's it. From then on, every Commit and sync in Source control pushes your changes, the host runs the build, and the fresh site goes live — the flow described in Publish .

Netlify

Create a new site in Netlify and connect it to your repository. In the build settings, set:

• Build command : bunx jx build

• Publish directory : dist

Netlify then builds and publishes on every push, with a free site address until you attach your own domain.

GitHub Pages

GitHub Pages serves files but doesn't take a build command directly — the build runs in a GitHub Actions workflow instead. In your repository, set Pages to deploy from GitHub Actions, and add a workflow that runs bunx jx build on every push and publishes the dist folder with GitHub's Pages deploy action. GitHub's own Pages documentation covers the workflow setup; the only Jx-specific parts are the command and the folder.

Anywhere else

The same two values — build with bunx jx build , serve dist — fit Vercel, Render, a plain web server, or your own CI. If a host can't run the build, you can even run bunx jx build yourself and upload the dist folder by hand: for a site of pages and content, that folder is the site. A project with a database, sign-ins, or server functions has one of the server-capable adapters set, so its dist/ carries a worker beside the pages — and that needs a host which actually runs it.

Next

• Publish to Cloudflare Pages — the host with a built-in Studio flow

• GitHub — get the project into a repository first