Publish your site

Gemmein hosts your app's frontend. Publish from a chat or from a computer, open the finished product on your laptop or phone, sign in and use it. Every publish lands on a private Development site first; the public Live site changes only when you approve a version.

What is hosted

The frontend's static files: HTML, CSS, JavaScript, images and fonts. A path with no file extension and no file of its own serves /index.html, so a single-page app's routes work. A page built in a chat loads the SDK from the site itself: import { gemmein } from "/__gemmein/sdk.js" in a <script type="module">. A build that bundles @gemmein/sdk from npm works as it is.

Server code is not hosted: a Node server, API routes and server-side rendering run in relays or on the app's own server. Gemmein does not build the app; a computer runs the build and npx gemmein publish sends the output.

From a chat

Add the Gemmein connector to ChatGPT or Claude, then ask for the site. The AI opens a draft (site_draft), puts each file (site_put_file, up to 1 MB a call) and publishes (site_publish). A draft carries the files the Development site serves now, so a change sends only the file that changed.

From a computer

npm run build
npx gemmein publish          # dist/, build/ or out/, or the folder you name
npx gemmein site             # both addresses and every version

The CLI scans for a secret key before anything is sent, hashes every file and uploads only the files Gemmein does not hold yet. Dot-files (.env) and links are never sent.

The answer

Every publish answers one of two:

• LIVE: the Development site's address and the version, after Gemmein opened the address and it answered with that version. LIVE means your private Development preview now serves that version: your public Live site doesn't change until you put a version live.
• FAILED: the step (build, upload, size, secret_scan or address_check), the file and line when known, the reason and the fix. Nothing changes at the address. Each code is on Errors.

Iterate in a chat

Ask for a change ("make the save button green"). The AI changes the one file that holds it and publishes only that file. A preview tab you have open reloads itself within seconds, on the same page and scroll. A publish that changes nothing costs nothing.

This works through the Gemmein connector in ChatGPT, and in other AI apps and coding agents, some of which take voice. Each app runs MCP connectors its own way, so the experience varies from app to app.

Who can open the Development site

You, signed in to Gemmein: the first visit on a device signs in at app.gemmein.com, then that device opens the preview for 30 days. Anyone with a share link (npx gemmein site share, site_share_link or the Site room) opens it for 7 days. The preview runs on the app's Development side: the Development public key, Development's caps and Stripe's sandbox. Until the app is live, after 30 days idle it is unpublished; its files are kept, and publishing again restores it.

Putting a version live

Once the app is live, npx gemmein site promote <version> (or site_promote) asks you to approve putting one Development version on the Live site, in your browser with the code Gemmein emails. The same files are copied; nothing new is uploaded.

Versions, rollback and download

Every publish is a version. npx gemmein site rollback <version> serves an earlier one on Development again. npx gemmein site pull downloads any version as a zip (the owner only, each download on Logs). Gemmein keeps the files of the newest 50 versions and of what is served; older versions keep their history row.

Limits

Every text file is scanned for a secret key before it is served. A key belongs in a relay or the app's own server; the page uses its public key.

Start

Which AI do you build with? Claude Code · Cursor · Codex · A browser tool. Or start building.