A guided walkthrough of the dashboards, workflows and configuration your school would use.
Request a Demo →Designed in Cameroon around real school operations, real connectivity and two working languages.
Why it matters →Nexus Kamer connects school operations, educators, parents and students in one place — from admission through enrollment, academics, attendance, fees and reporting.
Term 2 · 2025/2026 · All sections
1,284
Across 28 classes
94.2%
Marked in 26 of 28
78%
Term 2 invoices
12
Admissions & permissions
Nexus Kamer is configured per school, so the same platform fits a small primary school and a multi-section secondary campus.
Ten connected areas of school operation around a single student record — so information entered once is available everywhere it is needed, and nowhere it should not be.
School work does not happen in modules. It happens in sequences — a request becomes a decision, a decision becomes a record, a record becomes a report. Nexus Kamer follows those sequences from beginning to end.
Application, review and approval
Record created, class allocated
Teaching, assessment, grades
Marked to the school’s rules
Invoice, verify, reconcile, receipt
Report cards and oversight
Invoice → Payment → Verification → Reconciliation → Receipt → Notification
Parent request → Principal review → Decision → Teacher notification
Certificate → Restriction → Affected activity → Dates → Status
Each role sees the part of the school it is responsible for — and only that part.
Leadership sees the whole school — population, attendance, academics, finance and everything waiting on a decision.
Teachers work inside the classes assigned to them — marking attendance, recording assessments and following progress.
Guardians and sponsors follow fees, attendance and reports for the students explicitly linked to their account — and nobody else.
Linked students only. A guardian account cannot reach any other student’s record.
Students see their own record: subject performance, attendance, released reports and the recognition they have earned.
Access follows relationships: a parent or sponsor account can only reach information for students explicitly linked to it, and a student account only reaches its own record.
Built around the realities of running a school here — connectivity, language, and the way school decisions actually get made.
Explore the platform →Connectivity in many schools is intermittent or expensive. Nexus Kamer is designed so that essential day-to-day work — such as marking attendance — can continue during an interruption and synchronise once the connection returns.
Offline support is scoped deliberately: not every feature works without a connection, and the interface always states the current sync status rather than hiding it.
Bringing school administration out of ledgers and loose paper and into one connected digital environment — where the school, its teachers, its parents and its students all work from the same record.
The physical school
Registers, files and receipts held in separate places.
The connected school
One record per student, shared across every workflow.
The digital community
Leadership, teachers, parents and students in one place.
English and Français are part of the product architecture, not a translation added at the end. Each user works in the language they choose, on the same school record.
Report card templates, fee documents and notifications follow the language of the person reading them, while the underlying data stays single-sourced.
Nexus Kamer is a web application. The same platform adapts to the office desktop, a tablet in the staff room and a parent's phone — no separate app to install.
One platform · three form factorsThe same web application, on whatever device is to hand
School records are sensitive. Access in Nexus Kamer is decided by role and by relationship, and important actions leave a trace.
Every account acts within a defined role, with permissions the school administrator controls.
Guardians reach only the students linked to them; students reach only their own record.
Accounts are individual and verifiable, with session handling appropriate to shared school devices.
Personal contact details stay inside the platform; communication does not expose private numbers.
Approvals, payments and record changes are traceable to an account and a moment in time.
Academic, financial and medical-restriction records are separated and access-controlled.
Access is not a single switch. Each account has a role, and within that role a boundary set by its relationships.
The whole school, within the permissions leadership grants.
School-wideAssigned classes and subjects — not the whole student body.
Assigned classesOnly the students explicitly linked to the account.
Linked studentsTheir own record, and nothing beyond it.
Own recordNexus Kamer is not a bank and does not hold school funds. The platform organises the school's financial operations and payment orchestration; settlement goes to the school's own designated bank or payment account.
Issued from the school's own fee structure.
Recorded against the invoice and the student.
Confirmed by the bursar before it counts as settled.
Matched against the school's account activity.
Released to the paying parent or sponsor.
Every step attributable and reviewable later.
| Invoice | Student | Amount | Status |
|---|---|---|---|
| INV-2042 | Ngwa A. · Form 3A | 120,000 XAF | Verified |
| INV-2043 | Mballa E. · Form 1B | 95,000 XAF | Awaiting verification |
| INV-2044 | Tchoumi L. · Form 5C | 150,000 XAF | Part paid |
Schools differ in calendar, grading, pass marks and promotion. Nexus Kamer is configured to match how your school already operates, instead of asking the school to change its operations for the software.
School administration · configured once, applied everywhere
Because records are captured once and connected, leadership reports are a view of the school's real activity rather than a separate exercise at the end of term.
1,284
94.2%
78%
31.4M XAF
Leadership, teachers, parents and students communicate inside the platform, so messages stay attached to the right student and the right term — and personal contact details are never exposed.
Term 2 assessment schedule has been published to the class.
Noted. Requesting permission for Friday afternoon.
Request received and forwarded for review.
Schools set their own criteria for recognition, and awards are recorded against the student's record alongside academic and attendance history.
An administrative record, handled discreetly.
From parent request to teacher notification.
Publish a post in WordPress and it appears here automatically — lead story first, then the two most recent supporting stories, each with its category, date, featured image and excerpt.
Add the first News post →News items are standard WordPress posts — category, date, featured image, excerpt and permalink come from the post itself. Photographs of school vehicles are environmental only; Nexus Kamer does not provide a transport-management module.
Nexus Kamer is built in Cameroon, for schools in Cameroon and across the continent, by a team working directly with school administrators.
Practical material for the people running the school
See how Nexus Kamer can simplify your school's operations, connect your community and give leadership clear visibility — configured around the way your school already works.
A member of the team will walk your leadership through the platform and how it would be configured for your school.