DocsSupportPricing
Roadmap (has updates coming soon)XFigma3.7K
Sign inGet All-Access
Categories
Dev Ops6
  • Cron Jobs
  • Infra Audit Log
  • Deployments
  • Firewall Rules
  • SLO Error Budgets
  • Data Connections
AI Ops9
CRM9
Agents10
Analytics9
Billing9
Bookings3
Files1
Inventory11
Users7
Digital TwinNew Digital Twin category with 2 interactive 3D blocks2

For AI Agents

Hand your agent this brief or the ReUI MCP, not a screenshot. Installs with a ReUI Pro or Ultimate license.

When to use

  • Platform and SRE consoles for cron jobs, releases, audit trails, SLOs, edge firewalls and data sources
  • On call triage of failing jobs, failed deploys, denied access, blocked requests and burning error budgets
  • Operator changes made in place: pausing a job, promoting or rolling back, editing rules, rotating credentials

When not to use

  • A single table on your own columns, with no charts, lanes or ops panels around it: use the Data Grid component
  • A table section for business records such as tickets, contacts, deals or timesheets: use the Base blocks
  • Only the record detail panel that slides over a list, without the console page: use the Sheet blocks

Agent notes

  • Every block pins now to Sep 29, 2026 14:20 UTC in REFERENCE_MS, set from REFERENCE_DATE in the audit log, and never reads the wall clock; pass your own now
  • Writes only update client state and answer with a sonner toast; no block calls a server, so add your API at each write point
  • Both page.tsx and each root set min-h-svh, and the root caps width at 1320px with its own padding; drop both inside an app shell

