Skip to content

Design system

Documentation

DesignComponents / Pricing

Components / Pricing

Beta

Pricing

A responsive plan comparison grid that keeps price, action, and included capabilities easy to scan.

On this page

Examples

Plan comparison

A responsive grid keeps the price, action, and feature list in one scannable comparison.

Choose the right pace

Compare the essentials, then choose the plan that fits your next stage.

Starter

A clear first step for small teams.

$0/ month
  • 1 workspace
  • Core project views
  • Community support

Growth

More room for a team that is moving quickly.

$24/ month
  • Unlimited projects
  • Advanced sharing
  • Priority support

Scale

Controls and support for complex organizations.

$80/ month
  • Unlimited workspaces
  • SAML single sign-on
  • Dedicated support

Pricing plan comparison

Slots and supporting context

Icons, badges, feature headings, notes, and actions stay owned by the consuming feature.

Flexible by design

Plans that meet you where you are

Use slots for meaningful details while the grid keeps every comparison aligned.

Solo

A focused toolkit for independent work.

$12/ month

Included in Solo:

  • Personal workspaceOne private space for your work.
  • Unlimited drafts
Cancel whenever you like.

Team

Shared workspaces for a small, aligned team.

$28/ member / month

Everything in Solo, plus:

  • Shared workspaces
  • Comments and mentions
  • Team activity history

Secure

Governance and visibility for larger organizations.

Custom

We will scope the right rollout together.

Everything in Team, plus:

  • SAML single sign-on
  • Audit exports
  • Security review

Pricing cards with optional slots

Long feature lists

Cards grow with their content so important features remain readable instead of being clipped.

Team

A balanced set of tools for day-to-day work.

$28/ member / month
  • Unlimited projects
  • Custom views
  • Comments and mentions

Business

More control for larger, faster-moving teams.

$64/ member / month

Everything in Team, plus:

  • Unlimited projects
  • Custom views
  • Comments and mentions
  • File attachments
  • Automations
  • Workspace history
Annual billing includes two months free.

Enterprise

Security and support tailored to your rollout.

Custom

We will help scope a plan for your organization.

  • Unlimited projects
  • Custom views
  • Comments and mentions
  • File attachments
  • Automations
  • Workspace history
  • Dedicated success manager
  • Custom data retention

Pricing cards with long feature lists

When to use

Use Pricing when people need to compare two or more plans before choosing a next step. It works for subscriptions, service tiers, and feature packages. Use Card for one bounded surface, and use a Table when many row-by-row comparisons matter more than plan-level hierarchy.

Usage

pricing-basic.tsx
import { Button } from "@phuctech/ui/components/button";
import { Pricing } from "@phuctech/ui/components/pricing";

const plans = [
  {
    id: "starter",
    name: "Starter",
    description: "A clear first step for small teams.",
    price: "$0",
    priceSuffix: "/ month",
    features: [
      { label: "1 workspace" },
      { label: "Core project views" },
      { label: "Community support" },
    ],
    action: <Button variant="outline">Start free</Button>,
  },
  {
    id: "growth",
    name: "Growth",
    description: "More room for a team that is moving quickly.",
    price: "$24",
    priceSuffix: "/ month",
    features: [
      { label: "Unlimited projects" },
      { label: "Advanced sharing" },
      { label: "Priority support" },
    ],
    action: <Button>Choose Growth</Button>,
  },
  {
    id: "scale",
    name: "Scale",
    description: "Controls and support for complex organizations.",
    price: "$80",
    priceSuffix: "/ month",
    features: [
      { label: "Unlimited workspaces" },
      { label: "SAML single sign-on" },
      { label: "Dedicated support" },
    ],
    action: <Button variant="outline">Talk to sales</Button>,
  },
] as const;

export function Example() {
  return (
    <Pricing
      aria-label="Plans"
      heading="Choose the right pace"
      description="Compare the essentials, then choose the plan that fits your next stage."
      plans={plans}
    />
  );
}

Pricing owns the layout and comparison semantics. Supply an ordered plans array, and provide the action slot from the consuming feature so navigation, loading, and business state stay outside the design component.

Composition

  • Give each plan a stable id, a clear name, a price, and a short audience description.
  • Use featured for one plan that deserves visual emphasis; keep the readable badge or explanation in badge.
  • Use featureHeading for inheritance copy such as “Everything in Growth, plus:”. Keep every capability in text inside features.
  • Pass a real Button or link as action. Pricing does not invent navigation or request state.
  • Keep pricing context in billing or note; do not hide conditions in a tooltip or color-only treatment.

API

Component API
PropTypeDefaultDescriptionConstraints
PricingHTMLSectionElement props + planscolumns: 3Responsive section wrapper and plan grid.plans must be ordered; columns supports 2, 3, or 4.
PricingPlanid, name, price, and optional slotsfeatures: []Data shape for one plan card.Use a stable id and keep price context explicit.
PricingCardHTMLArticleElement props + plan fieldsfeatured: falseStandalone card for custom compositions outside Pricing.Use a meaningful heading in name and keep action content keyboard reachable.
PricingFeaturelabel, description?, included?, icon?included: trueOne readable capability row.Never rely on the check/minus icon alone to convey meaning.
columns2 | 3 | 43Controls the responsive grid columns at wider breakpoints.The grid collapses to one column on narrow screens.
featuredbooleanfalseAdds a quiet brand border, tint, and ring to a plan.Visual emphasis only; it does not change semantics or action behavior.
action / badge / icon / noteReactNode—Slots owned by the consuming feature.Use accessible controls and labels in the supplied nodes.

Tokens

Component tokens
TokenRoleEffective valueUsage
--color-bg-surface / --cardPlan surfacesemantic surface backgroundKeeps cards legible in both themes.
--color-border-default / --borderPlan boundaryshared neutral borderSeparates comparable plans without heavy decoration.
--primaryFeatured emphasisbrand action colorMarks one featured plan with a subtle border, tint, and ring.
--radius-2xlCard geometryshared large radiusGives the comparison grid a consistent surface silhouette.
--type-size-sm / --type-size-xlHierarchyshared body and heading scaleSeparates plan labels, supporting copy, and price values.

Accessibility

  • Pricing renders a section, article cards, h2/h3 headings, and a list for features so the comparison has a navigable structure.
  • Keep the plan name and feature labels visible. Icons are decorative defaults and are marked aria-hidden.
  • Supply a real Button or link in action; ensure its visible label describes the plan or next step.
  • Long feature lists grow the card naturally. Do not clip them or put required pricing terms in a hover-only surface.
  • Test at narrow widths and with keyboard focus; the grid becomes one column so every action remains reachable.

Do and don’t

Do

Keep the price, billing context, CTA, and included capabilities in each plan’s hierarchy.

Don’t

Use color alone to mark the best plan, hide conditions in a tooltip, or make the entire card an unlabeled click target.

  • Card is the simpler bounded surface for one related content group.
  • Button supplies the action slot and keeps loading/disabled behavior explicit.
  • Badge can label a featured or recommended plan without replacing its text hierarchy.
  • Table is better for dense row-by-row feature comparisons.