# How can I use Vercel with GitHub IP restrictions?

**Author:** Tilly Gee

---

## What is the constraint?

When you have an [IP allowlist](https://docs.github.com/en/enterprise-cloud@latest/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list) enabled on GitHub, you need to configure which IPs can access your resources in your GitHub account. Because the Vercel GitHub integration uses the API to access your git repos, it means that the restriction will apply to things such as project creation, repository linking and accessing your source code during the build step. By default, Vercel's infrastructure uses a dynamic range of IP addresses for outbound requests, which can make allowlisting a challenge.

## Can I still use Vercel whilst keeping IP restrictions enabled?

Yes! You can still use Vercel with this feature enabled by deploying as part of your GitHub actions or just using the [Vercel CLI](https://vercel.com/docs/cli) directly.

When using GitHub actions, you will need to deploy your project with `vercel build` and then `vercel deploy --prebuilt`. This allows you to build your project without exposing your source code to Vercel. This skips the build step on Vercel and uploads the previously generated `.vercel/output` folder to Vercel, meaning Vercel does not need to access the GitHub API, so you don’t need to allow any Vercel IPs.

[**Learn more about how to configure GitHub Actions and Vercel**](https://vercel.com/guides/how-can-i-use-github-actions-with-vercel) for custom CI/CD workflows.

## Enterprise Customers

If you have an Enterprise team on Vercel, please reach out to your Vercel representative directly, who can discuss custom options to set this up using the GitHub integration.

---

[View full KB sitemap](/kb/sitemap.md)