Service Terms

1. Domain Name Registration

By using or accessing the domain name reservation services, you further acknowledge that you have read, understand, and agree to be bound by the Domain Name Registration and Services Addendum which is hereby incorporated into this Agreement.

2. Marketplace

By using or accessing Vercel’s Marketplace, you further acknowledge and agree that you have read, understand, and agree to be bound by Vercel’s Integrations Marketplace Service Terms.

3. AI Products and Services

By using or accessing Vercel's AI Products and Services, you further acknowledge and agree that you have read, understand, and agree to be bound by Vercel's AI Product Terms, which are incorporated into this agreement.

4. Flat Rate CDN

Vercel provides Flat Rate CDN, with tiered Team-level CDN capacity, as described at vercel.com/pricing and in the Documentation. Flat Rate CDN is available only with paid plans and will be disabled if you cease to be on a paid plan. If your usage exceeds the current Flat Rate CDN’s tier capacity, at the start of the next billing cycle, you will be automatically (a) upgraded to the tier corresponding to your usage and charged the fees for that tier at the start of your next billing cycle, or (b) switched to the usage based pricing described at vercel.com/pricing (“PAYGO Rates”), if you exceed the highest tier allocation. You may disable Flat Rate CDN at any time and be charged at PAYGO Rates from the start of your next billing cycle.

If a higher tier fee applies, then Vercel will give you at least seven (7) days’ prior notice (or any longer period applicable law requires). You may avoid the higher tier fee by downgrading, disabling Flat Rate CDN, or canceling your self-serve subscription before your next billing cycle. Tiers do not downgrade automatically; you may downgrade at any time, effective at the start of your next billing cycle.

If your usage violates the Flat Rate conditions in the Documentation, Vercel may at the start of the next billing cycle (a) reduce the performance (e.g., move projects to the Flex CDN tier) of the CDN Services made available to you, (b) disable Flat Rate CDN and charge you the PAYGO Rates, or (c) take other appropriate actions as reasonably determined by Vercel, each in accordance with the Documentation. Flex CDN is a best-effort service with no latency or availability guarantees.

5. Connect

1. Definitions

“Customer Managed Connector” means the connector operating model where Customer registers an OAuth client directly with a Third Party Platform and authorizes Vercel to store Customer's credentials and exchange tokens via that OAuth client on Customer's behalf. “Third Party Platform” means a third party platform that Customer interacts with using Vercel Connect. “Vercel Assisted Setup” means the process where Customer authorizes and instructs Vercel to perform some or all of the steps required for Customer to register an OAuth client directly with an eligible Third Party Platform. “Vercel Managed Connector” means the connector operating model where Vercel registers an OAuth client with the Third Party Platform and Customer authorizes Vercel's OAuth client to access Customer's account or workspace.

2. General

(a) Customer may only use Vercel Connect in either Customer Managed Mode, including through Vercel Assisted Setup, or Vercel Managed Mode.

(b) Vercel will implement all interactions with Third Party Platforms through Vercel Connect at the instruction of Customer. Customer retains primary responsibility under Customer's agreements with those Third Party Platforms in connection with Customer's use of Vercel Connect.

3. Vercel Managed Connector

Customer may use Vercel Managed Connector only with permitted Third Party Platforms and will be bound by any terms of service imposed by that Third Party Platform.

4. Vercel Assisted Setup

By using Vercel Assisted Setup, Customer authorizes and instructs Vercel to connect and retrieve relevant credentials and data from the eligible Third Party Platforms on Customer’s behalf for the purposes of expediting its Customer Managed Connector setup. Vercel Assisted Setup is performed as a one-off action and Vercel does not manage any connection created under it.

5. Restricted Use

Customer must not route through Vercel Connect any Cardholder Data (as defined under PCI DSS), Protected Health Information (as defined under HIPAA), Non-Public Personal Information (as defined under the Gramm-Leach-Bliley Act), ITAR-controlled technical data, or other categories of regulated data designated by Vercel, except as expressly approved by Vercel in writing.

6. Customer Actions

Customer authorizes and is responsible for all actions initiated by it or its users, applications, integrations, deployments, or agents through Vercel Connect, including the creation, installation, configuration, linking, unlinking, deletion, or use of connectors and actions taken via tokens minted or exchanged by Vercel Connect.

7. Third Party Platform Availability

Vercel may at any time add or remove Third Party Platforms to Vercel Connect without notice to Customer. Vercel does not warrant availability or uptime of any specific Third Party Platform. If a Third Party Platform suspends, terminates, or materially modifies developer access, Vercel will use commercially reasonable efforts to restore service, but is not liable for the interruption.

8. Token Revocation

Customer is responsible for revoking tokens with Third Party Platforms. At Customer’s request, Vercel will attempt to revoke tokens but some attempts may not succeed.

9. Representations and Warranties

Customer represents and warrants that:

