Liberty Next
Liberty Next is a connector-driven low-code framework. The principle is simple: configuration describes the data sources, the framework discovers the rest at runtime. A SQL connector is a few lines of TOML pointing at a database pool and a list of queries; 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.
Two paid applications ship on Liberty Next:
- Nomasx-1 — enterprise security and compliance. Centralised view of users and roles, Oracle and JD Edwards licence compliance, automated Segregation of Duties analysis. For auditors, security officers and licence managers.
- Nomajde — JD Edwards companion. Live screens on the JDE data: master data, security maintenance workbench, transactions, scheduled BIP reporting, live monitoring. For JDE operators, security administrators and ops engineers.
The framework itself (without the licensed connectors) is free.
Liberty Next is in active development. This documentation is being written alongside the framework — pages may still be sparse, screenshots may be ahead of the deployed build, and some sections are placeholders. The Framework section is the recommended entry point.
At a glance
POST /admin/reload rebuilds the registry; in-flight requests keep the version they started with.licensed = true connectors — that is what gates nomasx1 and nomajde.What it brings
| Area | What Liberty Next provides |
|---|---|
| Data sources | SQL pools (PostgreSQL, Oracle, SQLite) and HTTP API endpoints, declared in TOML under config/. |
| Schema discovery | Columns are read from the query's cursor at runtime; the dictionary adds labels, formats and display rules per column. |
| Screens | One Screen entry per business object: grid, modal form, per-field conditions, audit tab. |
| Dashboards | Charts and KPIs over the same named queries — bar, line, pie, stat panels. |
| Auth | TOML or database backend, JWT tokens, OIDC against any provider. |
| AI assistant | Anthropic-powered tool-use over the connectors, screens and dashboards configured on the instance. |
| Frontend | React 19 + Vite + TypeScript, single-page, dark default with light theme, EN / FR. |
Local development
python3.12 -m venv .venv
.venv/bin/pip install -e ".[dev]"
./start.sh init-config # copy config/*.toml.example → real (uncommitted) files
./start.sh init-db # FIRST RUN: create the auth store + an `admin` user
./start.sh # build frontend if stale, then run FastAPI on :8000
./start.sh dev # same, with auto-reload
./start.sh frontend # Vite dev server on :5173 (HMR) — pair with `./start.sh api dev`
./start.sh help # all commands
The backend serves the built frontend (frontend/dist) at /; no copy step. A fresh checkout with no config/connectors.toml runs API-only — the framework pool is the only connector configured by default.
Environment knobs:
| Variable | Purpose |
|---|---|
LIBERTY_DB_URL | Framework pool (auth tables when [auth] backend = "db"). Defaults to a local SQLite file. |
LIBERTY_JWT_SECRET | Token signing key — ephemeral when unset. |
LIBERTY_MASTER_KEY | Crypto master key used to decrypt ENC: values in configuration. |
LIBERTY_LICENSE_KEY | RS256-signed JWT that unlocks licensed connectors (nomasx1 / nomajde). |
ANTHROPIC_API_KEY | Enables the in-app AI assistant. |
Config files support ${NAME} and ${NAME:-default} references.
Next steps
| Where to go | Why |
|---|---|
| Framework → Overview | Layered model: pools, connectors, dictionary, screens, dashboards, menus. |
| Framework → Connectors | Define a SQL or API connector in TOML — schema, params, writable gate. |
| Framework → Screens | Wrap a connector query in a Screen — grid, filters, modal form, audit. |
| Nomasx-1 overview | Enterprise security and compliance — users, roles, Oracle / JDE licence compliance, Segregation of Duties. |
| Nomajde overview | JD Edwards companion — master data, security maintenance, transactions, reporting, monitoring. |