Free for non-commercial sites
For non-commercial & hobby sites
Deploy from CLI or personal git integrations
Previews for every git push
$20/mo per member
For the optimal development & collaboration workflow
Up to 1 TB of bandwidth
Unlimited function requests & 1000 GB-hours of execution
Dynamic edge caching
Suited to your business
Maximize developer productivity
Scaled bandwidth pricing
Isolated infrastructure for the fastest builds & zero queues
Dedicated support manager & SLAs
All plans include Bandwidth, Builds, and Serverless Function Execution subject to our fair use policy.
Serverless Function Execution
Serverless Function Execution Timeout
Multi-Region Serverless Functions
Unlimited Serverless Function Invocations
$20/mo per member
Deployments per Day
Domains per Project
Vercel Projects Connected per Git Repository
HTTPS/SSL by default
Password Protected Previews
SAML Single-Sign On and 2FA
SSO Protected Previews
Custom Firewall Rules
Email Support SLA
SLA for 99.99% Uptime
Advanced Support Scope
Dedicated Customer Success Engineer
Code Audits & Professional Services
Our Hobby plan is for personal, non-commercial use. Pro is for small teams with moderate bandwidth and collaboration requirements. Enterprise is for teams seeking greater performance, collaboration, and security. Contact our sales team to learn more.
We are glad you are growing and scaling with Vercel! Please contact us to discuss your resource requirements and we can customize a plan for your team.
No, there is not a limit.
Potentially. Transfer fees are dependent on the TLD and the domain renewal fee. The domain-transfer workflow will alert you of fees before initiating transfer.
We calculate the total response size which includes headers along with the number of bytes in the body. Anything served from our servers from your project’s domain will be counted as bandwidth (including JSON responses for Serverless Functions).
When it comes to Serverless Functions though, GB-Hrs is calculated by multiplying the duration that your functions ran for by the amount of memory that was consumed by them.
To learn more, check out the Usage documentation.