ASP.NET Core 8 · Blazor ServerPages run on the server and the browser shows the result over an always-open channel: the same "state + events" model as Windows programs, which is why porting from the desktop came naturally.
One database per shopSQL Server, same schema as the desktop. Each shop has its own database and sees only that; you enter the cloud from a desktop backup or from a clean archive.
The Control RoomA control database outside the shops' own: who may enter, with which licence, until when, on how many seats. Seats are counted as live circuits; the kill switch is immediate.
One code, two runtimesThe desktop's VB.NET classes live in MyShop.Core and compile for both worlds (net472 and net8.0): one fix serves both, and the "twin" test proves it on the numbers.
Two-level accessFirst the shop — code and shop password — then the user's card with their password, roles and permissions. PBKDF2 password hashing, secrets kept out of the package, ASP.NET data protection.
HTTPS, HSTS, headersAutomatically managed certificate, HSTS on, security headers checked from outside; the browser talks to the fiscal printer on the local network with the operator's explicit permission (Local Network Access).
OperationsWindows Server with IIS and SQL Server; nightly backups verified and restore-tested, a demo reset at 04:00, logs and a /salute health endpoint.
UpdatesOne release from our bench and every shop is updated together, behind ten seconds of courtesy page; the previous release is kept for rollback.
TestsSeventeen automated test benches — stock across the two runtimes, prices, synchronisation, e-invoicing, bills of materials, items, balancing, the fiscal printer — plus a scripted browser that drives the real pages like a cashier would.
For resellersResellers' shops live on our servers, with a reseller console to manage their own; their connectors get SQL access limited to the single database, never exposed to the world.
