Lyncs architecture presentation, with a fictional client and demo data

Lyncs

Move any system into Lyncs without losing a record, a grade or a certificate.

This page explains how Lyncs works in plain language: the idea, the architecture on one page, all 30 steps, a live demo, the safety guarantees and how we build it.

Demo client: Horizon Academy on Moodle 4.3Target: LyncsLyncs AI sees field names only, never learner data

The idea, in plain words

Schools and companies keep years of courses, learners, grades and certificates in an old system. Moving them is like moving house with valuables: one dropped box can become a compliance problem. Lyncs is the careful moving company.

Every record ends in one of five places. Nothing is lost silently.

The Lyncs architecture on one page

Data moves left to right through five zones. The old system is only ever read. Gates stop the work from moving on until something has been checked.

Always running under every zone

The gates, in order

All 30 Lyncs steps, in 8 stages

Read top to bottom. Each stage ends in a gate: a check that must pass before the next stage starts. Use the button on a card to watch that stage in the demo.

Watch Lyncs run

A demo migration for a fictional school: 426,102 records from Moodle into Lyncs.

Why you can trust it

Six guarantees built into Lyncs, not promised in a contract.

How we build Lyncs

Start with the smallest slice that can complete one real migration safely. Measure the effort. Widen only when a gate says it is worth it.

Lyncs must be ready to receive a bulk import first

What the first migration includes, and what waits

The 13 build phases

Decision gates

Glossary

Plain meanings for the terms used above.