(a) Customer’s instructions or Vercel’s provision of Vercel Connect under this Agreement would not cause Customer to breach any agreement with a Third Party Platform; (b) Customer holds all rights necessary in the credentials, scopes, and content Customer provides to or routes through Vercel Connect; and (c) all data routed through or in connection with Vercel Connect will be done in accordance with the applicable agreement with the Third Party Platform.

6. Enterprise Managed Users

These Enterprise Managed Users Service Terms apply where Customer provisions or verifies to Vercel an email domain for a Team or Organization.

1. Domain ownership

Customer represents and warrants that it owns or controls each domain it provisions or verifies and will, within 5 business days, promptly notify Vercel of any domain it ceases to own or control.

2. Managed Accounts

Customer agrees that (a) Managed Accounts (as described in Section 6 (Managed Teams and Managed Accounts) of the Agreement) are Customer’s Authorized Users; (b) Customer's Agreement governs the Managed Accounts; and (c) the Customer is liable for the actions it takes with respect to Managed Accounts, including any personal content accessed in them.

3. Notices and consents

Customer must comply with applicable law with respect to its management of Managed Accounts. Vercel will provide the account-level notices described in Section 6 (Managed Teams and Managed Accounts) of the Agreement.

4. Disputes

Customer is responsible for resolving any disputes between Customer and third parties with respect to the Managed Accounts.

7. Bring Your Own Cloud

In using Bring Your Own Cloud (BYOC), Customer may copy, install and run Vercel-provided runtime and provisioning tools solely as necessary for its authorized use of BYOC under the Agreement. Open-source components remain governed by their applicable licenses.

Customer must have authority to connect its AWS accounts to Vercel and authorizes Vercel to invoke designated functions and process associated requests, responses, logs and metadata outside those accounts as necessary to provide BYOC. Customer’s AWS accounts, resources and AWS-provided services are Non-Vercel Services. Customer is responsible at all times for provisioning, securing, maintaining and backing up its AWS resources, and paying relevant AWS charges. Vercel’s backup obligations exclude Customer-managed AWS resources.

When Customer discontinues use of BYOC, Customer must revoke Vercel’s BYOC access to its AWS accounts and remains responsible for its AWS resources and charges. Except as expressly modified above, the Agreement remains unchanged.

8. Organizations

These Vercel Organizations Terms govern the administration of or participation in an Organization.

1. Definitions

“Organization” means one or more Sub-Teams organized under the Organization. “Organization Admin” means the Authorized Users of the Customers in the ‘Admin’ role to manage the Organization. “Sub-Team” means a Team in an Organization.

2. Customer Responsibility

The Customer is solely responsible for the entire Organization, including for (a) all activity, use, and fees across the Organization, including by a Sub-Team; (b) the policy configurations of the Organization, their effect and consequences; and (c) obtaining all notices to and consents from its Organization users required to provide Admin Access (as defined below) to the Organization Admin. Each Organization Admin and each user of the Sub-Team is Customer’s Authorized User. Customer acknowledges that the Organization structure and settings do not affect, and are not a commitment regarding, where data is processed or stored.

3. Organization Admin Rights and Obligations

Customer authorizes Vercel to (a) give each Organization Admin access to the software, code, data, information, feedback, suggestions, text, input, content, and other materials submitted by Sub-Teams for the Services, settings, Sub-Team user information, usage, and activity and audit logs (“Admin Access”), and (b) act on all instructions from an Organization Admin. Customer, acting via Organization Admins, is responsible for resolving any disputes with or between Sub-Teams, or any members of the Organizations.

4. Adding and Removing Sub-Teams. An existing Team may become a Sub-Team of an Organization by accepting an invitation from an Organization Admin. Customer is responsible for obtaining and maintaining all necessary consents and authorizations required for that Team to join the Organization. Customer is responsible for the Team (now as a Sub-Team) fees accrued or outstanding to Vercel at the time of joining the Organization. Customer acknowledges that any separate agreement covering that Team ceases to apply to it from the time of joining the Organization and at all times while part of the Organization. If the Organization removes a Sub-Team, then (a) the Customer ceases to be responsible for that Sub-Team (accrued fees remain payable) and (b) that Sub-Team and all of its projects will be deleted, unless the Organization Admin for that Sub-Team transfers those projects to another Team outside of the Organization.

5. Managed Domains

Vercel will treat an Organization as a Managed Team (if Customer has one) as described in the Vercel Terms of Service for every domain provisioned by or verified for the Customer or any Sub-Team. The Organization Admins may exercise the Managed Team's rights in accordance with the Enterprise Managed Users Service Terms for the entire Organization. An Organization is subject to the notice and recovery process in Enterprise Managed Users Service Terms.

6. Billing

Fees incurred under the Organization are consolidated and payable by Customer as a single payer, and committed amounts form a single Organization-level pool unless otherwise agreed in writing between the parties. Per-Team usage attribution is informational and does not modify the Fees payable by Customer. Customer acknowledges that any enforcement of spend limits may be delayed and does not discharge payment obligations for any Fees incurred.