From research universities to schools, boarding houses, and business schools — AMVLET gives institutions a private, encrypted, on-campus communications platform built on the open Matrix standard. Their data, on their servers, under their jurisdiction.
Universities, schools, boarding schools, and business schools all face the same question: who controls the conversations that take place on campus? AMVLET puts that answer back in the hands of the institution.
Private messaging, video, and group rooms for tens of thousands of students, faculty, and researchers — hosted on the university's own infrastructure.
One safe channel for teachers, parents, and pupils — replacing the patchwork of consumer apps that quietly send children's data to foreign companies.
Round-the-clock pastoral communication between houseparents, students, and parents — encrypted, auditable, and never routed through Silicon Valley.
Cohort-grade collaboration between executives, alumni, and corporate partners — with the confidentiality that case studies, NDAs, and recruiting pipelines demand.
Universities are where the modern internet was born. They were among the first to run their own email servers, their own web servers, their own libraries of knowledge. Today, the same logic applies to messaging.
A large research-led medical university in Europe has been quietly running a campus-wide encrypted messenger for tens of thousands of doctors, students, and staff — entirely on its own servers, integrated with its existing identity and clinical systems. The platform is the same open standard AMVLET is built on. The lesson is simple: this works at scale, in regulated environments, on the institution's own terms.
What used to take a large internal IT project — server rollout, federation setup, identity integration, mobile app distribution, training — AMVLET delivers as a turnkey deployment. Universities get the sovereignty without the multi-year build.
Servers run in the university's own data centre. Student, faculty, and research conversations never leave the institution's perimeter or its national jurisdiction.
Students and staff sign in with the same campus credentials they already use for email and library systems. No new accounts, no shadow IT, no personal phone numbers shared.
Departments, hospitals, research groups, and partner institutions can collaborate across servers without surrendering their data to a central platform. Every party stays in control of its own users.
End-to-end encryption protects unpublished results, grant work, and clinical-trial discussion — keeping intellectual property out of consumer messaging apps and foreign cloud providers.
The hard parts — federation, encryption, identity integration, mobile clients, admin tooling — arrive pre-assembled. The university focuses on teaching and research, not on running a messaging stack.
Teachers, parents, pupils, and the head office in one private network — replacing the mix of consumer chat groups, SMS chains, and personal email that no one can audit.
Pupil messages, photos, and contacts never flow through advertising platforms. The school is not the product. The pupils are not the product.
Form-tutor groups, year-group rooms, and parent channels are created and moderated by school staff — not by whoever happens to start a WhatsApp chat first.
Conversations between staff and pupils are logged, attributable, and reviewable for safeguarding purposes — without requiring teachers to surrender their personal phones.
Parents and pupils install one app and sign in. No new phone, no new number, no extra licence. The school keeps the data; the family keeps the convenience.
Most schools today communicate through a shifting mix of consumer messengers, personal email, and printed letters home. Each one is convenient, none of them is private, and none of them is under the school's control. When a parent screenshots a class chat, when a teacher's personal number ends up in a year-group thread, when a pupil's photo travels through an advertising-funded server — the school carries the risk.
AMVLET gives a school its own communication layer: one app, branded for the school, hosted in a place the school chooses, governed by the data-protection rules the school is already required to follow. Setup is the kind of thing the school's existing IT lead can do in an afternoon — not a year-long procurement.
Boarding houses run on conversations: between house parents and pupils, between night staff and matrons, between schools and families spread across time zones. These conversations are sensitive, constant, and often urgent — yet most of them happen today on consumer apps that the school neither owns nor can audit.
AMVLET puts the whole boarding community on a single, encrypted, school-controlled network. House groups, duty rotas, parent updates, and emergency channels live in one place — with full continuity of records when a houseparent or matron leaves their role.
Each house has its own private space for staff, pupils, and parent contacts. Information stays inside the house and inside the school.
Duty staff coordinate handovers, medical incidents, and welfare checks in dedicated channels, with a clear, time-stamped record for the safeguarding lead the next morning.
Asynchronous, encrypted updates and voice notes reach parents wherever they are — without exposing pupils, staff, or family contact details to advertising platforms.
When a houseparent leaves, the conversation history stays with the house, not on a personal phone. The next person in the role inherits the full context.
Staff communicate with pupils and parents through their school identity, never their private number. The boundary is built into the platform, not left to individual judgement.
Each cohort, club, and alumni chapter gets its own encrypted room — replacing the public group chats where confidential discussions usually leak.
Live case work, executive coaching, and confidential project rooms run inside the school's own infrastructure — not on a public conferencing service that may train AI on the contents.
Recruiters, sponsors, and executive education clients connect to cohorts through federated rooms — keeping their own data on their own servers while still talking to your students.
End-to-end encryption means the school's IT team — and any external vendor — cannot read confidential discussions between students and corporate partners.
Alumni keep a school-issued identity for life, used to join class reunions, careers networks, and continuing-education programmes — without selling the alumni list to a third-party platform.
Executive students, alumni, and corporate partners carry expectations about discretion that consumer messengers cannot meet. Case studies are confidential, recruiting pipelines are confidential, the conversations after a guest lecture are confidential — and yet most of these run today on platforms that explicitly reserve the right to harvest content.
AMVLET delivers a private, branded network that lives under the business school's own jurisdiction. Class cohorts, alumni chapters, and executive education clients get the same modern user experience as a public messenger — without surrendering the school's most valuable asset, the trust of its community.
A major European research-led medical university has been operating a campus-wide, encrypted, federated messenger for years — across tens of thousands of doctors, students, researchers, and staff. The data lives on the university's own servers. The platform integrates with the university's identity systems. Federation lets it interoperate with partner institutions without giving up control.
This is not a slide deck. It is the live, daily communications platform of a large public institution. AMVLET brings the same architecture to your campus — and removes the heavy engineering effort that the early adopters had to invest. What once required a multi-year internal project is now a turnkey deployment.
Julius is a digital-native co-founder who spends most of his time on campuses — listening to students, professors, and IT teams about how messaging actually works in their institutions. As Youth Advisor, he runs the on-campus education programme: workshops, guest lectures, and pilot deployments that put sovereign communications into the hands of the next generation.
AMVLET's education programme is led by our Youth Advisor and Co-Founder. It is designed to do more than sell software to a procurement office — it is designed to make sovereign communications part of how the next generation thinks about technology. Four practical pillars, available to any university, school, boarding school, or business school we partner with.
A guest-lecture module on digital sovereignty, data-protection law, and open-source security — designed to drop into existing computer-science, cybersecurity, business, and policy programmes.
Deploy AMVLET on campus for a pilot cohort. Students, staff, and parents experience sovereign communications first-hand, with data hosted locally under the institution's own oversight.
Partner with us on applied research: new use cases for federated communication, post-quantum encryption, identity, and education-specific deployments.
Local graduates — with a deliberate emphasis on under-represented groups in technical roles — work directly on AMVLET deployments, building real-world engineering experience while still on campus.
Schools and universities are some of the most heavily regulated handlers of personal data in any country. AMVLET is designed to satisfy those rules out of the box, not retrofitted to them.
Full GDPR compliance with data residency in the EU, lawful basis for processing student and staff data, full data-subject rights, and a Data Processing Addendum included with every deployment.
Designed from the ground up to satisfy the Personal Data Protection Law: data localisation inside the Kingdom, consent management, and governance controls aligned with national requirements.
Platform and operational processes certified to ISO 27001. Independently audited security controls, documented incident response, and full risk-management framework.
Architecture, access controls, and audit logs aligned with FERPA requirements for institutions handling US student education records and parental access rights.
Logged communications between staff and pupils, role-based access for designated safeguarding leads, and clear separation between personal and professional accounts.
Built on a published, non-profit-maintained open protocol. Any institution can fork, migrate, or self-host its deployment at any time, without permission and without losing data.
Run a campus pilot in weeks, not years. Our Youth Advisor will co-lead the rollout with your IT and academic teams.