Configuration describes the data sources — the framework discovers the rest at runtime. A SQL or API connector is a few lines of TOML; the React UI then builds a typed grid, a filter row, a modal form and lookups from the columns the query actually returns. No schema duplication, no per-screen code.
How it works
Load the TOML config, expose its queries to a screen or a dashboard, and the framework renders everything else — grid, dialog, filters, auth, role pruning, export buttons, audit columns, the assistant and scheduled jobs.
The grammar
Everything the framework does composes from five primitives. Once you’ve read these five, the framework’s surface is essentially mapped.
A connection to a database — a SQLAlchemy URL plus credentials.
“How do I reach this data?”
A named set of queries or REST endpoints on top of a pool.
“What questions do I want to ask this source?”
A grid + edit dialog over a connector’s queries.
“How do I let a person look at this and edit it?”
A layout of KPIs and charts over the same queries.
“How do I summarise this for the headline view?”
The sidebar tree that organises screens and dashboards into an app.
“How do I make this navigable?”
Around the five sit the supporting layers: the dictionary for labels and formats, auth & roles for who-sees-what, Nomaflow for scheduled work, the AI assistant and Python plugins.
Schema-discovered, not schema-declared
Nothing about your data is duplicated in framework configuration. The connector knows the query; the database knows the columns. When a column changes, the UI reflects it on the next reload.
Use cases
CRUD over existing tables, role-gated, with a sensible default UX. From “I have a database” to “users are using it” in about a day.
KPIs and charts over named SQL queries. Shared filter bar, drill-down to grids, PDF export — no separate BI tool for the 80% case.
A modern UI over JD Edwards, SAP or NetSuite — users, security, BIP queue, master data. Gives operators a faster way to live in the ERP.
A UI on top of webhook receivers, scheduled syncs and ETL pipelines. Nomaflow runs the jobs; the framework renders the runs.
A scoped slice of an internal app exposed to outside users via OIDC. Row-level access, audit trail and file uploads, all framework-native.
Approve / reject / route — multi-step forms, status workflows, scheduled escalations. Form conditions handle the per-state UX.
The right tool when most of your screens are list-and-edit on top of a database, with sprinklings of dashboards, jobs and integrations — which describes the vast majority of internal applications.
Vendor applications
The framework itself is free and open-source. A license key (an RS256-signed JWT) unlocks the bundled vendor products that ship on top of it.
Enterprise security, Object Usage Tracking, Oracle & JD Edwards licence compliance and Segregation of Duties — one audit-ready platform.
Master data, security maintenance, transactions and BIP reporting on one searchable grid. SQL + AIS API, no fat-client ping-pong.
Bridge any ERP to the French e-invoicing reform — UBL generation, pre-submission validation, Plateforme Agréée routing and lifecycle tracking.
Under the hood
React 19 + Vite + TypeScript, built once and served static by the backend on the same port. Dark default with a light theme swap, react-i18next EN / FR, @tanstack/react-table for the grid, react-markdown for the assistant, Monaco for in-app editing. You don’t write any of it — the framework renders everything off the configuration.
Python 3.12, FastAPI, SQLAlchemy 2.0 async with asyncpg (PostgreSQL) and oracledb (Oracle, thin), the Anthropic SDK for the AI assistant, authlib for OIDC, Argon2 for hashing, AES-256-GCM field encryption, APScheduler for cron jobs, Socket.IO for live updates. One process, one port, no companion daemons.
Liberty Next is free and open-source. Try the live demo, read the docs, or deploy your own instance.
