AI Learning Experience Platform for Universities & Enterprises

A general chatbot answers questions without knowing your course, your learners or your assessments. Filari works inside the learning environment. The assistant answers from your approved course material, and it connects those answers to practice questions, feedback, progress and next-step recommendations for each learner.

It does not have to be. Filari is built as a modern learning experience layer over a headless Moodle learning core. You can use it as a complete new learning platform, or add the Filari experience and AI layer on top of an existing Moodle setup. The right model depends on your current platform and goals, and we assess this during discovery.

If you choose the model where Filari is added to your existing Moodle, no migration is required. Your courses, users and records stay in Moodle, and Filari adds the learning experience and AI capabilities on top. If you choose a new standalone platform instead, content and user migration becomes part of the project plan.

Universities and higher-education institutions, online education and EdTech providers, coaching and test-preparation institutes, and corporate learning and professional development teams. Each type of organisation can configure the platform around its own programmes, roles and workflows.

Yes. Filari can generate draft courses, modules, learning objectives, summaries and assessment banks from your existing documents. These are drafts. Faculty or trainers review, edit and approve them before anything is published to learners.

Suitable source material includes lecture notes, reading material, presentations and similar teaching documents. Output quality depends on the quality and structure of the source. Scanned or image-heavy files may need cleaning before use. We recommend testing with one real course during the demo.

From a source document, Filari can draft a course structure with modules and lessons, learning objectives, lesson summaries, and question banks with multiple-choice, scenario-based and descriptive questions. Your team decides which drafts to keep, change or discard.

No. AI-generated content and questions are reviewed by faculty or trainers before publishing. This keeps academic accuracy, tone and assessment decisions with your educators.

Yes. Every generated lesson, summary and question is editable. Educators can rewrite sections, add their own material, reorder modules or remove items before and after publishing.

Learners can ask questions about their course material, request simpler explanations, ask for examples, get summaries of a lesson and request hints while practising. The assistant is available inside the course, so learners do not need to leave the learning environment to look for basic help.

The assistant answers from your organisation's approved course material and knowledge base, using retrieval-augmented generation (RAG). It does not answer from the open internet. This keeps answers aligned with what your educators teach.

The assistant is designed to stay within the approved material rather than guess. How it responds to out-of-scope questions, for example pointing the learner to the educator or a related resource, is configured during implementation.

The assistant is designed to support understanding, not to hand out answers. It can give hints, explanations and worked examples instead of final answers during practice. Your institution can configure how it behaves in assessment situations.

Where the selected AI service and your implementation support it, the assistant can provide explanations and summaries in relevant languages. Supported languages are confirmed during discovery, based on the AI provider and your learner groups.

Filari can generate multiple-choice, scenario-based and descriptive questions from your course material. These can be organised into question banks, practice quizzes and tests. Educators review every question before it is used.

The AI Evaluation Assistant gives rubric-based scoring suggestions for descriptive answers. These are suggestions for human review. Educators make the final grading decision.

Yes. Practice activities can show feedback that explains why an answer is right or wrong and which topic to revisit. The level of automated feedback depends on the question type and the rules your educators configure.

Yes. Filari supports SCORM 1.2, SCORM 2004 and xAPI with a Learning Record Store, so you can use existing packaged content and track learning activity.

Filari recommends relevant lessons, revision material and practice activities based on available information such as course progress, assessment results and defined learning objectives. How well this works depends on the data available and the learning logic configured for your programmes.

Filari can identify skill gaps and learning readiness from progress and assessment data, so educators can see who may need additional support. Decisions about interventions stay with your educators and support teams.

Faculty can review learner progress and see topics a class may need retaught. Programme leaders and administrators can view participation, progress and assessment performance across courses and learner groups. Dashboards are configured around your roles and reporting needs.

Yes. Filari supports skill-gap identification, re-skilling recommendations and certification expiry forecasting. This is useful for professional programmes and corporate learning teams that manage recurring certifications.

Yes. Filari supports custom branding, colour themes and domain mapping, so learners see your institution's brand rather than ours. Certificates, email templates and dashboards can also carry your branding.

Yes. Filari supports multi-tenant setups with tenant-specific catalogues, dashboards, certificates, email templates and reporting. This suits universities with multiple schools, groups with several brands, or EdTech providers serving institutional clients.

Yes. Android and iOS apps are available in learner mode, for accessing courses, reading content and learning on the go. Administration and course authoring are done on the web platform, not in the mobile apps.

Yes. Filari supports paid certification programmes, coupons, a cart, payment gateway integration, invoicing and corporate bulk enrolment.

Filari is built on a headless Moodle core, so it works closely with Moodle. Integration with other LMS platforms depends on the platform, its available APIs and supported standards. We assess the right approach during discovery.

Yes. Filari supports enterprise SSO and Active Directory, so learners and staff can sign in with their existing institutional or company accounts.

Supported HRMS platforms include Darwinbox, Keka, SAP SuccessFactors and BambooHR. Integrations with student information systems, CRM, ERP and other tools depend on their APIs and your requirements, and are scoped and quoted separately.

The AI layer is built on large language models with retrieval-augmented generation and vector search. The AI provider is selected and configured for your implementation, based on your requirements for quality, cost, data location and policy.

No. Your institutional data, including course material and learner information, is not used to train public AI models.

Data protection depends on the selected architecture, AI provider, configuration and institutional policies. Access control, data retention, consent and regulatory requirements are defined with your team before deployment, and role-based permissions control who can see which data.

Hosting and cloud infrastructure are provided by your organisation or agreed during the project, so you can choose a location that matches your data-residency requirements. We document this as part of implementation planning.

Your educators and administrators. Faculty review AI-generated content before it is published, educators make final grading decisions, and your institution decides which AI capabilities are switched on for which roles.

It depends on the model you choose, the number of integrations and how much customisation you need. After discovery we share a phased plan with clear milestones, for example a minimum viable version first, followed by the full rollout.

Pricing depends on scope: the deployment model, number of learners, integrations and customisation. We share a quote after a discovery conversation. Third-party costs such as cloud hosting, AI API usage, SSO, SMS or push gateways and app store accounts are paid directly by your organisation.

Yes. Bring one sample course or a set of teaching documents to the demo, and we will show you what Filari builds around it, including draft lessons, questions and the learner experience.

Support scope is agreed in your engagement, covering areas such as platform maintenance, updates and help for your administrators. We define response expectations with your team before go-live.