Third-party API docs

  • TanStack Table v9: API reference, docs, used by 6 of 6 blocks
  • Sonner v2: API reference, docs, used by 6 of 6 blocks
  • Recharts v3: API reference, docs, used by 5 of 6 blocks
  • Shiki v4: API reference, docs, used by 4 of 6 blocks
  • dnd kit v6: API reference, docs, used by 1 of 6 blocks (these are the Legacy docs; dndkit.com's default docs cover the newer @dnd-kit/react, a different API)
  • Motion v12: API reference, docs, used by 1 of 6 blocks (the docs follow the latest Motion, with no React API break since v12)
Markdownhttps://web.dev.reui.io/blocks/solutions/dev-ops.md
MCPsearch({ query: "dev ops", type: "block", category: "dev-ops" })
Full index for agents:llms.txtReUI MCP setup

Shadcn Dev Ops Blocks: 6 Consoles for One Production Platform

This is not a set of status widgets. The 6 blocks are a console for each job a platform or SRE team runs every day: a cron jobs console to keep scheduled work on time, a deployments console to promote and roll back releases, an edge firewall to decide which requests get through, an SLO console to spend the error budget on purpose, an audit log to prove who changed what, and a connections page for the data sources everything reads.

All 6 share one sample platform: the same services, environments, people and ids. Deploy DEP-4127, the payments-api canary in the deployments console, is a promote event in the audit log, the payouts-scheduler rollback DEP-4107 is a budget event on the SLO burn-down, and the connections page lists which cron jobs and SLOs read each dataset. Every count and timestamp derives from a fixed reference date rather than the wall clock.

All of it is React and Tailwind source installed through the shadcn CLI, built on ReUI DataGrid, Filters, Frame, Code Block, Badge, Stepper and Timeline with shadcn Sheet, Chart, Switch and AlertDialog.

All Dev Ops Blocks

Open any block on its own page for a live preview, the components it is built from, and the install command.

  • Cron Jobs Dev Ops Cron Jobs Console with Run History Bars, Cron Editor and Job Detail Sheet
  • Infra Audit Log Dev Ops Infrastructure Audit Log with Outcome Volume Chart, Saved Views and Diff Sheet
  • Deployments Dev Ops Deployments Console with Promotion Lanes, Live Canary Rollout and Release Sheet
  • Firewall Rules Dev Ops Edge Firewall Console with Ordered Rules, IP Lists, Protections and Traffic Log
  • SLO Error Budgets Dev Ops SLO Console with Error Budget Burn-Down, Burn Rate Alerts and Objective Sheet
  • Data Connections Dev Ops Data Connections Settings with Linked Datasets, Masked Data Preview and Sync Activity

The 6 Consoles and What Each One Does

Scheduled work lives in the cron jobs console. Each row carries an enable Switch and its last 20 runs as a toned bar strip, tabs split Healthy, Failing and Paused jobs, and the selection bar runs, pauses, resumes or deletes in bulk. The job sheet steps through jobs with Overview, Runs and Settings tabs: each run's log in a Code Block, and a cron editor with presets, a plain English reading of the expression and the next 3 fire times.

Shipping happens in the deployments console. Staging, Sandbox and Production lanes show every service's version and promote a release forward, a canary rollout advances live through its stages to a gate that waits for Promote, and the Deploy History grid filters by service, environment, strategy, author and cluster. The deploy sheet has Pipeline, Logs, Health and Changes tabs: a streaming log you can follow, error rate and latency against the baseline, the commits in the release, and roll back behind a confirm.

The edge is the firewall console. Rules are rows you drag into priority order and edit with a Filters condition builder that previews which recent requests a rule would match. Managed WAF, bot defense, rate limiting, minimum TLS and an Under Attack mode sit beside IP allow and block lists, every request in the live log opens a trace of how it got its verdict, and Test Request runs a request through the same rules.

Reliability is the SLO console. KPI tiles lead into an error budget burn-down where each day is a lollipop and a drag sums the budget those days spent, and the objectives grid carries a rolling budget and burn alerts per SLO, with mute and unmute in bulk. The SLO sheet has Overview, Burn Rate, Events and Settings tabs, with burn rates over 1 hour, 6 hour and 3 day windows, incidents you can exclude from the budget, and Copy as OpenSLO.

Accountability is the audit log. An outcome-stacked volume chart scopes the grid to the time span you select, a denied attempts queue tracks which denials were reviewed, and the event grid has saved views, chip filters, bulk mark reviewed and CSV or JSON export. The event sheet steps through Details, Changes, Raw and Related tabs: a before and after diff, the raw JSON payload, and the events that share its request or session on a Timeline.

Data sources are the connections page. Stat cards, an hourly sync activity chart and a needs attention list sit over one grid each for databases, warehouses, apps and files, across 11 integrations from Neon and BigQuery to Stripe and Google Drive. The connection sheet links datasets, previews sample rows or the schema with personal data masked, and rotates a failing credential, and New Connection is a 3 step Stepper with a connection test before you pick datasets.

Sized for a Platform Team, Not an Observability Vendor

These are the screens a platform team opens, at the density it works at. There is no scheduler, CI runner, metrics store or edge proxy behind them: jobs, deploys, audit events, firewall rules, SLOs and connections are typed local data, and the live parts, the canary rollout and the firewall's traffic log, run on a demo tick that a real event stream replaces.

What that buys you is a category you can read in an afternoon. Each block installs on its own and keeps its sample data in its own data file, so you can keep the deployments console, wire it to your pipeline, and delete the firewall without untangling anything.

Restyle and Rewire

  • One sample platform Services, environments, people and ids repeat across the 6 consoles, so a deploy, a job or an SLO reads the same wherever it shows up.
  • No wall clock Every count and timestamp derives from a fixed reference date, so previews, screenshots and tests render the same every time.
  • Undo on writes Each write fires one toast, changes carry Undo, and deletes and rollbacks confirm in an AlertDialog first.
  • 8 styles, 2 bases Install on Base UI or Radix in any of the 8 ReUI styles so the consoles inherit your existing radius, density, and color scale.

Related Shadcn Solutions Block Categories

  • Agents Blocks (10 blocks) Run queues, step traces and failure triage, the same operator patterns applied to autonomous agents.
  • AI Ops Blocks (9 blocks) Provider failover, feature flags and token spend ledgers for the AI layer running on the same platform.
  • Users Blocks (7 blocks) Roles, just-in-time access approvals and an access audit timeline for the people behind every change.
  • Analytics Blocks (9 blocks) Funnels, cohorts and alert rule settings for the product metrics that sit beside service health.
  • Billing Blocks (9 blocks) Metered usage audits and invoice ledgers, where the platform's usage turns into charges.

All Shadcn Block Groups

Browse the full ReUI Shadcn blocks library by product surface. Each group bundles category-level blocks you can mix and match across your project.

  • Shadcn Application Blocks (303) Browse 303 Shadcn Application blocks across 23 categories.
  • Shadcn Data Grid Blocks (47) Browse 47 Shadcn Data Grid blocks across 9 categories.
  • Shadcn Charts Blocks (52) Browse 52 Shadcn Charts blocks across 10 categories.
  • Shadcn Solutions Blocks (76) Browse 76 Shadcn Solutions blocks across 11 categories.
  • Shadcn AI & Agents Blocks (22) Browse 22 Shadcn AI & Agents blocks across 3 categories.
  • Shadcn eCommerce Blocks (87) Browse 87 Shadcn eCommerce blocks across 13 categories.
  • Shadcn Marketing Blocks (67) Browse 67 Shadcn Marketing blocks across 8 categories.

Frequently Asked Questions

Do these work with Kubernetes, Argo CD or GitHub Actions?

Yes, because the blocks are UI only. Jobs, deploys, audit events, firewall rules, SLOs and connections are typed local arrays you replace with data from your cluster, your CI or your provider APIs. Nothing imports an orchestrator or a monitoring SDK, so the cron jobs console can front Kubernetes CronJobs in one app and a plain jobs table in another.

Can I use just the deployments console on its own?

Yes. Each block installs independently through the shadcn CLI and pulls only the primitives it needs, so adding the deployments console brings in ReUI Data Grid, Filters, Code Block, Frame, Badge, Alert and Icon Tile, plus shadcn Sheet, Chart, Alert Dialog and the other shadcn primitives it uses. The blocks share sample ids for the demo, but no block imports another.

How do I connect the consoles to real data?

Replace the seed arrays in each block's data file with your own queries, and swap the fixed reference date for the current time. The grids, filters, charts and sheets stay as they are. The canary rollout and the firewall's live log run on a demo tick, and manual job runs, syncs and the connection test resolve on short demo timers. Those are where your event stream and API calls plug in.

Will the consoles match my existing shadcn app?

They are built on shadcn/ui primitives plus ReUI's free components, shipped in 8 styles across the Base UI and Radix bases, and themed from Tailwind design tokens. Status colors come from the success, warning and destructive tokens rather than chart hues, so a failing job or a blocked request reads the same in light and dark.

Start building with ReUI Pro today.

Every Pro block, every style, and every future addition, with one license for unlimited projects.

Get All-Access

From $249, once. Lifetime updates.

Application

  • App Shell
  • Auth
  • Card
  • Dashboard
  • Dialog
  • Empty State
  • Event Calendar
  • Flow
  • Form
  • Gantt
  • Kanban Board
  • List
  • Navbar
  • Onboarding
  • Profile
  • Rich Text Editor
  • Schedule
  • Settings
  • Sheet
  • Stats2 meter cards moved here from Charts, 17 in all
  • Timeline
  • Whiteboard
  • Wizard

Data Grid

  • Base
  • AdvancedAdded 2 new Data Grid Advanced blocks, 5 in all
  • Columns
  • Drag & Drop
  • Editing
  • Expansion
  • Filtering
  • Grouping
  • Virtualization

Charts

  • Area ChartAdded a new Inbound Leads area chart block
  • Bar Chart
  • Composed Chart
  • Line Chart
  • Pie Chart
  • Radial Chart
  • Sankey ChartNew Sankey Chart category with 3 flow chart blocks
  • Slope ChartNew Slope Chart category with 2 rank-shift chart blocks
  • Sparkline
  • Status Tracker

AI & Agents

  • AI Chat
  • Agent Activity
  • AI UsageNew AI Usage category with 2 spend blocks

Solutions

  • Dev Ops
  • AI Ops
  • CRM
  • Agents
  • Analytics
  • Billing
  • Bookings
  • Files
  • Inventory
  • Users
  • Digital TwinNew Digital Twin category with 2 interactive 3D blocks

Templates

  • All templates

eCommerce

  • Category Card
  • Checkout
  • Comparison
  • Coupon
  • Filter Sidebar
  • Product Card
  • Product Detail
  • Product Grid
  • Receipt
  • Review
  • Shopping Cart
  • Wishlist
  • Shop Hero

Marketing

  • Blog
  • Compare
  • Contact
  • CTA
  • FAQ
  • Hero
  • How It Works
  • Pricing

Resources

  • Components
  • Blocks
  • Icons
  • MCP for Agents
  • Docs
  • Support
  • Pricing
  • Tailwind Plus Alternative
  • Roadmap(has updates coming soon)
  • AffiliateSoon

Legal

  • Privacy Policy
  • Terms & Conditions
  • License
  • Refunds
  • Cookies

© 2026 ReUI. All rights reserved.

3.7K
  1. Blocks
  2. Solutions
  3. Dev Ops
Markdown

Shadcn Dev Ops Dashboard Blocks for Platform and SRE Teams

A console for each platform job: scheduled jobs, an audit trail, deploys with a live canary, an edge firewall, SLOs with error budgets, and data connections.