Skip to main content
When a scale-to-zero project has a connected repository, every open pull request gets a preview environment: a full deployment of that PR’s code on its own managed subdomain.

​
Lifecycle — fully automatic

  1. PR opened → preview created and deployed.
  2. PR updated → preview redeployed with the new commits.
  3. PR closed or merged → preview torn down; the app and subdomain are released.
There is nothing to configure beyond connecting the repository.

​
Inspecting previews

API: GET .../previews; MCP: await korve.previews.list({ orgId, projectId }). See the Previews API.

​
Removing one by hand

Closing the pull request does this automatically — manual removal is for previews you want gone early (or whose PRs live forever).

​
Notes

  • Previews run with the project’s current environment variables.
  • Preview traffic meters like any other scale-to-zero usage and counts toward the project’s budget.
  • Previews currently apply to scale-to-zero projects.