One codebase, every academy.
Lectern is the system an academy runs its operation on. Every academy on it is a configuration of one codebase rather than a fork of it, which is the only reason a team this small can run any of them.
tenants
one shared system
- meridianlive
- name
- Meridian Academy
- domain
- meridian.lectern.systems
capabilities
- student_records
- check_in_kiosk
- qbank_pipeline
- portal_access
- payroll_analytics
- admissions_consulting
- your-academynot configured yet
- name
- Your academy
- domain
- yours.lectern.systems
capabilities: the ones you asked for, the rest off
Adding an academy adds a row. It does not add a copy of the software, which is why the second one costs less than the first.
One academy runs on it today and pays for it.
Why it works this way.
The core is the same everywhere: a student working toward a score by a test date. Software built around the appointment can book and bill, because the appointment is all it knows about. Software built around where a student is headed can tell you who is drifting.
Want to talk it through?
One academy, one email. The person who would configure your system is the person who answers it.