Status Cards, animated React component
Free React status page cards. Each service shows its state, uptime and a live response-time line that redraws as new samples arrive, with a 30-day strip you can scrub. A banner above sums up the worst state. Press a status to simulate an incident and the colours, numbers and line all answer.
- Free
- Dashboards
- Hover
Like Status Cards? 287 more are in Pro.
Pro unlocks all 287 Pro components, every template and block, and everything we release next. Status Cards stays free.
Set it up, copy the code
Choose values for the main props and the JSX on the right updates to match.
Colours for a light or a dark page.
Runs a scripted incident through the cards, with a live latency feed, until the visitor touches a status. Never runs under reduced motion.
Your JSX
<StatusCards
tone="light"
autoplay={false}
/>Props
| Prop | Type | Default | What it does |
|---|---|---|---|
| items | StatusCardItem[] | — | The services to show: name, status, and optionally note, uptime and latency. Four demo services when left out. |
| tone | "light" | "dark" | "light" | Colours for a light or a dark page. |
| autoplay | boolean | false | Runs a scripted incident through the cards, with a live latency feed, until the visitor touches a status. Never runs under reduced motion. |
| onStatusChange | (item, next) => void | — | Called when someone presses a status to move it on. |
| className | string | "" | Extra classes for the outer element. |
Add it to your project
- 1
Set up your project once
You need a Next.js project with Tailwind CSS and the
@/import alias. In its root folder, run this once. It createscomponents.jsonand thecn()helper insrc/lib/utils.ts:npx shadcn@latest init -d
Starting from nothing? The Quick Start walks through the whole thing.
- 2
Connect the registry
Run this once per project. It writes the Nexus UI entry into
components.jsonfor you:npx shadcn@latest registry add "@nexus-labs=https://www.nexus-ui.com/api/registry/{name}"Type it exactly as shown.
{name}is filled in by the CLI with the component you ask for, so you never replace it.
- 3
Add the component
Run this from your project root. It adds the component, the helpers it imports and its npm packages.
npx shadcn@latest add @nexus-labs/status-cards
- 4
Check what was added
With a project made as in the Quick Start (a
src/folder), these files land in it:components/status-cards/index.tsstatus-cards.tsx - 5
Copying by hand? Skip the registry
Instead of steps 2 and 3 you can copy the files yourself, with no registry and no API key. Step 1 still applies, so that
cn()exists. Install the packages:npm install framer-motion
Then show the source and create each file at the path it gives:
- 6
Use it in a page
Installing only adds the files. Import the component in a page and render it. The Usage tab on the preview shows a fuller example with props:
// src/app/page.tsx import { StatusCards } from "@/components/status-cards"; export default function Page() { return ( <main> <StatusCards /> </main> ); }
Like Status Cards? 287 more are in Pro.
Pro unlocks all 287 Pro components, every template and block, and everything we release next. Status Cards stays free.
Status Cards questions
How do I install the status cards?
Run `npx shadcn@latest add @nexus-labs/status-cards`. It adds the component and installs framer-motion.
What data does each card need?
A `name` and a `status` of operational, degraded, outage or maintenance. `note`, `uptime` and `latency` are optional. The response-time line and the 30-day strip are generated from the name, so they stay the same between renders.
Can I feed it real data?
Pass your own `items` and update `status` as your monitor reports. The cards react to every change. The line and the 30-day strip are illustrative, so replace them with your own series before showing real history.
How does a visitor simulate an incident?
Pressing the status pill moves a card to the next state and calls `onStatusChange`. With `autoplay` a scripted incident runs by itself until someone touches a pill.
Is colour the only signal?
No. Every state has a text label, each card has an accessible name that includes its state and uptime, and a polite live region announces changes to the summary banner.