Billing

Billing applies to the hosted service, and to each organization rather than each person: the organization is the unit of billing, and its projects, members and API keys are covered by its plan. Everyone in an organization sees its plan beside the organization's name in the header's switcher; its Owner and Admins also have its Billing page (/{organization}/billing), which links to the public Plans page (/plans). Billing is in the organization's sidebar, before Settings, and g b reaches it.

The Hobby planCopy Anchor Link

Every organization starts on the Hobby plan, which is free: no card, no expiry, and no payment details asked for until it moves to a paid plan.

The plansCopy Anchor Link

The Plans page posts the three plans: Hobby, free; Pro and Teams, each one flat monthly price; packs of more capacity on either paid plan; and one add-on, SSO, on Teams alone. It posts what each plan holds, what a pack adds, and what happens past each limit. Every feature is on every plan, members are never sold, and nothing is metered: a bill is the plan and the packs an organization holds, and it does not move on its own.

Any limit Hobby gains, and any pack that goes on sale, is listed here as well, with what Hobby includes and what more of it costs, before it applies to any organization.

Changing plansCopy Anchor Link

Moving up, to Pro from Hobby or to Teams from Pro, applies at once: a first plan is bought on Stripe's Checkout page, and a move from Pro to Teams changes the subscription in place, prorated for the rest of the period, with no card asked for again.

Moving down, from Teams to Pro, takes effect when the current period ends, as a subscription you are used to does: the organization keeps Teams, and everything it holds, until then. Its Billing page names the day and offers Keep Teams, which takes the move back any time before it. A move to Hobby drops a pending move, since it ends the period first.

Moving down to Hobby, offered under Move down with the paid plans, is the subscription's cancellation: it runs to the end of the period, then the organization falls to Hobby, keeping its projects, its data and its members. Until then the Billing page names the day and offers Keep Pro or Keep Teams, which takes the move back. An organization that could not fall to Hobby — another of yours holds your Hobby place, as below — is refused the move, and the page names the ways out instead: delete it, merge its projects into your Hobby organization, or hand it to someone whose Hobby place is free.

One Hobby organizationCopy Anchor Link

While Pro and Teams are for sale, a person has one free organization, their Hobby place, as Vercel holds an account to one Hobby team: it is held by their Hobby organization, or kept by a paid one set to fall to Hobby when its period ends. Every other organization of theirs is paid for before it exists. Being a member of other people's organizations is never limited.

• Your first organization is your Hobby organization.
• Another you create while something of yours holds your Hobby place is paid for first: the panel that creates it asks whether it starts on Pro or Teams, each with what it holds, sends you to Stripe's payment page, and the organization is created the moment the payment is confirmed, and opens. Nothing is created, and nothing charged, if you leave the payment page.
• A paid organization you move to Hobby keeps its plan to the end of its period, then falls to Hobby, and holds your Hobby place from the moment you set the move; taking the move back frees the place. While another of yours holds the place, the move is refused, since the organization could not fall to Hobby: delete it, merge it into your Hobby organization, or hand it over instead, as its Billing page says.
• A card that fails until Stripe's retries run out ends the plan all the same. The organization falls to Hobby when your Hobby place is free; when another of yours holds it, the organization is paused: it keeps its projects, its data and its members, and stays readable, exportable and deletable, but takes in nothing new — exports to the OpenTelemetry endpoint, questions to the console agent, invitations and members added to a project from the organization are refused with a 402 that names Pro — until it is on Pro or Teams again, merged into your Hobby organization, handed to someone whose place is free, or, once your place frees, moved to Hobby from its Billing page. Nothing resumes on its own.
• Handing an organization over: one on Hobby, paused, or set to fall to Hobby goes only to an owner with no organization on Hobby or set to fall to it; the offer, or its acceptance, is otherwise refused, naming Pro. A paid organization goes to anyone. A paused one handed to someone whose place is free takes that place and resumes.
• Merging: the owner of a paid or paused organization can merge it into their Hobby organization from its Billing page. Every project moves across, with its API keys, its data and the people on it, and the emptied organization is deleted, confirmed with a code emailed to its owner.

Each change is written to the organization's audit log and raised in its notifications.

One member on HobbyCopy Anchor Link

While Pro and Teams are for sale, an organization on Hobby holds one member, its owner, as Vercel's Hobby team holds one person. An invitation from it, to the organization or to one of its projects, is refused with a 402 that names Pro, and one sent while the organization was on a paid plan seats nobody past that once it has fallen to Hobby: the invitation stays live for when the organization moves back. Nobody is ever removed: an organization that falls to Hobby keeps every member it has, and its Owner and Admins can still add those members to its projects, which brings nobody new in. Its Members page says so in place of the invite button, and a project's under By email, closed beside From the organization. A paid organization holds as many members as it invites, and being a member of other people's organizations is never limited.

Data outCopy Anchor Link

While Pro and Teams are for sale, each plan holds an organization's machines to so much data out a UTC day: what the read API and the CLI answer, with what each request's connection costs, and every export downloaded. The Plans page posts each plan's numbers.

• Past the day's data out, the read API and every export answer 429 until midnight UTC; the CLI's answers count toward the day but are never refused. An audit log export is built no larger than the day, so a long log comes a day's worth at a time.
• The Owner and Admins are told in the organization's feed once a day while it lasts.

Self-hosted installationsCopy Anchor Link

A self-hosted installation has no plans, no usage limits and no billing.