No. What is billed is generation: your plan sets what you can produce in a month, never how many people then use the application. It arrives with its own accounts and two roles (administrator and read-only), which you create from within the application. There is no seat counter to watch. The only real limit is hosting, not a licence.
What is counted, and what is not
Per-seat pricing is the norm in business software: every person added costs money, which pushes teams to share a login, to delay bringing a colleague in, or to choose a tool on a criterion that has nothing to do with the work. That question does not arise here, because that is not what is being sold.
Blueprint Maker bills GENERATION. The Discovery plan is free, Pro is €25/month, Max is €149/month, and what they bound is what you produce: the cost of each generation is shown before you launch it. Once the application is delivered, it is yours, and nobody counts who opens it.
The practical consequence is easy to check: adding the workshop's sixth person does not change your bill, because no line measures them.
Accounts and the two roles
Except for deliberately public applications, every generated application ships with its own authentication: a login page, its own accounts, passwords stored hashed, and an administrator account created at the start. You add the others from within the application, without asking us for anything.
There are two roles. The administrator sees and edits everything. The read-only role can consult but cannot create, edit or delete. The part that matters: that restriction is enforced ON THE SERVER, on every API call, not merely by hiding buttons in the interface. A hidden button is a courtesy; a server rule is a guarantee.
On top of that come the ordinary needs of a small team: disabling an account when someone leaves, or forcing a password change at first login.
- Accounts created from within the application, with no involvement from us
- Administrator role: read and write
- Read-only role: consultation, writes refused server-side
- Disabling an account without deleting it
- Password change enforced at first login
The only limit that really exists
The bounded part has to be named, otherwise the answer would be too good. The demonstration address provided with an application has a duration tied to the plan: 48 hours on Discovery, 7 days on Pro, 14 days on Max. That is a hosting window, not a user quota, and it does not depend on how many people log in during that time.
Beyond it, the application remains yours: the code is exportable as a ZIP or pushed to your GitHub, and you host it wherever you like. The ceiling then becomes your hosting and your database, which is a technical question rather than a commercial one: nobody will invoice you for an extra user on a server that is your own.
In other words, the question “how many users am I allowed” has no numeric answer, because no allowance is sold by the unit.