A SaaS blueprint describes everything needed to stand up a working product: the modules and their fields, the pages and their layouts, the menus, the data connectors and bindings, the user types, and the theme. Installing one gives you a functioning application on day one, which you then make yours.
The business objects your product is about, with types, validation, and relationships already defined.
Screens bound to those modules, arranged and ready, rather than blank canvases you populate by hand.
Navigation that differs by role, so an administrator and a field technician do not see the same product.
The wiring between what a component displays and where that data comes from.
Colours, typography, and spacing as variables you override once rather than editing every screen.
The automation the product needs to be useful, not just the screens it needs to look complete.
Blueprints move through draft, published, and archived. Archived versions remain installable by existing buyers even after a newer version supersedes them — because a customer who purchased version two should not be forced onto version three to reinstall.
When an application is provisioned from a blueprint, the exact version used is recorded. That means a support conversation eighteen months later can establish precisely what was installed, and a re-provision produces the same result rather than whatever is current.
Anything you build can become a blueprint. If you have solved a vertical well once — a compliance workflow for clinics, a dispatch system for field service — you can package it, version it, and either reuse it across your own clients or publish it for sale.
Extensively. The blueprint is a starting point, not a constraint. Pages, modules, fields, workflows, and theme are all editable afterwards.
Yes. That is the intended path for agencies who have solved the same problem for several clients.
Install it as many times as you like. Each installation is a separate application with its own databases and container.
Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.
No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.
Get started free Read the docs