Skip to main content

Ship customizable software with React and AI

ZUI is an open-source system for building analytics views, internal applications, and reports from your own data and component vocabulary.

Start with a working interface. Add custom components, AI generation, user-specific customization, workflows, and governance only when your product needs them.

Choose your path​

I need to deliver analytics​

Build a responsive view with shared filters, KPIs, charts, and a data grid. Your application supplies rows and actions; ZUI supplies the reusable interface behavior.

Ship the analytics view →

I want a coding agent to build it​

Give Codex, Claude Code, or another coding agent a focused, maintained task prompt. It will use the correct packages, derive the view from your data contract, and validate the result before returning it.

Build with a coding agent →

I am adding ZUI to an existing product​

Use @zuilib/apps as the core view system. Register only the built-in and domain components your product allows, then render a JSON-safe ViewSpec against data and action handlers owned by your host application.

Understand Apps and views →

I want to evaluate complete enterprise applications​

Compare a pharmaceutical cold-chain control tower with an insurance claims back office. Both are deployable, role-aware applications built from the same ZUI packages and ZUI Cloud contracts.

Explore the reference applications →

The core loop​

Your data, actions, and components
↓
Registry + AI context
↓
ViewSpec / AppSpec
↙ ↘
React interface ZUI Cloud
↑
Human and AI patches
  1. Describe your data. One DatasetSchema drives filters, metrics, charts, grids, field pickers, validation, and model context.
  2. Define the vocabulary. The registry contains ZUI components and your own domain components. Rendering, editing, and generation share it.
  3. Create the view. Write the ViewSpec directly or let an LLM generate it from the registry's prompt and JSON Schema.
  4. Refine safely. Human and AI changes become minimal, reviewable, undoable patches rather than regenerated application code.
  5. Ship it. Render the view in React, persist it for each user, compose it into an application, save it through Config Store, or export it through PDF Export, or deliver it on a durable schedule.

What stays yours​

ZUI does not fetch from your backend or choose a model provider. Your application owns credentials, data access, business logic, routing, actions, policies, persistence, and model calls. The open-source library owns the interface contracts and reusable components between them.

Open-source library and managed service​

The components, view system, builder, workflow surfaces, AI interfaces, and tooling are the open-source ZUI project. ZUI Cloud is the optional Cloud or Cloud Private service layer: Config Store persists immutable app/view versions, PDF Export renders the same validated view and theme, and Scheduled Delivery records every recurring artifact and target outcome. Use the managed service or follow the Cloud Private operations runbook when your platform team must operate its data plane.

Explore by outcome​

You needStart here
Filters, metrics, charts, and tablesAnalytics quickstart
Customizable or AI-generated screensViews in Apps
Pages, resources, actions, and policiesApp runtime
Complete multi-role enterprise examplesReference applications
Approvals, tasks, audit, and writebackWorkflows
An embedded authoring experienceBuilder
Assistant UI inside your productAI interfaces
Individually installed UI controlsPrimitives
Package names and entry pointsPackage reference