For IT administration
A plain Node.js application.
Next.js, Prisma and a MySQL database. No exotic infrastructure, no build step on the server, no search engine on the side. Participants come in via CSV or via SSO on the accounts you already manage.
Sound familiar?
Yet another platform to manage, with its own account sync, its own updates and a support stream that lands on your desk.
That is the worry, and it is a fair one. So this platform is built to ask little of you: familiar technology, clear roles, one-button updates, and a status page that says what is going on before anyone raises a ticket.
What administration takes
01 · Administration
Familiar technology
Next.js with server components, React, TypeScript, Prisma on MySQL or MariaDB, and Tailwind. A Node app like the ones you probably already run, including on hosting without shell access.
Access via CSV or SSO
Participants come in via a CSV file with a deliberately lenient format, or via Entra ID on the accounts you already manage. Self-registration does not exist, and SSO never creates an account automatically.
Clear roles
Platform administration, organisation administration and participant. By construction an organisation administrator only sees their own people; all administrative queries pass through a single enforcement point.
One-button updates
You run database migrations at the press of a button, including bookkeeping of what has already been applied. So an update can be carried out safely even without shell access.
A status page that says it
Per environment variable whether it arrived, whether the database connection works, which tables are missing and whether the content is in place. Details only for logged-in platform administrators, with a token-protected emergency entrance for when the database itself is the problem.
One daily background job
Reminders, the reinforcement track, the monthly email, cleaning up sessions and pruning the audit log: one job does it all, with the command ready to copy on the admin page. File uploads live outside the project folder, so a deploy never wipes them.
You decide which trainings an organisation may use, when modules unlock and who sees what.
02 · Your own LMS
Prefer your own LMS? Then SCORM.
On request a module is packaged as a SCORM 1.2 package with all course material, images, interactions and downloads inside. The package reports completion, score, last position and the given answers back to your LMS. Every package carries a traceable code and every export is logged. So you deliver no second environment, just a package in the one you already have.
Questions
03 · Short answer
What has to run on our side?
Node.js and a MySQL or MariaDB database. Nothing more: no build step on the server, no separate search engine, no message queue. The daily background job is a single command in a scheduler.
How do we set up a hundred people at once?
With a CSV file in a deliberately lenient format, or via Entra ID single sign-on on the accounts you already manage. Whoever comes in via invitation must choose their own password at first login and gets nowhere until then.
What do we see when something breaks?
The status page tells you per environment variable whether it arrived, what the database actually reports and which tables are missing. Migrations have their own bookkeeping, so you also see what has been applied and what has not.
See the administration from the inside
In a half-hour demo we walk through organisation administration, the status page and the migration button. Bring your own questions.