Docs / deploy

Publish & deploy

Publishing builds your project and serves it from a production URL — https://<slug>.poleved.app. Every project gets one, and you can publish as often as you like.

Publishing your project

  1. Click Publish in the project header. The Deploy dialog opens.
  2. Add or edit environment variables if your app needs them.
  3. Click Publish in the panel.

The status badge moves Pending → Building… → Deploying… → Live. Once it reads Live, the URL appears at the top of the panel with a copy button beside it.

The new version is built and started before any traffic moves onto it, so people using the current version are not dropped mid-deploy. If the new version fails its health check, the deploy is abandoned and the version already live keeps serving.

The first build of a project is a cold one and usually takes several minutes; later builds are much faster because dependencies are already cached. A build still running after 10 minutes is stopped and marked Failed — that is a ceiling, not a target.

Environment variables

The Deploy dialog includes an Env variables editor. Values are encrypted at rest and never shown back to you — saved values render as dots.

  • Saving applies to your next deploy, not the one already running. Publish again to pick up a change.
  • The editor is a bulk replace: anything you remove from the list is deleted when you click Save.
  • Up to 50 variables per project, and up to 4 KB per value.
  • Names take uppercase letters, digits and underscores, and must start with a letter.

Your preview and a default deploy use the same project database. To keep production on separate data, point DATABASE_URL (or MYSQL_URL) at your own database here.

Deployment history

History lists your recent deployments: the status, the short commit each was built from, and how long ago it ran.

Every row has a log button. Build log shows the build output for that deployment. Runtime log shows what your app is printing right now, and is only available on the deployment currently live.

A Failed row also offers Resolve with AI. It shows you the error and log tail first, then sends them to the AI as a normal prompt — so it costs a run, like any other prompt.

Rolling back

Rollback rebuilds an older deployment from the commit it was built from.

  1. Find a row marked Superseded — a version that was live before this one.
  2. Click the rollback button on that row.
  3. Confirm. A new deployment starts, tagged rollback, and the row it came from is tagged rolled back.

Only Superseded rows can be rolled back to. Live is already serving, and Failed rows never produced a working version to return to.

A rollback uses your current environment variables, not the ones in place when that version was first built. If you have changed a variable since, restore it before rolling back.

Metrics

While a deployment is live, the panel shows CPU, Memory and Requests for it over a 1h, 6h or 24h window. Samples are kept for 7 days.

Changing your URL

Click the pencil button next to Publish to open Rename URL slug. The slug is the first part of your production URL.

  • Lowercase letters, digits and hyphens; it cannot start or end with a hyphen.
  • Some names are reserved and will be refused.
  • Once per 24 hours per project, and not while a deploy is in flight.

The old URL stops working immediately, so re-share the new one with anyone holding a link.

To serve the app from a domain you own, see custom domains — your poleved.app URL keeps working alongside it.

Unpublishing

Click Unpublish on a live deployment and confirm. The production URL goes offline and the row becomes Unpublished. Nothing is deleted: click Publish whenever you want it back.

Limits & notes

  • Build timeout is 10 minutes. Cold first builds are the slowest you will see.
  • Build logs and build artifacts are kept for the 2 most recent deployments per project. Older rows stay in the list, but their log is cleared. Rolling back to an older row still works — it rebuilds from that version's commit rather than reusing a stored image.
  • Metrics samples are kept for 7 days.
  • Slug rename: once per 24 hours per project. The old URL stops working at once.
  • Rollback is offered on Superseded rows only, and uses current env vars.
  • Env vars: 50 per project, 4 KB per value, applied on the next deploy.
  • Your plan sets how many deployments can be live at once — 1 on Spark, 3 on Maker, 10 on Studio.
  • Limits may change during alpha.

Related