School automation, in one calm rhythm.
SchoolERP is a School Automation System that connects school operations, people, communication, and the public school website—inside an isolated workspace for each institution.
Designed for education teams of different shapes
One connected workflow
From school setup to a live digital presence.
SchoolERP brings operational context and public communication into one deliberate flow, so administrators can see where work begins, who can act, and what gets published.
Set up the school
Create the school, primary campus, roles, and administrator access in a defined tenant context.
Organize daily records
Keep campus and student work inside one role-aware operational workspace.
Connect the community
Coordinate staff, guardian, student, and communication flows without mixing school contexts.
Publish with control
Build the bilingual school site, review content, and publish through a verified hostname.
The operating surface
The school day, made legible.
A focused workspace keeps core school contexts close without turning the interface into a maze.
Students and campuses
Keep student and campus context visible to the people whose roles permit access.
Roles and portals
Dedicated administrator, teacher, guardian, and student experiences support each school community.
School communications
Prepare communication workflows for email, SMS, Telegram, and WhatsApp channels.
Website and domains
Create a responsive Bangla and English school site and connect a verified domain safely.
Purposeful automation
Keep people in context, not in silos.
Staff work from the school context their role allows. Guardians and students reach their own portals. Administrators manage the school website and domains without leaving the operating environment.
- Explicit school and campus context
- Role-aware portals and administration
- Communication channels prepared for school workflows
- Bilingual website publishing with domain verification
Security is part of the workflow
Each school stays inside its own boundary.
School context is explicit, sessions use the protected same-origin path, and a hostname is published only after its provisioning and verification steps are ready.
Tenant isolated
School context is checked as requests move through the platform.
Verified hostnames
A school hostname follows ownership, routing, and TLS readiness checks.
Controlled access
Roles determine which workspace and school operations a person can use.
Published marketplace plans
Start with the plan that fits your school.
Review the current pilot and annual buying options, localized pricing, and secure payment path in the Mohuls Marketplace.