Schema-driven. Event-first. Generator-first.
Zex is an AI-native framework for teams who want the ergonomics of Laravel, the deploy model of Go, multi-frontend generation across Svelte, Vue, and React, and a machine-readable architecture that makes modern LLM tooling genuinely useful.
zex new crm --db postgres --frontend vue cd crm zex make:auth zex make:crud customers zex make:crud invoices zex dev
Core ideas
The product goal is not just faster scaffolding. It is a system where generation, observability, and customization all reinforce each other.
Spin up auth, CRUD, admin, search, billing, galleries, dashboards, and mobile shells through a CLI that removes repetitive work instead of pretending boilerplate is productivity.
Framework metadata lives in machine-readable files so assistants, analyzers, and platform tooling can reason about the real project graph instead of guessing hidden conventions.
Every unit of business logic becomes a discrete action with validation, policy checks, transactions, events, and response handling in one predictable slice.
Zex is designed to ship with CSRF protection, rate limiting, request limits, secure cookies, audit logs, file validation, and policy-first access patterns without bespoke patchwork.
Keep the deploy story simple: SQL-first persistence, a predictable Go runtime, optional infrastructure, and a backend that can ship as one binary when the project is ready.
Observe how actions emit events, trigger jobs, and call tools through an action graph built for debugging, system design, and AI-assisted reasoning.
Workflow
Zex is designed to keep repetitive work automated while preserving clear ownership over the last mile of behavior and design.
Comparison
Zex borrows the parts teams love, then adds a machine-readable project model and action-graph observability that most stacks still treat as optional.
| Capability | Zex | Laravel | PocketBase | Raw Go stack |
|---|---|---|---|---|
| One-command full-stack bootstrap | Designed for instant full-stack project setup | Strong CLI scaffolding | Simple starter setup | Manual composition |
| Machine-readable framework brain | First-class metadata files for AI tooling | Mostly convention based | Limited project metadata | Custom implementation required |
| Action graph observability | Built into the architecture | Requires packages and custom design | Minimal by default | Build it yourself |
| Single binary backend deploy | Core positioning | Not native | Native | Native |
| Multi-frontend generation from one spec | Svelte, Vue, React, Capacitor from one contract | Separate ecosystems | Admin-oriented UI only | Custom build pipeline |
| Secure defaults with audit-first workflows | Policy, audit, tool permission model | Possible with ecosystem packages | Basic defaults | Depends on team discipline |
Gallery
These self-contained visuals sketch the operating model: schema studio, generated admin, action graph, mobile shell, and the framework brain behind them.
The system view: schema, actions, tools, routes, and the metadata layer that keeps everything synchronized.
A preview of the generator-first admin surface with audit, jobs, events, and model management.
Visual traces for business flows, emitted events, async jobs, approvals, and tool calls.
Pages, tables, forms, and galleries all sourced from a shared UI contract and token system.
Use the same contracts to spin up a Capacitor-based mobile shell without rebuilding the product model.
Docs and examples
The docs explain the first-class primitives, schema-driven generation, action flow, tools and MCP, deploy model, and how the framework brain keeps humans and assistants aligned.
Open source and sustainability
The site includes a Stripe-ready donation flow for teams who want to support framework development while the framework roadmap moves from architecture to implementation.
Blog
Three launch articles are included to support SEO, explain the product direction, and give the framework a stronger voice than a typical placeholder landing page.
Conventions are helpful, but LLM tooling needs explicit project metadata to reason accurately. Zex treats that metadata as a first-class part of the architecture.
Read article Controllers are often too coarse for modern products. Zex treats actions as the real business primitive so logic, permissions, and events stay visible.
Read article Most full-stack products repeat the same patterns. The opportunity is not to romanticize manual setup, but to build a safer boundary between generated scaffolding and custom product work.
Read articleFAQ
The messaging keeps the ambition high while staying honest about what is already defined versus what still belongs to the roadmap.
Zex is presented as a real framework direction with a defined CLI, architecture, and product scope. The site stays honest about roadmap items while treating the framework as something meant to be built and adopted.
Because teams usually have to choose between performance, frontend flexibility, and developer ergonomics. Zex is built around the idea that they should reinforce each other instead of competing.
The framework keeps a machine-readable model of itself. That means LLMs can inspect models, actions, tools, routes, and event graphs as explicit data instead of inferring everything from naming convention and folder luck.