Online Learning Platform for Universities

US regional accreditors (WASC, MSCHE, HLC, SACSCOC, NECHE, NWCCU) require auditable evidence of student learning outcomes, credit-hour equivalence for online courses under the US Department of Education Program Integrity Rule, and student identity verification in credit-bearing online courses. The platform generates rubric-mapped outcome reports at the course, program, and institution level; tracks seat-time and engagement metrics that support credit-hour equivalence arguments; logs identity-verification events for exam sittings and course sessions; and exports OLC Quality Scorecard evidence across the nine scorecard categories. Institutions running the platform assemble accreditation self-studies from platform reports rather than reconstructing evidence from disconnected systems.

A 5,000-learner university running self-hosted OpenEduCat typically spends $150,000-$300,000 across 5 years covering hosting infrastructure (AWS m5.xlarge or equivalent handles 5,000 learners comfortably at roughly $200-$400 per month), one-time implementation and SIS-consolidation project ($50,000-$150,000 depending on migration complexity), optional Enterprise support at $19 per staff user per month, and training. Canvas Cloud plus a separate SIS plus separate parent and communication tools typically lands at $400,000-$700,000 across the same 5 years; Blackboard Anthology similarly. The gap widens at scale because commercial platforms are per-learner priced while open-source infrastructure scales sub-linearly. The specific numbers depend on institution scale and procurement bargaining power; the ratio is consistent across published EDUCAUSE Core Data Service and institutional procurement data.

1EdTech (formerly IMS Global) LTI 1.3 support covers the third-party tool ecosystem universities depend on: Turnitin for plagiarism detection and originality reports, ProctorU and Honorlock for online proctoring in credit-bearing exams, Respondus LockDown Browser for high-stakes assessments, Kaltura and Panopto for lecture capture and video hosting, WeBWorK and MyMathLab for math courseware, Zoom and Google Meet and Microsoft Teams for synchronous sessions, and library-database platforms via LTI Advantage. LTI 1.3 Deep Linking, Names and Role Provisioning Services, and Assignment and Grade Services are all supported. Configuration for a specific vendor typically takes 2-4 hours with vendor cooperation.

US universities running Title IV programs must track satisfactory academic progress (SAP), report student enrolment status to NSLDS (National Student Loan Data System), calculate return of Title IV funds under the R2T4 rule when students withdraw, and generate 1098-T tuition statements annually. The platform handles SAP tracking against configurable GPA and pace-of-completion thresholds, generates NSLDS enrolment reports, computes R2T4 refund amounts, and produces 1098-T forms with box-1 (payments received) and box-5 (scholarships and grants) reconciliation to the fee ledger. Title IV audit-trail retention meets Department of Education record-keeping requirements.

Yes. Competency-based education (CBE) programs decouple learning from seat-time, requiring competency-mapping, direct-assessment workflow, and prior-learning-assessment (PLA) credit posting. The platform supports competency-map definition at the program level, per-student competency-progress tracking against defined mastery criteria, PLA credit recording with source documentation, and direct-assessment academic-year reporting for federal-aid eligibility under the US Department of Education CBE experimental sites and CBEN (Competency-Based Education Network) reference framework. Institutions running C-BEN-aligned programs use the platform for competency-progress evidence.

The platform is built on the Odoo OWL frontend framework which follows WCAG 2.1 AA guidelines with 2.2 alignment in active development. Coverage includes screen-reader support in NVDA, JAWS, and VoiceOver, keyboard navigation for all interactive elements, accessible video player with caption tracks and audio description, accessible quiz interfaces with sufficient time and clear focus states, and high-contrast themes. A VPAT (Voluntary Product Accessibility Template) is available for institutional procurement review. Section 508 (US federal contractors), EN 301 549 (EU public sector under the Web Accessibility Directive), and state-specific laws (California AB 434, Massachusetts EOHHS) are addressable with the platform baseline plus institutional accommodation workflow. US OCR enforcement under Section 504 and Title II of ADA is a real institutional risk; the platform provides the accessible substrate.

Yes. GDPR Article 44 restrictions on transfers of personal data to third countries, reinforced by Schrems II, make US-headquartered cloud SaaS platforms difficult for many EEA universities. Self-hosted OpenEduCat runs in AWS Frankfurt, Azure Germany, GCP Belgium, French Bleu Cloud (S3ns), German Delos Cloud, or on-premise inside the university data centre. Data residency, encryption at rest and in transit, and access-log audit are institution-controlled. For US universities under state-specific residency rules (California CPRA, Illinois BIPA for biometric identifiers, Texas SB 820 for K-12), the same self-host flexibility addresses the requirement. Vendor cloud-only SaaS platforms cannot match the sovereignty control.

A large university typically runs a 12-18 month phased migration. Phase 1 (months 1-3) covers evaluation, procurement, and platform provisioning. Phase 2 (months 4-6) covers 1-2 department pilots to validate course-content migration via Common Cartridge or QTI export, gradebook history import, SSO and identity migration via Shibboleth or SAML, and faculty-training design. Phase 3 (months 7-12) covers institutional rollout with phased department-by-department migration aligned to academic-year boundaries. Phase 4 (months 13-18) covers legacy-platform decommission with learner-record archive per accreditor retention requirements (typically 5-7 years for US regional accreditors). The determining factor in migration success is faculty change-management investment, not the platform technology.