BSBV SaaS Core
Control plane for sellable tenant software.
Build a commercial SaaS offer without mixing Core, marketplace, module runtime and tenant business truth. Core controls what can be bought and activated; tenant runtime delivers the customer application.
One path. Three responsibilities. No mixed runtime story.
The homepage must route users into the correct next surface instead of explaining the same overview repeatedly.
Define the sellable platform truth.
Packages, licenses, domains, accounts, billing, plugins and module availability stay governed in Core before any tenant runtime starts.
Let buyers choose concrete products.
Modules, plugins and runtime templates are presented as purchasable catalog items with details, demos, prices and activation paths.
Activate the customer application separately.
Tenant databases, module journeys, themes and operational business data stay outside the Core customer journey.
Start with the thing the customer can buy.
The catalog is the decision surface. It separates commercial products from technical extensions and runtime templates.
Business products
Industry-ready engines like SolarCalcPRO with frontend demo, backend demo, own data model and purchasable package scope.
Technical extensions
Reusable capabilities such as API keys, consent, tag management and runtime services with explicit dependency contracts.
Runtime page systems
Frontend and backend page suites generated from the shared UI truth and bundled with compatible modules or sold separately.
Move from platform promise to product selection.
Open the marketplace when you want modules, plugins and templates. Use the architecture call when rollout, licensing or tenant boundaries need to be clarified first.