Reldavona is a responsive React and TypeScript operations workspace for teams designing AI-agent products. It connects agent management, run inspection, human approvals, incident response, cost analysis, evaluations, guardrails, integrations, audit history, and settings across 17 directly addressable routes.

Included product

• 8 seeded agents with list, detail, create, edit, pause, enable, and local run-start workflows
• 36 seeded runs with search, filters, pagination, payloads, logs, traces, JSON export, and detail views
• 8 approval requests with risk filters, evidence, policy checks, mandatory decision notes, and history
• 6 incidents with severity filters, timelines, acknowledge, resolve, reopen, and linked retry workflows
• Cost and budget views, 12 evaluations, 6 guardrails, 8 integrations, CSV exports, and audit history
• Global workspace search, responsive grouped navigation, useful empty and not-found states, and deterministic reset
• Editable source, production build, tests, buyer previews, setup and customization guides, and dependency notices

Connected demo workflows

Create or edit an agent, start a local run, and open its new run record. Approve or reject a guarded action with a required note and see the linked run, history, overview, and audit log update. Acknowledge, resolve, reopen, or retry an incident and follow the newly linked run. Settings, currency, timezone, budget, guardrail, integration, and environment changes persist locally across views.

Technical stack

• React 19.2.8
• TypeScript 5.9.3
• Vite 7.3.6
• Tailwind CSS 4.3.3
• Recharts 3.10.1
• Lucide React 0.468.0

Node.js ^20.19.0 or >=22.12.0 and npm are required.

Important scope

Reldavona is a frontend source template with deterministic demo data. Zero backend is required to run the included experience. It does not include authentication, authorization, a database, API routes, live AI-provider calls, payment execution, ticket-system calls, webhooks, background jobs, production observability ingestion, a custom domain, or hosting. Visible operational actions mutate the local demo store or export local data; they do not execute the displayed external operation. Buyers connecting production systems must add their own backend, security model, credentials, remote-data validation, and provider adapters.