Architecture
Clean core, controlled expansion
The core remains single-vendor; complex business models live behind plugin boundaries. That keeps performance and the sales story clean.
Technical layers
Next.js Front
Storefront and customer portal are localized, API-backed and SEO-focused.
NestJS API
Auth, licensing, releases, CMS, sales and support services are separated with clear modül boundaries.
PostgreSQL
Product, customer, order, license, domain and CMS data live in persistent storage.
Operations
The admin panel is the trust screen of the product
During the demo, buyers should see not only the storefront but the real operations panel they will use.
Architecture decisions
Why plugin boundaries?
Because not every customer needs multi-vendor, affiliate or subscription logic. A lean core improves speed and maintainability.
Where does license verification live?
Stilgen Hub manages license keys and domain activations; front and customer portal read this data from the API.