School-first product
Workflows start with the people, structures and responsibilities found inside a school.
About Unifloe
Unifloe is built and operated by PaperKite
PaperKite creates and operates Unifloe, a school ERP and LMS built for Indian schools. Unifloe brings academic, administrative, financial, communication and campus work into one role-aware product.
Role-aware by design
Students, faculty, leaders and operational teams receive focused views backed by server-side permission checks.
Gradual rollout
Schools can begin with the workflows that matter most and expand their enabled modules over time.
01
About Unifloe
PaperKite creates and operates Unifloe
Unifloe is PaperKite's school ERP and LMS for Indian schools. PaperKite develops and operates the product, while schools use Unifloe to connect teaching, attendance, fees, requests, communication and campus services around a shared school structure.
The platform covers web and installable PWA experiences, with selected mobile journeys using the same authenticated school APIs. Each school retains its own identity, enabled modules, academic structure and data boundary.
02
About Unifloe
Built around real responsibility boundaries
Visibility in the interface is not treated as authorization. Product services evaluate the signed-in actor, school tenant, role, module entitlement, assignment, ownership and workflow state before protected actions are allowed.
PaperKite operates the platform control plane for institution onboarding, module entitlements, subscription administration and approved support communication. School-owned academic and operational decisions remain inside authorized school workflows.
- Tenant-aware school records and platform records
- Role, assignment and ownership checks
- Audited high-impact changes and approvals
- Private school uploads and controlled delivery
03
About Unifloe
Practical progress, not inflated claims
Unifloe has a catalogue of 65 registered modules. Some have dedicated workspaces and domain services, some share richer grouped workspaces, and some remain configurable manifest-driven surfaces until a school needs a specialized flow.
Demo and onboarding conversations therefore focus on the workflows a school intends to use, the current implementation shape, required integrations and a realistic rollout sequence.
See how PaperKite can map Unifloe to your school.
Share your priorities and receive a focused product conversation.