ObjectUI
Apps and dashboards as projections of business metadata
ObjectUI is the View Layer of ObjectStack. Apps, views, dashboards, and actions are declared as presentation metadata next to your Zod-defined business objects. The runtime renders them with React + Tailwind + Shadcn — permission-aware, versioned, and consistent with what AI agents see through the same MCP tools.
View as Metadata
You declare the view (metadata). The runtime renders it (React) — and agents see the same structure via MCP.
{
"type": "dataTable",
"object": "users",
"columns": [
{ "field": "name", "sortable": true },
{ "field": "email", "sortable": true },
{ "field": "role", "filterable": true }
],
"actions": [
{ "label": "Edit", "type": "navigate", "route": "/users/:id/edit" },
{ "label": "Delete", "type": "confirm", "variant": "destructive" }
],
"pagination": true,
"search": true
}Why ObjectUI?
A single source of truth for what users see and what agents touch.
Modern Stack, Not a Black Box
Rendered with React, Radix primitives (Shadcn UI), and native Tailwind CSS. Override styles, register your own components, ship production-grade interfaces that match your design system.
View Metadata, Not Frozen Frontends
Layouts, fields, validation, and actions are metadata served by the Control Layer. Ship UI changes without redeploying the frontend. Roll back a misbehaving view the same way you'd roll back a schema.
Patterns You Stop Rewriting
Data tables, multi-step forms, kanban boards, approval inboxes, dashboards — declared once, rendered everywhere. The business meaning stays in metadata, not buried inside per-app components.
First-Class Custom Components
Register your own React components into the engine and use them in view metadata. ObjectUI is a foundation, not a cage. Custom widgets inherit the same validation, permissions, and audit as built-ins.
How It Works
View Metadata → Engine → Renderer — wired to the same Control Layer that powers your APIs.
Step 1: View Metadata
A structured, versioned view definition. Type-safe, agent-readable, diffable like any other artifact.
Step 2: The Engine
ObjectUI's runtime hydrates state, validates input, resolves permissions, and triggers actions through ObjectOS — the same path agents take.
Step 3: The Renderer
React + Shadcn UI map view nodes to accessible, responsive components. Beautiful, consistent interfaces rendered from declarative metadata.
Use Cases
From admin panels to AI-operated dashboards.
Admin Surfaces & Internal Tools
Render complete CRUD and review interfaces from the same Zod-defined objects that back your APIs. Junior engineers and AI agents read from the same metadata — UI drift becomes impossible.
Dynamic Forms & Approval Flows
Multi-step wizards, conditional logic, and validation are metadata, not bespoke state machines. Forms surface the same business actions exposed to agents as MCP tools — same rules, same audit.
Data-Heavy Operator Consoles
Virtualized tables, dashboards, and analytics views that scale to millions of rows. Operators and agentic copilots share a consistent, permissioned view of the business.
Production-Grade Extensibility
ObjectUI is a foundation you build on, not a cage.
Register custom React components into the engine and reference them from view metadata. Custom widgets inherit validation, permissions, and audit from the same Zod-defined business objects.
// 1. Register your custom component
import { SignaturePad } from '@/components/custom';
objectUI.registerComponent('signaturePad', SignaturePad);
// 2. Use it in your view metadata
{
"type": "form",
"object": "contracts",
"fields": [
{ "name": "counterparty", "type": "text" },
{
"name": "signature",
"type": "signaturePad", // your custom component
"label": "Please sign here",
"required": true
}
]
}
// 3. It just works
// ✓ Validation comes from the Zod object
// ✓ Permissions enforced by the kernel
// ✓ Same surface exposed to agents via MCPPart of ObjectStack
The View Layer of an AI-native business backend.
ObjectUI works against any backend that speaks the protocol, but it is designed to pair with ObjectQL (Data) and ObjectOS (Control). Together they form a stack where humans and AI agents operate the same business through the same metadata.
Standalone
Works against any ObjectStack-compatible backend
Integrated
Pairs natively with ObjectQL + ObjectOS for an end-to-end agent-ready surface
Define Your Business Once.
Let Humans And Agents Operate It Safely.
Stop scattering business logic across SQL, JavaScript, and UI state. Make objects, permissions, workflows, APIs, UI metadata, and agent tools one structured Zod source of truth — analyzable, versioned, and auditable end to end. Launch July 2026.