Problem

Academies and schools often rely on disconnected tools to manage students, teachers, staff, attendance, schedules, payments, and communication. This fragmentation creates operational overhead, makes information harder to access, increases manual work, and limits collaboration between administrators, teachers, students, and parents. The platform also requires a robust permission model to handle different user roles while maintaining data security and traceability for sensitive operations.

Solution

**Brivio** was designed as a unified educational ERP platform that brings academic, administrative, financial, and communication workflows into a single system. The platform provides dedicated portals for administrators, staff, teachers, students, and parents, supported by a granular **RBAC** permission system. It covers academy and branch management, scheduling, attendance, curriculum, homework, payments, helpdesk, reporting, real-time communication, and notifications. Flutter was used to deliver a consistent cross-platform experience, while Supabase provides a scalable backend based on PostgreSQL, Authentication, Storage, and Edge Functions, complemented by Firebase Cloud Messaging for push notifications.

Architecture

Brivio follows a **Feature-Driven Modular Architecture** inspired by **Clean Architecture principles**, with clear separation between presentation, business logic, and data layers. The application is organized into independent feature modules such as Authentication, Academy, Attendance, Payments, Communication, Curriculum, Helpdesk, Reports, and Security. This structure allows individual modules to evolve and remain maintainable without tightly coupling the entire system. The backend is powered by Supabase and PostgreSQL, using Supabase Auth for authentication, Storage for file management, Edge Functions for backend operations, and Realtime capabilities for live data and communication. On the application side, Riverpod is used for state management, GetIt for dependency injection, and Hive, Flutter Secure Storage, and Shared Preferences for local persistence and secure data handling.

Challenges

One of the main challenges was designing a single platform that could serve five different user roles while maintaining a clear and focused experience for each role without duplicating business logic or building completely separate systems. The project also required a granular permission model capable of handling a large number of actions and resources while maintaining data security and enforcing access policies at the database level. Another challenge was managing complex relationships between students, groups, teachers, schedules, attendance, and payments, while also supporting real-time features such as communication and notifications without compromising application performance or scalability.

Results

Brivio resulted in a unified platform covering a broad range of academic, administrative, financial, and communication workflows within a single ecosystem. The modular architecture provides a strong foundation for scalability and maintainability, while the RBAC system establishes clear and controlled access across different user roles. Core workflows such as attendance, homework, payments, communication, and reporting are now organized through dedicated role-based portals, creating a more structured experience for every stakeholder and providing a solid foundation for introducing additional modules and capabilities in the future.