Deploy & Publish

Deploy & Publish

One-click publish

Click Publish in the header to build and deploy your project live. Deployments use a blue-green strategy — your existing live site stays up during the build and switches over only when the new version is ready. Zero downtime.

  • Static HTML sites publish instantly — no build step needed
  • React/Vite/Next.js sites are built automatically before publishing
  • The published site is independent of your dev preview — changes only go live when you click Publish
  • Multi-page routing works correctly — /about, /admin-dashboard etc. all load the right page

After publishing, use the Links button (green ExternalLink icon) in the header to open your Live Site or Dev Preview in a new tab.

GitHub auto-deploy

Connect a GitHub repository to enable auto-deploy. Every push to your repo triggers an automatic build and publish — usually completing in under 2 minutes. Use the Clone option when creating a project, or connect via Domain Settings → GitHub token.

NoteGitHub auto-deploy requires a valid GitHub Personal Access Token with repo read access. Add it in the project's Domain Settings modal.

Performance & limits

AI Codes It is designed for startups, MVPs, side projects, and production apps with moderate traffic. Here's what to expect honestly:

  • Static sites — served directly by nginx with no cold starts. Handles thousands of concurrent visitors without issue
  • React/Vite/Next.js apps — same as static after build. The built assets are served from nginx, not Node.js
  • Edge functions — run as persistent Node.js processes (no cold starts). Response time depends on what the function does — simple DB queries typically respond in under 50ms
  • Database — shared PostgreSQL instance, one schema per project. Fine for most apps; not suitable for high-write workloads (>1000 writes/sec)
  • Dev preview — your dev server is a real running process (e.g. npm run dev). It stays warm as long as your project is active

If your project gets real traffic and you start hitting limits, the platform won't throttle you silently — contact support to discuss options. For very high-traffic sites (>50k monthly visitors), a dedicated VPS or migration to a managed cloud provider may be the right call, and your code will move cleanly.

NoteThere are no artificial request rate limits on published sites. Limits come from the underlying server resources (1 vCPU, ~3.8 GB RAM). The AI and IDE endpoints are rate-limited per plan to ensure fair usage across users.

Long-term reliability

Your projects and published websites are built to stay up — indefinitely. This is not a sandbox or a trial environment. When you publish a site here, it is meant to run for years.

  • Your code is always yours — every project is a real Git repository stored in Gitea. You can clone it, download it as a zip, or push it to GitHub at any time. No proprietary format
  • Your database is exportable — use the SQL console to run pg_dump or export tables as CSV at any time. Your data is never locked inside the platform
  • Published sites stay live — live sites run independently from the IDE. Even if you stop using the builder, your published site keeps running
  • No surprise shutdowns — we do not delete inactive projects or unpublish sites without notice. If anything changes, you will be contacted well in advance
  • Standard stack — your apps are plain HTML/CSS/JS, React, or Node.js. They run on nginx and standard Node processes — nothing exotic. Any developer can pick up and continue your project
NoteIf you ever want to move off the platform entirely, your full project is one git clone away. Pair it with a PostgreSQL export and you have everything needed to host anywhere.