A deploy dashboard with live logs, built by Claude Code on Elements

A deploy dashboard with live logs, built by Claude Code on Elements

Deploy pipelines with streaming logs, production rollbacks, live service health, and charts of deploys per day, build time, success rate and time to recovery.

View the code on GitHub →

How it's built

Rolloutly needed deploy pipelines that stream their logs, production rollbacks, service health that refreshes itself, charts of a month of deploys and roles for the team. Each of those is a part of Elements, so the agent spent its 29 minutes on the dashboard itself.

  • Streaming deploys. A deploy is a job that walks each stage and sends every log line, stage change and final status on a channel. The deploy page prints the log as it runs, and the overview, service and activity pages pick up each status change.
  • Live service health. A one-line cron schedule runs a health job every minute that takes a reading every ten seconds and pushes it to every open screen on a second channel. A release that failed its health check stays degraded until a new deploy or a rollback replaces it.
  • Rollbacks. Rolling back checks that the chosen release ran in production and that nothing else is deploying, then sends it through the same pipeline as a deploy.
  • Charts from the data. The insights page computes deploys per day, build time, success rate and time to recovery in SQL and draws them as SVG, and refreshes when a deploy finishes.
  • Server calls as function calls. Starting a deploy, rolling back and managing the team call server functions straight from the page with @rpc.
  • Data and roles from SQL. Migrations define the platform and seed one admin, three engineers, twelve services and thirty days of deploy history with failures and rollbacks. Sessions and roles give admins the team page.

Why Elements

Elements is the integrated stack for building apps with AI: a TypeScript project server, build system, app framework and deployment system, engineered from the ground up as one. Your editor, tools and one or many agents all connect to the same always-on project server, which runs type checking, program analysis, migrations and tests as the agent builds. Built-in guardrails keep the app structured correctly and secure as it grows from prototype to production.

Run it yourself

Paste this into a terminal. It installs Elements, creates your copy of this app and starts it.

curl -fsSL 'https://elements.dev/install?create=rolloutly&scaffold=demo-rolloutly' | sh
View script