It's a complete application, not a mockup: a real PostgreSQL database (via Prisma), API routes that create, read, update and delete data, authentication, and an interface that READS and WRITES to that database. Before delivery, every application goes through automated validation: it must compile, start as it would in production, and let a browser click through every section — not just “look like” it works.
Mockup and application: what actually separates them
A mockup shows an interface: screens that look like this or that, often with data hard-coded in the source or a handful of examples that don't survive a page reload. It's useful for discussing a project; it doesn't persist anything, and it doesn't compute anything.
An application, on the other hand, persists: what you create is still there the next day, in a real database, and what you edit ripples out everywhere it's displayed. Blueprint Maker generates the second kind, systematically: a Prisma schema, a dedicated PostgreSQL database, API routes for every entity, an interface that reads those routes instead of showing hard-coded values.
The proof: automated validation before delivery
What this page claims only matters if it's checked, not just written. So every generated application goes through a runtime validation step before it's delivered: the code is extracted, the application is built as it would be in production, started on a real server, and an automated browser then clicks through every section of the navigation to confirm it renders without error.
This step isn't a cosmetic check on the source code: it runs the application exactly as a visitor would, against an isolated database dedicated to validation. An application that doesn't compile, doesn't start, or crashes when a section opens isn't shipped as-is.
What that means for you, concretely
The application arrives with realistic demo data so you can evaluate it right away, but nothing is fixed: create a record, edit it, delete it, and the real database keeps track. The dashboard doesn't show numbers written in advance: its indicators are computed by querying the database every time it renders.
And because it's standard code (Next.js, Prisma, TypeScript) rather than a proprietary black box, it exports: as a ZIP archive or a GitHub push, so you can host it wherever you want and evolve it like any software project.