Glossary

The vocabulary of business applications, without jargon

Business application, no-code, deterministic generation, CRUD, code ownership: the terms that come up when you want a management tool — defined simply, with what they imply for you.

Business application

A software application built around the concepts, rules and vocabulary of a specific activity: a contractor's job sites, an association's members, a maintenance company's work orders. Unlike generic tools (spreadsheets, office suites), a business application structures data — everything has its record, its links, its status — and automates the useful views: filtered lists, dashboards, histories.

Blueprint Maker generates complete business applications from a natural-language description: database, management screens, dashboard and demo data.

See also CRUD · Entity · Dashboard (KPI) · See the use cases

No-code

A family of tools for building applications without writing code, by visually assembling blocks (forms, tables, automations). No-code excels at fast prototyping, but the application remains executed BY the platform: data and logic live with the vendor, the subscription is permanent, and the builder's limits become the application's limits.

Code generation takes the opposite path: the tool produces an autonomous application whose source code exists, exports and is owned.

Low-code

An intermediate approach between no-code and classic development: a visual platform generates most of the application, and developers complete specific parts with code. Low-code targets enterprise IT teams more than independents; it reduces development time but keeps the platform dependency and its licence cost.

AI application generation

Automatically producing a software application from an intention expressed in natural language. Two schools coexist: direct generation, where an AI model writes all the code — fast but unpredictable — and deterministic generation, where AI is limited to understanding the need and producing a specification, the code then being written by classic, reproducible programs.

Blueprint Maker belongs to the second school: that's what guarantees every generated application works — real screens, consistent data, accurate dashboard.

Vibe coding

The practice of having a conversational AI write code by describing the desired result and iterating through successive touch-ups without reading the produced code. Effective for exploring and prototyping, vibe coding produces applications whose internal structure nobody — not even the author — knows: maintenance and reliability inherit that.

Deterministic generation differs: the application's structure is explicit (a validated specification), and the produced code is the same at every generation for the same specification.

AppSpec (application specification)

A structured document describing an application to generate: its entities (the things being tracked), their fields and relations, its screens, statuses and indicators. In Blueprint Maker, AI turns your description into an AppSpec — the plan you validate before generation — then deterministic builders turn the AppSpec into code.

The AppSpec is the boundary between understanding and execution: AI stops at the specification; the code is written by reproducible programs.

Deterministic generation

The property of a generation system whose output is entirely determined by its input: the same specification always produces the same code. Concretely, no screen is “invented” at generation time: what gets built is what the plan announced, and the interface components are correct by construction.

That's the fundamental difference between Blueprint Maker and tools that have an AI model write all the code on every request.

Entity

A category of things an application tracks: Client, Project, Item, Member, Work order. Each entity has fields (name, date, amount, status…) and relations to other entities — a project belongs to a client, a work order concerns a piece of equipment. Identifying entities and their relations is the core of designing a management application; it's precisely what Blueprint Maker derives from your description.

Relation (database)

A structural link between two entities: “a client HAS several projects”, “a work order CONCERNS a piece of equipment”. Relations are what distinguishes a database from a pile of spreadsheets: they guarantee a client record shows all its projects, with no duplicates or copy-paste. In an application generated by Blueprint Maker, described relations become real navigation links between records.

Relational database

A storage system organising data into interlinked tables with integrity rules: you can't have a work order attached to a client that doesn't exist. It has been the standard of management computing for forty years — reliable, queryable, durable. Applications generated by Blueprint Maker rest on a relational database (via Prisma), not on free-form documents.

CRUD

Acronym for Create, Read, Update, Delete: the four basic operations on data — create a record, view it, edit it, delete it. A “CRUD interface” means the screens enabling those operations: lists, detail records, forms. It's the foundation of any management application; Blueprint Maker generates them automatically for every described entity, with search, sort and filters.

Dashboard (KPI)

A summary screen aggregating the application's data into steering indicators (KPIs): active projects, amount to invoice, members up to date, items below threshold. A good dashboard is computed directly on the database — never estimated. In applications generated by Blueprint Maker, indicators derive from your description and are computed by deterministically generated code.

Demo data (seed)

A realistic dataset installed with a new application to make it immediately evaluable: plausible clients, several months of history, varied statuses. Without a seed, a new application is just a shell of empty screens — impossible to judge a list, a filter or a dashboard. Every application generated by Blueprint Maker arrives with a narrative seed consistent with your trade.

Code ownership

The ability to retrieve, host and modify your application's source code without anyone's permission. It's the structural protection against vendor lock-in: if the vendor disappears, raises prices or changes terms, the application keeps existing elsewhere. Blueprint Maker delivers ownership by construction: full code ZIP export, GitHub push, free hosting.

ZIP export / GitHub push

The two exit paths of a generated application: the ZIP archive contains the entire source code (database, API, screens, configuration) ready to install elsewhere; the GitHub push places that same code in your repository, ready for teamwork and continuous evolution. Both are available for every application generated by Blueprint Maker.

SaaS (Software as a Service)

A distribution model where software is used online, by subscription, with nothing to install. Nearly all modern management software is SaaS — with a flip side: the data and the tool stay with the vendor. An application generated by Blueprint Maker is used like SaaS (dedicated URL, nothing to install) but escapes the flip side: its code exports and hosts freely.

Custom software

Software developed specifically for one organisation, as opposed to off-the-shelf software sold identically to everyone. Historically reserved for structures able to invest tens of thousands of euros, custom software becomes accessible through generation: Blueprint Maker produces an application specific to your activity for the cost of a subscription, with the code owned.

Next.js

An open-source web framework built on React, among the most used in the world for modern web applications. Applications generated by Blueprint Maker are standard Next.js applications: any web developer can read, host and evolve them — a guarantee of durability and independence.

Prisma

An open-source tool linking an application's code to its relational database: it describes the schema (entities, fields, relations) in a readable format and guarantees typed, safe data access. Applications generated by Blueprint Maker use Prisma — their data schema is explicit, versionable and understandable by any developer.

Hosting / dedicated URL

Any web application must be hosted somewhere to be reachable. Blueprint Maker deploys every generated application to a dedicated URL, immediately usable — and since the code exports, you can take hosting into your own hands at any time: company server, local host, cloud platform. The included URL is a convenience, not a tether.

Generation levels (Sketch, Craft, Masterpiece)

The three finish levels of a Blueprint Maker generation. Sketch quickly produces a working application to validate the structure; Craft refines screens and indicators; Masterpiece pushes visual and functional polish to the level of a daily production tool. Each level's credit cost is displayed before generating.

Theory is simpler in practice

Try for free See the use cases