Vercel is changing the terms for Hobby and Pro – check this

What has changed

Vercel’s updated terms take effect on 19 October 2026. The change covers Hobby and Pro subscriptions purchased directly through the service. In Vercel’s changelog, the company highlights clearer rules on credits, automatic renewal, cancellation, accounts managed by an employer and certain consumer rights in the EU and UK. The product-specific rules have also been moved to separate service terms.

For anyone building a company, the main question is not whether the text has become longer. The question is what risk you take by putting an important part of the business on a particular plan.

The terms make a clear distinction between Hobby and paid plans. According to the agreement, Hobby may only be used for personal or non-commercial purposes. Vercel also reserves the right to change the plan’s features and limits, stop offering the plan or suspend projects and deployments.

The new wording also clarifies how purchased and included credits work. Credits are tied to Vercel’s fees, cannot be transferred and may expire. Subscriptions renew automatically unless renewal is turned off. Prices passed on from external providers may change when their prices change.

This does not mean that Vercel has suddenly become unsuitable. It means that the choice between Hobby and Pro needs to be treated as a business decision, not merely as a way to keep costs down during development.

Hobby is not a free business plan

It is easy to start on Hobby while a product still feels like an experiment. You may have no revenue, few visitors or be testing the idea with a small group. But the boundary in the agreement is not primarily about traffic or turnover. It is about personal or non-commercial use.

A service may therefore be commercial before it has started making money. This applies, for example, if you:

• show the product to prospective customers or investors
• collect leads ahead of a launch
• accept bookings, orders or payments
• operate the service through a limited company
• use it as part of paid work
• offer a tool intended to become part of the company’s operations

Commercial use cannot always be determined by a simple label. A personal portfolio site and a site that actively sells consultancy services may look the same technically but serve different purposes. If the project is connected to how the company finds customers, provides a service or develops a future offering, you should not assume that Hobby is suitable simply because the product is at an early stage.

The current agreement also makes Hobby less predictable. Vercel states that projects and deployments on the plan may be suspended or removed, even without prior notice. The plan’s features and limits may also change.

This is primarily a matter of continuity. A prototype being unavailable for a while is often manageable. A product with signed-in users, paying customers, active campaigns and incoming webhooks from Stripe is another matter.

Practical rule of thumb: when a Vercel deployment becomes important to the company’s sales, delivery or customer relationships, you should explicitly check that the plan permits its use. Do not let the choice of plan be determined by Hobby having been the default when the project was created.

Suspension can have wider consequences than a broken website

When a frontend on Vercel becomes unavailable, the rest of the system may continue to work. Supabase may continue storing data and Stripe may continue recording events. But users may be unable to sign in, manage their accounts or complete a purchase.

The problem becomes more serious when Vercel is also used for server functions. A suspension may then affect:

• API calls from the web app
• webhooks from Stripe and other services
• scheduled jobs
• generation of documents or emails
• authentication callback addresses
• file uploads and processing
• internal administration tools

Vercel’s terms allow the company to terminate accounts for breaches of the agreement, non-payment and exceeding usage limits. They also state that content may be deleted when an account is terminated. For Hobby, there is additional wording stating that projects may be removed or suspended.

You therefore need to distinguish between a restriction and a suspension. A restriction may mean that a feature becomes slower, stops working or starts costing more. A suspension may remove the entire public entry point to the product.

Also check which email address owns the account. The updated terms include a specific section on accounts that use a domain belonging to an organisation. If an employer or another organisation verifies the domain, projects created within its team may be managed by the organisation. Vercel also describes a process in which the user is notified and given time to move personal content if the account is to become organisation-managed.

You should therefore not use a temporary work address for a project that is actually owned by your own company. Make sure that the account, team, Git repository, domain and payment method have the correct owner from the outset.

How to review your current use

Start by mapping what is actually hosted on Vercel. Do not look only at the website shown in the browser. Over time, a project may have gained more dependencies through Lovable, ready-made templates, integrations and quick changes.

Work through the following checklist:

• Check whether the project is on Hobby, paid Pro or a trial.
• Describe the project’s purpose in one sentence without technical terms.
• Note whether the project is used for sales, customer work, payments or service delivery.
• Check who owns the Vercel team and which email domain the account uses.
• Check who owns the Git repository and can give a new hosting provider access.
• List all environment variables and document where their values come from.
• Identify functions, webhooks, scheduled jobs and callback addresses.
• Check where the domain is registered and who can change the DNS settings.
• Make sure the payment method works and that the right person receives notifications.
• Read Vercel’s current acceptable use policy for content and technical usage patterns.
• Check the model training setting if the project contains code or data that should not be used for that purpose.
• Save a copy of the terms or record the date when the review was carried out.

Vercel’s terms state that content from Hobby and a Pro trial may be used for model training. For paid Pro, this is not enabled by default, but the setting should still be checked. This is particularly important if the project contains customer data, internal business logic or material received under a confidentiality agreement.

Also review subscription renewal and credits. A cancellation or downgrade normally takes effect at the next renewal. Included credits may expire when the subscription period ends, while separately purchased credits follow their own rules. Do not therefore treat credits as a balance that can safely be saved or transferred.

If anything is unclear, contact Vercel and describe the use in specific terms. Do not simply ask whether your project is commercial. Explain what users do, how the company uses the service and which parts run on the platform. Save the response with your technical documentation.

Build a migration plan before you need it

A migration plan does not mean that you should leave Vercel. It means that the product should not be locked in through a lack of knowledge. You should know what needs to change if the terms, costs or business requirements are no longer suitable.

Start with the code. The project should be kept in a repository controlled by the company. It should be possible to install, build and start the project without anyone having to export it manually from an individual’s account.

Then document the configuration. Environment variables should have clear names and a recorded source, but secret values should be kept in an appropriate password or secrets manager. Record which variables are needed in development, testing and production.

Next, review anything linked to Vercel addresses:

• permitted Supabase redirect addresses
• Stripe webhook addresses
• OAuth callback addresses
• links in email templates
• permitted domains for external API services
• DNS records and certificates
• scheduled calls
• monitoring and error reporting

The domain is your most important switch. If it is managed outside the hosting account and you have access to the DNS settings, traffic can be redirected to another environment. If the domain, code, hosting and payment method are all held in the same private account, moving becomes considerably more difficult.

Also back up data in the systems where it is actually stored. If the database is in Supabase, you should understand its backup and restoration options. Files, user details and payment history may be held by different providers and need to be handled separately. Vercel’s terms explicitly state that you must also maintain your own backups of your content.

A useful migration plan does not need to be long. It should state:

• who decides whether to move
• who has access to each affected account
• which functions need to work first
• which external addresses need to be updated
• how to verify sign-in, payments and data access
• how traffic is redirected
• how to revert if something goes wrong

Review the plan whenever the product gains a new critical integration or the provider’s terms change. The choice of plan and infrastructure then becomes part of the company’s ongoing risk management, rather than an urgent technical issue after something has already stopped working.

If you want to review the choice of plan, dependencies and migration route with someone to ask, that is a good place to start.

---

Source: Vercel changelog