Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

API Versioning Dashboard Block for React

A sunset readiness panel for an old API version: a countdown bar, a three-condition gate worked out from the data, the consumers still calling v1 with a Migrated switch each, and a Confirm sunset button that stays inert until the gate passes.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Decide whether v1 can be turned off, with this sunset readiness panel for React with Base UI. Inside a hairline frame with a plus mark on each corner, a countdown bar runs from the announcement to the sunset day with today marked. Under it, six Tapermark consumers still calling v1 show their last call, calls a day and the endpoints they have left to move in a Progress bar, each with a Switch named Migrated. A gate at the end checks three conditions worked out from the data: no v1 calls for seven days, every consumer acknowledged, and the brownout test done. Flipping a Migrated switch updates the gate and the share of traffic still on v1. The Shine Button Confirm sunset is the one primary and stays inert, with its reason, until the gate passes; Notify consumers only logs. It's built from Switch, Progress, Button, Shine Button and Guides. For API platforms and developer relations teams.

FAQ

How do I fill it with my consumers?

Edit CONSUMERS: a name, the ISO date of its last v1 call, its calls a day, the endpoints it still calls out of its total, and whether it has acknowledged. ANNOUNCED, SUNSET and AS_OF are the three dates, ALL_CALLS is traffic across every version, and BROWNOUT describes the test. The countdown, the conditions and every figure are worked out from those.

How is the gate decided?

The first condition passes when every consumer that hasn't migrated last called v1 seven or more days ago. The second passes when every one that hasn't migrated has acknowledged. The third is the brownout test, which is typed as done. Each condition shows a check or a dash, its title and a sentence saying why, and the header of the gate counts how many are met.

Why can't I press Confirm sunset?

It can be pressed, but while any condition is open it only answers in the status line how many remain. The button is marked unavailable to assistive technology instead of being removed from the tab order, so keyboard users hear the reason. Once the gate passes, it confirms in this page only; flipping a switch afterwards takes the confirmation back.

What stays local, and how do I wire it for real?

Everything: no consumer is migrated, notified or switched off. Notify consumers only logs how many it would reach. To make it real, read last-call dates and volumes from your gateway logs, record acknowledgements from your consumer contacts, and have Confirm sunset schedule the shutdown.

How does it look on a phone?

Each consumer is a two-line row with its switch at the end of the first line, the gate sits under the list, and the action foot stays pinned so Confirm sunset and its reason are always in reach.

  • Pro

    A month's 10M-call quota as a segmented bar by consumer and a running total against an even pace, with the projected run-out day and a cap field per consumer that moves it.

  • Pro

    Eight endpoints against six probe locations as a matrix of pass, slow and fail cells, with a slider for how many locations must fail before an endpoint counts as down, and a reading for the chosen one.

  • Pro

    Nine endpoints ranked by p50, p95 or p99 with a range bar on one 0 to 1,000 ms scale, an SLO slider that marks the ones over it, and a histogram of the chosen endpoint's requests.

  • Pro

    A heatmap of eight endpoints by the last 12 hours in a five-step ramp with the average ms in each cell, an SLA slider that rings the cells over it, and a list of the slow endpoints with their trend.

  • Pro

    Errors per hour as a row of 24 selectable columns with a line at 60 an hour, the chosen hour's six error groups ranked by count with a Mute and Undo for each, and a sample stack trace for the group you pick.

  • Pro

    A day of gateway calls as 24 stacked hourly columns by status family, a toggle to show any combination of 2xx, 3xx, 4xx and 5xx, totals with the change on yesterday, and the top endpoints for the families on.