Supported web projects can have a preview URL on their task. This guide describes the URL, updates, lifecycle, and access.
The URL
Preview URLs follow this shape:
https://<team>-<task-id>.preview.veflow.ai
For example, task PAR-125 on the paragon team uses paragon-par-125.preview.veflow.ai. The address stays the same as the PR receives updates.
When previews are provisioned
A managed run starts the development server after opening its PR, when the repository has a supported dev script. Watch the task banner for startup progress.
External preview links appear when supported deployment providers post them on the connected PR.
When previews refresh
Every push to the PR branch triggers a rebuild. The URL stays the same; the running instance behind it picks up the new commit.
Wait for the updated preview before reviewing a new push. Startup and rebuild time depend on the project and its dependencies.
When previews tear down
Veflow stops hosted previews as tasks or PRs close and when runtimes become idle. A stopped runtime no longer serves the app, but the task keeps its preview controls.
Use Stop preview to release the runtime and Restart preview when you need it again. Restarting requires a plan with live previews.
Scoping & access
By default, preview URLs are public. Anyone with the link can open them. A team name and task identifier should not be treated as an access control.
Use the previewed app's own authentication for access to protected features and data. External preview providers may have their own access controls.
What runs in the preview
The hosted preview runs a browser-facing web project through its npm run dev script. The server must listen on the port expected by the runtime.
Native mobile apps, desktop applications, and background workers without an HTTP interface don't have a hosted app preview. They can still produce PRs for review.
For help with a custom setup, email hi@veflow.ai with the project’s start command and any services it needs.