Three-Plan Pricing Toggle
Three plans with a monthly/yearly switch, yearly prices derived from the monthly figure so the two can never disagree.
What actually runs out on each plan, including what happens when it does — the row a pricing table leaves off.
components/plan-limits-list.tsxnpx hoverlab add plan-limits-list
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
Start a page with this section — add more, order them, and leave with the page source.
Pricing tables list what a plan includes. They rarely say what happens at the limit, which is the thing that decides whether a limit is survivable.
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
'use client'
/**
* <PlanLimitsList> — What actually runs out on each plan, including what happens when it does — the row a pricing table leaves off.
*
* Pricing tables list what a plan includes. They rarely say what happens at
* the limit, and that is the fact which decides whether a limit is
* survivable — the layout problem is that "10 GB storage" and "10 GB
* storage, then read-only" are the same row in every pricing table ever
* built.
*
* So each row's badge is hard or soft, and the detail says what the system
* actually does. The obvious wrong answer is a checkmark grid, which cannot
* express "throttled, not cut off" at all.
*
* The retention row is the one that earns the block. It is a hard limit
* whose consequence is deletion, and it is the row a pricing table would
* never carry — which is precisely why putting it here builds more trust
* than the three friendly rows above it.
*
* The API row states that you are told at 80%. A soft limit with no warning
* is a hard limit that arrives as a surprise, and saying where the warning
* fires is what makes "soft" mean something.
*
* Rows are buttons with `aria-pressed` because a real implementation opens
* the current usage behind each one. `status` and `tone` are separate so
* "hard" reads as hard for someone who cannot see that it is red — which on
* a page about what gets deleted matters more than most. The demo selects
* the first row.
*/
import * as React from 'react'
type Tone = 'neutral' | 'positive' | 'warning' | 'critical'
export interface PlanLimitsListRow {
id: string
label: string
detail?: string
tone?: Tone
/** What the badge says. Falls back to the tone name when absent. */
status?: string
}
export interface PlanLimitsListProps {
heading?: string
intro?: string
rows?: PlanLimitsListRow[]
className?: string
}
/*
Tones as complete utility classes, never assembled from fragments.
Tailwind scans source text, so `text-${tone}-foreground` produces no
class at all — the same failure as an undefined token, and just as
invisible in review.
*/
const TONE_CLASS: Record<Tone, string> = {
neutral: 'bg-muted text-muted-foreground',
positive: 'bg-primary/10 text-primary',
warning: 'bg-accent text-accent-foreground',
critical: 'bg-destructive/10 text-destructive',
}
const ROWS: PlanLimitsListRow[] = [
{ id: "row-1", label: "Seats", detail: "Hard limit. Inviting past it prompts an upgrade rather than charging silently.", tone: "warning", status: "hard" },
{ id: "row-2", label: "API requests", detail: "Soft. You are throttled, not cut off, and told at 80%.", tone: "positive", status: "soft" },
{ id: "row-3", label: "Storage", detail: "Soft, then read-only. Nothing is ever deleted for being over.", tone: "neutral", status: "soft" },
{ id: "row-4", label: "Retention", detail: "Hard. Data past the window is deleted on schedule and cannot be recovered.", tone: "critical", status: "hard" },
]
export function PlanLimitsList({
heading = "What runs out, and what happens then",
intro = "Pricing tables list what a plan includes. They rarely say what happens at the limit, which is the thing that decides whether a limit is survivable.",
rows = ROWS,
className,
}: PlanLimitsListProps) {
/*
Per-instance prefix for every id this block emits.
The literals these replaced were a latent duplicate the moment the
block appeared twice on one document, and `aria-labelledby` on a
duplicated id resolves to the first match -- so the second copy was
labelled by the first copy's heading. Client component, so `useId` is
the right tool.
*/
const uid = React.useId()
const [selected, setSelected] = React.useState<string | null>(rows[0]?.id ?? null)
return (
<section
aria-labelledby={`${uid}-plan-limits-list-heading`}
className={`w-full bg-background px-6 py-16 ${className ?? ''}`}
>
<div className="mx-auto max-w-3xl">
<h2
id={`${uid}-plan-limits-list-heading`}
className="text-2xl font-semibold tracking-tight text-foreground"
>
{heading}
</h2>
<p className="mt-2 text-sm text-muted-foreground">{intro}</p>
<ul className="mt-8 divide-y divide-border overflow-hidden rounded-xl border border-border bg-card">
{rows.map((row) => {
const isSelected = row.id === selected
return (
<li key={row.id}>
{/*
A button, not a div with onClick. The row is operable, so
it has to be reachable by keyboard and announce its
selected state — aria-pressed is what carries that.
*/}
<button
type="button"
aria-pressed={isSelected}
onClick={() => setSelected(row.id)}
className={`flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ${
isSelected ? 'bg-muted/40' : ''
}`}
>
<span className="min-w-0 flex-1">
<span className="block truncate text-sm font-medium text-foreground">
{row.label}
</span>
{row.detail ? (
<span className="mt-0.5 block text-sm text-muted-foreground">
{row.detail}
</span>
) : null}
</span>
<span
className={`max-w-[7rem] shrink-0 truncate rounded-full px-2.5 py-1 text-xs font-medium ${
TONE_CLASS[row.tone ?? 'neutral']
}`}
>
{row.status ?? row.tone ?? 'neutral'}
</span>
</button>
</li>
)
})}
</ul>
</div>
</section>
)
}
bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.Drop it at components/plan-limits-list.tsx and import it where you need the section:
import { PlanLimitsList } from '@/components/plan-limits-list'1 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.
Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.
| Prop | Type | Default |
|---|---|---|
heading | string | "What runs out, and what happens then" |
intro | string | — |
rows | PlanLimitsListRow[] | ROWS |
className | string | — |
The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.
This block is interactive. The markup below is its initial state with the event handlers stripped — you will need to re-wire the behaviour in your framework.
<!--
Plan Limits List — markup from the Hoverlab catalog.
This is the block rendered once to HTML and wrapped as a component
file. It is not a port of the React source: the Tailwind classes carry
the design, which is the part that took the work, and they are the same
in every framework.
This block is interactive in React and the handlers are NOT here.
Buttons, toggles and menus render in their initial state and do
nothing until you wire them up.
-->
<section aria-labelledby="_R_0_-plan-limits-list-heading" class="w-full bg-background px-6 py-16 ">
<div class="mx-auto max-w-3xl">
<h2 id="_R_0_-plan-limits-list-heading" class="text-2xl font-semibold tracking-tight text-foreground">What runs out, and what happens then</h2>
<p class="mt-2 text-sm text-muted-foreground">Pricing tables list what a plan includes. They rarely say what happens at the limit, which is the thing that decides whether a limit is survivable.</p>
<ul class="mt-8 divide-y divide-border overflow-hidden rounded-xl border border-border bg-card">
<li>
<button type="button" aria-pressed="true" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset bg-muted/40">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Seats</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Hard limit. Inviting past it prompts an upgrade rather than charging silently.</span>
</span>
<span class="max-w-[7rem] shrink-0 truncate rounded-full px-2.5 py-1 text-xs font-medium bg-accent text-accent-foreground">hard</span>
</button>
</li>
<li>
<button type="button" aria-pressed="false" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">API requests</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Soft. You are throttled, not cut off, and told at 80%.</span>
</span>
<span class="max-w-[7rem] shrink-0 truncate rounded-full px-2.5 py-1 text-xs font-medium bg-primary/10 text-primary">soft</span>
</button>
</li>
<li>
<button type="button" aria-pressed="false" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Storage</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Soft, then read-only. Nothing is ever deleted for being over.</span>
</span>
<span class="max-w-[7rem] shrink-0 truncate rounded-full px-2.5 py-1 text-xs font-medium bg-muted text-muted-foreground">soft</span>
</button>
</li>
<li>
<button type="button" aria-pressed="false" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Retention</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Hard. Data past the window is deleted on schedule and cannot be recovered.</span>
</span>
<span class="max-w-[7rem] shrink-0 truncate rounded-full px-2.5 py-1 text-xs font-medium bg-destructive/10 text-destructive">hard</span>
</button>
</li>
</ul>
</div>
</section>
What each framework gets across the whole catalog — effects convert properly; this rung is markup.
The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Want the whole screen instead of this one section? Open a page and copy it entire.
All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.
Browse PricingCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
Three plans with a monthly/yearly switch, yearly prices derived from the monthly figure so the two can never disagree.
One price given a whole card, with the objection a one-time price raises answered under the button rather than in a FAQ further down.
A slider that turns a rate card into the number a buyer actually cares about, with a per-tier breakdown so the total can be checked rather than taken on trust.
A real table with scoped headers, a sticky first column and screen-reader text behind every check and dash.
One-time packs with the per-credit price worked out for the reader and the saving stated rather than implied — the pricing shape for a product that sells quantity, not a subscription.
A native radiogroup of plans with the current one disabled and the prorated charge announced as it changes — the upgrade dialog, not the marketing table.
The case for the price, made beside the price — what the alternative costs, in the units a buyer already measures.