Questions
Clear answers before your school rollout.
A practical guide for school owners, administrators, registrars, accounting teams, and IT teams evaluating KernelCampus.
What does KernelCampus help a school manage? +
KernelCampus brings admissions, school websites, student records, payments, parent and student portals, communications, cybersecurity review, and LMS preparation into one operational platform.
Can a school start with admissions only? +
Yes. A school can begin with website and admissions workflows, then add payment verification, portals, student records, LMS, library, property, and reporting modules as the rollout matures.
How are payments handled? +
The production-ready flow supports fee structures, payment schemes, invoices, manual proof upload, accounting verification, and receipts. Online gateway adapters can be enabled when the school merchant account is ready.
Does KernelCampus support mobile access? +
Yes. The Laravel backend is API-ready for the Flutter mobile app. Parents and students can use secure tenant-aware endpoints after selecting their school.
Can each school use its own branding? +
Each school can configure its logo, colors, banners, website content, and portal branding without changing the shared KernelCampus codebase.
How does onboarding usually work? +
The usual rollout starts with school setup, academic structure, admissions offerings, fees and payment rules, portal access, staff roles, and a short UAT cycle before pilot launch.