Reference applications

Aegis and Cedarline are complete, deployable products—not component-gallery screens. Both consume the public ZUI packages, use a Go and SQLite host, enforce authorization on the server, and connect to Config Store, PDF Export, and Scheduled Delivery. Their workflows and visual systems deliberately differ so you can evaluate ZUI as an application platform rather than an industry-specific template.

Application	Industry and workflow	Demonstrates	Live app
Aegis Cold Chain Control Tower	Pharmaceutical distribution, temperature compliance, carrier performance, intervention, and quality review	Dense operational analytics, maps, exception queues, regional row scope, governed actions, and quality audit	Open Aegis
Cedarline Insurance — Claims Operations	Claim intake, evidence review, coverage analysis, reserves, settlement authority, correspondence, and compliance	Document-oriented case files, a custom evidence board, guided decisions, manager approvals, role-specific queues, and audit-ready reports	Open Cedarline

Every seeded account uses the password demo. The applications contain deterministic synthetic data only.

What is shared

Both applications use AppSpec for pages, resources, actions, policies, variables, theme, environments, and publish targets. The runtime registries compose @zuilib/apps, Charts, Data Grid, Workflows, AI, and Text Editor. Administrators use @zuilib/builder to edit and validate the same application document rendered to end users.

The Go hosts retain executable queries, credentials, sessions, row-level authorization, mutations, and audit records. They delegate versioned personal views, governed PDFs, and durable delivery schedules to ZUI Cloud without placing a service key in the browser.

Run locally

From the repository root:

pnpm install
pnpm --filter @zuilib/cloud browsers # once per machine

pnpm reference-apps:start
# Aegis:     http://127.0.0.1:8081
# Cedarline: http://127.0.0.1:8082

Deploy the hosted examples

The deployer targets the same GCE VM and nginx/certbot setup used by zuilib.com. It creates an isolated systemd service and persistent SQLite directory for each application, atomically switches releases, verifies /api/health, and rolls back a failed service start.

1. Copy deploy/env.production.example to deploy/.env.production.
2. Point aegis.zuilib.com, claims.zuilib.com, and cloud.zuilib.com at the VM.
3. Set the ZUI Cloud key and distinct scheduler generator secrets.
4. Deploy the shared service, the applications, and then the documentation:

./deploy/cloud/deploy
./deploy/reference-apps/deploy all
./deploy/deploy

Deploy or verify one application independently:

./deploy/reference-apps/deploy aegis
./deploy/reference-apps/deploy cedarline
./deploy/reference-apps/deploy --check all # local build/package validation only

Production domains are configurable with AEGIS_DOMAIN and CEDARLINE_DOMAIN. See the repository's deployment guide and each application's source for the complete operational contract: Aegis · Cedarline.