Skip to content
RivetUI

Card

Groups related content and actions into clearly defined regions.

@rivetui/card

Preview

Explore each composition interactively, then open its code in the same context.

Default

Compose only the regions needed to create clear hierarchy around related content and actions.

Note
CardHeader and CardFooter are optional. A content-only card is valid when extra regions would add no useful structure.

Production gateway

Public entry point for traffic routed through the Frankfurt region.

Requests
28.4k
Latency
84 ms
Errors
0.02%
Operational

Composition

Adapt the same primitive to metrics, settings, or action-oriented content without adding new card variants.

Worker capacity

Runtime allocation for the current environment.

72%18 / 25 active

Private network

Isolate services from public ingress and route traffic internally.

Registry

Installation

Add the component source and its declared dependencies with the shadcn CLI.

Install component
bunx --bun shadcn@latest add @rivetui/card
Inspect registry item

Public interface

API reference

Component-specific props are listed here. Native element and Base UI props continue to pass through.

Card

PropTypeDefault
classNamestring—
Rivet UI / CardComponents engineered, not decorated.