01 · Install
Choose a route that fits your server.
Ubuntu/Debian installer, Docker Compose or a Node.js development setup. Each route lists prerequisites, commands and what to do after the first sign-in.
Open installation guide →Home / Documentation
For school teams and operators
Find the next step, from first install to daily use.
SchoolKick guides for attendance, family access, fees, exams, server setup and the API. This early release changes as the product grows.
02 · First day
Create the school and take a first register.
Set up an owner account, create classes, invite teachers and guardians, add learners and make the first attendance record.
See attendance features →03 · Fee records
Keep invoices and payment status traceable.
Create invoices, record cash or UPI QR payments confirmed by the school office, issue receipts and review refund approvals. Card and bank provider integrations are not available yet.
Review fee workflows →04 · Exams
Manage registration through the hall ticket.
Set subjects, registration dates, attendance eligibility and fees; families register linked learners and view issued hall tickets. Marks entry and result release are not available yet.
Review exam workflows →05 · API
Read the route map before integrating.
The OpenAPI file lists operations, summaries and role access. Request and response schemas are incomplete, so verify a workflow against the source and test it before relying on automation.
Open OpenAPI 3.1 route map →06 · AI access
Use public docs with AI tools safely.
Machine-readable product guides and the OpenAPI route map help AI assistants understand the software. School records remain behind signed-in sessions and role checks.
AI access and data boundaries →07 · Operate
Make decisions about access, updates and backups.
Read the current security controls and known limits. Configure HTTPS, limit account creation, test backups and follow local rules for children’s information.
Read security notes →Before production use
Know the release boundaries.
No independent security, accessibility or legal review has been completed. Keep real learner data out of the hosted demo. Operators remain responsible for permissions, backups and retention.