Frontend Developer Toolkit

ObjectUI

Schema-driven React interfaces for serious frontend teams

ObjectUI is for frontend developers: render objects, forms, dashboards, pages, and plugin views from ObjectStack metadata while keeping React, Tailwind, Shadcn, custom routing, custom auth, and your own backend under your control. The same metadata also powers APIs and AI tools.

View as Metadata

Declare metadata; ObjectUI renders a real interface through the app shell and providers.

View Metadata
schema.json
{
  "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
}
Rendered ObjectUI Surface
A fully functional, permission-aware data table: • Shadcn UI components, beautiful by default • Sortable / filterable columns derived from object metadata • Row-level permissions: agents and humans see the same scope • Actions also exposed as MCP tools (user.edit, user.delete) • Pagination, global search, responsive layout • Accessible by default (ARIA, keyboard navigation) • Tailwind classes — fully customizable

Why ObjectUI?

A modular frontend toolkit: use the full Console when useful, or compose app-shell/provider packages inside your own React application.

Built for React Teams

Use familiar React primitives, Tailwind utilities, Radix/Shadcn components, and your existing design system. ObjectUI renders from metadata without trapping you in a black box.

Metadata Without Losing Control

Views, pages, dashboards, forms, fields, and actions can come from metadata, while routing, auth, layout boundaries, and component overrides stay in your frontend code.

Console or Embedded Shell

Run the complete ObjectStack Console, or embed @object-ui/app-shell and @object-ui/providers for a small custom interface connected to your REST, GraphQL, or ObjectOS backend.

Frontend Plugin Surface

Register custom fields, widgets, view types, and plugins such as kanban, calendar, charts, reports, maps, AI, and workflow views.

How It Works

Metadata -> providers -> app shell/renderers, with your own backend or ObjectOS.

Step 1: Metadata

Objects, views, dashboards, pages, fields, labels, and actions are structured definitions that can be loaded lazily and localized by convention.

Step 2: Providers

DataSourceProvider, MetadataProvider, and ThemeProvider bridge ObjectUI to ObjectOS or to your own REST/GraphQL/custom API.

Step 3: Renderers

AppShell, ObjectRenderer, DashboardRenderer, PageRenderer, and FormRenderer map metadata to accessible React components.

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.

Extensibility

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.

Custom Component Example
custom-component.tsx
// 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 MCP
Ecosystem

Part of ObjectStack

The View Layer of an AI-native business backend.

ObjectUI works independently with any backend via providers, but it aligns naturally with ObjectOS and ObjectStack metadata. ObjectQL is only the data engine behind some of those objects, not a requirement for every UI integration.

Standalone

BYO backend with @object-ui/app-shell + @object-ui/providers

Integrated

Full ObjectOS Console and ObjectStack metadata integration

Early Access Program

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.

No commitment required
Priority access for technical teams
Beta starts April 2026