--- title: "Get full-stack Preview Environments with Encore and Vercel – Encore Blog" url: https://daily.dev/posts/get-full-stack-preview-environments-with-encore-and-vercel-encore-blog-6r6fbcmwt source_url: https://encore.dev/blog/preview-envs type: article source: "Encore" published: 2026-05-31T07:49:20.882Z updated: 2026-05-31T09:14:16.846Z tags: ["cicd", "vercel"] reading_time: 5 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Get full-stack Preview Environments with Encore and Vercel – Encore Blog **[Encore](https://daily.dev/sources/encore-blog)** · 5 min read · 0 upvotes · 0 comments ## Summary Encore and Vercel have partnered to enable full-stack Preview Environments that span both backend and frontend. The core challenge was that Vercel's preview environments were tied to individual commits without PR number context, making it impossible to automatically route frontend previews to the correct backend environment. After a quick collaboration with Vercel's CEO, a new environment variable `VERCEL_GIT_PULL_REQUEST_ID` was introduced. Encore's generated clients now use this variable to automatically route API calls to the matching backend Preview Environment, enabling end-to-end testing of changes across the full stack with minimal configuration. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Data Previews](https://daily.dev/posts/data-previews-dqxmcmh1i) · Tinybird · 1 upvotes · 0 comments --- Tags: [#cicd](https://daily.dev/tags/cicd), [#vercel](https://daily.dev/tags/vercel) [View this post on daily.dev](https://daily.dev/posts/get-full-stack-preview-environments-with-encore-and-vercel-encore-blog-6r6fbcmwt)