QR-Ashram

Institutional governance for K-12 schools

The Digital Spine of Institutional Governance

Governance-grade school operations without the bloat of a legacy ERP.

QR-Ashram gives schools a disciplined operating core for identity, attendance, fee ledgers, parent communication, and reporting while keeping the public entry path simple and institutional.

Public entry for school administrators, teachers, and governing bodies
QR identity as a system primitive for attendance and institutional records
Built for Tier-2 and Tier-3 Indian schools that need structure before sprawl

Problem Statement

Why schools outgrow legacy ERP stacks before they become truly governed.

QR-Ashram is built around the operational constraints of Indian schools, especially where affordability, staffing density, and intermittent connectivity shape the real daily workflow.

Bloated legacy ERPs

Schools pay for broad software suites that are expensive to adopt, rigid to configure, and poorly matched to the daily operating rhythm of smaller institutions.

Fragmented record systems

Attendance, fees, identity, and parent communication often live in separate tools, which creates duplication, blind spots, and operational debt.

Connectivity gaps at critical touchpoints

Gate entries, classroom routines, and office workflows cannot stop when network quality drops. Institutional systems need continuity, not best-case assumptions.

Solution Architecture

Platform spine, governed plugins, and one institutional identity across many surfaces.

The core architecture is intentionally sequenced. Schools start with the mandatory operational spine, then activate adjacent capabilities without losing control of data ownership, workflow boundaries, or governance discipline.

Identity and access spine

Multi-tenant access control, QR-linked profiles, and role-aware governance for students, staff, and operators.

Operational event surfaces

Attendance, fee actions, parent communication, and reporting share a disciplined event model instead of siloed feature islands.

Sync and reporting foundation

Offline-first touchpoints and structured reporting keep schools functional during disruptions and auditable afterward.

v1.0 Module Proof

Core modules for daily operations, not abstract roadmap theater.

The first release focuses on the minimum institutional operating system a school needs every day. Each surface exists because it is operationally mandatory, not because it makes for a broader feature list.

Dashboard

Active

Central control surface for metrics, alerts, and administrative visibility.

Students

Active

Identity, enrollment, records, and governed profile management across the institution.

Staff

Active

Teacher and operator administration with role-aware assignments and searchability.

Attendance

Active

QR-driven attendance logs and registers structured for daily operational throughput.

Fees

Active

Basic ledgers, dues tracking, and collection workflows designed for v1.0 discipline.

Parents

Active

Communication hub for messages, notices, and institutional broadcast surfaces.

Trust and Security

Built for institutional scrutiny, not casual SaaS tolerance.

Schools, networks, and governing bodies need systems that support accountability. QR-Ashram is framed as a governance surface first, which changes how permissions, records, and future expansion are handled.

Supabase-backed multi-tenant architecture with strict tenant isolation

Row-level security and role-based access control as first-order platform rules

Audit-friendly operational data for attendance, communication, and financial actions

Policy-aware posture for retention, privacy controls, and institutional reporting

Roadmap

A phased platform roadmap with a clear operational sequence.

The roadmap is activation-governed. Each version extends the same core institutional spine rather than forking into disconnected product lines.

v1.0Active Build

Platform Spine Activation

Operational foundation across dashboard, students, staff, attendance, fees, and parents.

v1.1Specified

Payments and Subscription Layer

Institutional plans, billing automation, GST invoicing, and Razorpay-backed state management.

v1.2Specified

Flutter Mobile Access

Native mobile access for gate security, teachers, parents, and offline-first field operations.

v1.3Specified

Plugin Architecture Framework

Governed extension model with capability declarations, event boundaries, and UI injection zones.

v1.5Specified

Institutional Network Governance

Multi-school trust and franchise oversight with centralized policies and network reporting.

Public Entry

Bring discipline to daily school operations before complexity becomes permanent.

Keep the public route simple, move authenticated users into the platform, and let decision-makers evaluate the governance model through a safe demo path.