Architecture & technology
One self-contained deployment. Your servers. Your data.
The complete application — web site and API — installs as a standard ASP.NET Core site on your Windows server. There are no external services, no agents and no licensing servers in the data path.
The shape of it
any current browser — no client install
web app + stateless API (.NET 10)
configuration catalog: local SQLite file
Every screen (area) is bound to its own data source; areas on different servers and databases coexist in one application. The SQLite catalog holds configuration only — areas, columns, lookups, users, groups, menu, filters — and ships empty: your staff configures everything in-app.
Technology foundation
| Layer | Technology |
|---|---|
| Application runtime | .NET 10 (current long-term-support generation) |
| Web API | ASP.NET Core 10 — stateless REST/JSON, JWT bearer sessions |
| Web client | React 18 + TypeScript single-page application — browser-based, no client install |
| Configuration catalog | SQLite — one local file, trivial to back up or keep in source control |
| Business data access | Microsoft.Data.SqlClient 7.x → Microsoft SQL Server / Azure SQL |
| Logging | Serilog (structured) |
| Hosting | Windows Server + IIS — one site, one app pool, standard tooling |
Design principles you can verify
- Strict layer separation — core, domain, persistence, API and client are separate; business-data access sits behind a single interface, so alternative backends are implementations, not rewrites
- Per-area data-source resolution — each screen’s connection is resolved from its metadata at request time; that is what makes multi-server operation work
- No DDL, ever — the application is a guest in your database
- Fail-soft — a partial outage degrades gracefully instead of taking the application down
- Tested — an automated suite of 167 tests covers the core services, the data engine, search & filtering, permission enforcement, form layout validation and the admin APIs
Requirements
- Windows Server + IIS
- .NET 10 runtime
- One or more SQL Server / Azure SQL databases reachable from the application server (Windows or SQL authentication)
- Any current browser for your users
- That’s it — no client installs, no inbound firewall exceptions for the data path
Roadmap: a cloud service with local data (secure bridge, vendor-hosted platform, data on your premises) is being developed; the architecture above is the reference edition used today.