How this is built
The parts behind the screens, read live from the running system. Including the ones that are not finished — a provider that is not connected says so here rather than leaving you to wonder why nothing happened.
The four pieces
Web front end
Next.js, server-rendered. 47 routes. Talks only to the API on the same origin.
Node, loopback only. IIS is the one thing the outside world reaches.
API
ASP.NET Core. Sessions are database rows, not signed tokens, so signing out actually signs you out.
Windows Service, loopback only, behind the same IIS site.
Worker
Background jobs and outbound messages. Leased rather than locked, so a dead worker releases its work by expiry.
A separate Windows Service, so reminders keep running when nobody is browsing.
Database
SQL Server, its own database and its own login. It cannot reach any other database on the instance.
Verified: reads and writes its own 47 tables, refused on every other.
The API
Loading the description…
Most of these need a signed-in session, so opening one directly returns 401 rather than data. That is the check working: every route is closed by default. Sign in as an employer first and the same links answer.