Training providers run on spreadsheets, shared inboxes and memory. nLearn runs the whole thing — the enquiry, the quotation, the booking, the trainer, the joining instructions, the certificate and the feedback — without any of it living in somebody’s head.
Open source. Hosted in the UK. And you own it — a perpetual licence and the source code, so it keeps running whatever happens to us.
An enquiry arrives — by phone, by email, from your website — and becomes a quotation built from your own rate card. Several options on one enquiry, priced properly, with the proposal generated as a PDF rather than assembled by hand.
The client accepts through a link and the quotation becomes a booking. Trainers assigned, venue set, delegates enrolled. Co-delivery handled properly — two trainers on one course, each with their own agreed fee.
Joining instructions sent automatically. Pre-course questionnaires so the trainer knows the room before walking into it. Certificates issued and verifiable by anyone holding the reference, without a phone call to check.
Delegates evaluate the course and the trainer. Trainers see their own feedback in their own portal, unattributed unless the delegate chooses otherwise. And you can always follow up, because you always know who said it.
PostgreSQL, Node.js, Vue, Caddy, Authentik. No proprietary platform underneath, no vendor whose pricing can change the economics of your business, and nothing you cannot inspect.
It matters more than it sounds. Software built on somebody else’s closed platform can only be handed over as far as that platform allows. Ours can be handed over completely, because every part of it can be.
A named provider in a named location, on a server nobody else shares. Not a region on a hyperscaler’s map that might mean anywhere.
One deliberate exception, stated rather than buried: encrypted backups sit in Western European object storage. The provider holds ciphertext and no key. Everything else — the database, the application, the identity provider — is in the United Kingdom.
The full security position → — including what we have not done.
The first question anyone sensible asks a small supplier is what happens if that supplier disappears. Most answers are reassuring noises. Ours is in the contract.
Irrevocable, and it survives termination for any reason — including if you stop paying us. It is not conditional on a subscription.
A complete copy with the full commit history, the documentation and the deployment configuration. Held in your systems, not ours.
Escrow exists because suppliers will not hand over source. We already have. There is nothing for an agent to hold that you are not holding already.
A reasonable question, and one worth answering before you ask it. If we give away the licence and the source, something has to pay for the work.
Hosting, backups, monitoring, security patching, upgrades and support. The infrastructure is ours to keep running and ours to answer for at three in the morning. That is what the recurring charge buys.
New features, integrations with your other systems, reports built the way you actually want them. Quoted before the work starts, not discovered on an invoice afterwards.
What you are not paying for is permission to use your own system. The licence is not the product. The service is. Which means we have to keep the service worth paying for, rather than relying on how painful leaving would be — because leaving is not painful. You could take the source and engage another developer tomorrow.
We think that is the right way round. It is certainly the more honest one.
Not a learning platform, and not a course marketplace. nLearn is the coordination — the part between a company asking for a course and the certificates going out.
It handles multiple legal entities, several sales areas, delivery in any currency, and trainers who are self-employed contractors rather than staff. If any of that sounds like an awkward exception to your current system, it is the ordinary case here.
Built and running on its own UK infrastructure. Nearly five hundred automated tests. A full documentation set — architecture, design, security, backup and recovery, records retention. First customer preparing to go live.
One customer so far, and one person building it. An independent penetration test is scheduled rather than done. Our open items are written down and shared with the customer, not left to be discovered.
Tell us what your week actually looks like and we will tell you honestly whether nLearn helps. If it does not, we will say so.
Get in touch →