Deployment

These are two different things and confusing them is the most common publishing mistake. Preview is the build you see inside the editor, rebuilt every time you prompt — it is for review and UAT. Production is the site your users visit, and it changes only when you publish a specific version.

So a change appearing in preview does not mean it is live, and a bug you just fixed in preview is still live in production until you publish again.

1. Select the exact version to ship.
2. Rebuild if preview looks stale.
3. Apply pending SQL for Supabase-backed apps.
4. Publish server features and secrets if edge functions changed.
5. Smoke-test production in an incognito browser.

Paid plans can attach a customer hostname to Techbilla hosting. Open Tools → Custom domain. Add the hostname, create a CNAME at your DNS host, then Check DNS and Connect to issue HTTPS. The live site serves the same files as Tools → Publish.

Example records (replace the value with the target shown in Tools → Custom domain):

• Cloudflare: same CNAME, Proxy = DNS only (grey cloud).
• GoDaddy: Type CNAME, Name www, Value the preview host, TTL 1 Hour. Forward acme.com → https://www.acme.com (no CNAME on @).

NeoBuild finds the Supabase edge functions in the generated files and publishes the ones that changed before preview or publish, so the frontend is never calling server logic older than itself. Each publish is recorded in Build History.

The step that catches people out is order: publishing the frontend does not publish the functions it depends on if you skipped that step. If a published app returns 404 from a function that works in preview, republish server features from the version you actually published — see Troubleshooting.