Universities
One agreement,two programmes.
A university collaboration brings together Lanvex Academy and Lanvex Venture Studio under a single memorandum, run as two clearly separate programmes with their own schedules.
Schedule A: Lanvex Academy
- The university teaches approved courses and runs permitted labs.
- Lanvex sets the syllabus, controls assessment and issues credentials. A course completion is not a credential.
- Engineer and Architect credentials need practical, proctored work on a Developer VM, which must actually exist before anyone books one.
Schedule B: Lanvex Venture Studio
- Founder discovery, domain validation and support for teams building a framework company.
- Student projects run with rights, data and contributor safeguards settled in writing first.
- The free student path carries no equity and no assignment of what a student creates.
What we settle together first
- An authorised institutional sponsor, and a signatory with the standing to bind the institution.
- Its own intellectual-property policy, applied to student and faculty work.
- Ethics, privacy and data policy for anything used in teaching. Learning examples use synthetic data.
- Written permission before any institution is named, pictured or implied as a partner.
Where we are
We are in conversation with institutions about the first cohort, each as its own separate collaboration. We name a university here once an agreement is signed and they are happy to be named.
Five pathways and forty-six modules, published so an institution can judge it before committing to anything.