Deploy your code

Build and deploy on AppJet

Ask the agent to build and deploy your app, or use the deployment control in the workspace. AppJet builds the project and deploys the resulting image. A build can succeed while deployment fails, so check the deployment result and open the running app before treating the release as complete.

Use Preview or Settings → Overview to find the current deployment URL. If the app fails to load, check runtime logs as well as build logs.

Dev and Edge endpoints

Dev endpoints are created for branches connected to AppJet. They are intended for development and preview rather than production caching.

The appjet branch also has a Cloudflare edge endpoint. Custom domains use this branch and are available on Starter and Pro. Use the URL shown for the app; different apps can run on different datacenters and domain names.

Deployment persistence

Successfully deployed apps have no seven-day expiry, including on Free. The same persistence policy applies to all plans.

An automatically created placeholder URL that has never received a real deployment can be cleaned up after 24 hours. This removes the unused placeholder, not the GitHub repository or saved workspace. An explicit new build can provision a new URL. Cleanup is gradual, so an eligible unused URL may remain longer than 24 hours.

Configure and verify

Check that your application listens on the configured port and the correct network interface. Store secrets in environment variables. Container-local files are not a substitute for persistent storage; use Supabase or a virtual disk when data must survive replacement of the running container.

See configuration, Supabase, and troubleshooting.