For universities that already run a records system and an LMS

One place to act. On top of your records system and Canvas.

The student record stays where it is. Teaching stays in Canvas. Anvara adds what students and offices are missing: requests with an owner and a deadline, payments that explain themselves, approvals with an audit trail, and a home page that says what to do next, in Bangla or English.

0systems replaced

1sign-in, with the university's own Google or identity provider

7interface languages, including Bangla

See the demo Talk to us The demo runs on test data with made-up students. Nothing you do there reaches a real university.

Teaser · 1 min 38 s · the real product on test data. The 13-minute walkthrough goes through every area.

How it fits

Your systems stay. Anvara is the layer people act in.

Anvara: the layer people act in

Reads the university's records; writes back only after the right person approves.

Requests, routing, deadlines
Holds that say how to clear them
Payment states and reconciliation
Financial aid, net payable
Registration guidance, exceptions
Transfer credit, degree audit
Results approval, grade-change trail
Exam timetable clash checks
Help pages with cited answers
Staff "Needs you" home
Two-factor sign-in, System status
Phone layout, 7 languages

status, balance, grades, rostersapproved results, enrolment changes, payment matches

Records systemStudent record, programmes, cohorts, official resultsStays official

Canvas or MoodleCourses, sections, people, enrolments, gradesStays the classroom

Banks, bKash, Nagad, cardsThrough the university's own gateway account; settlement filesStays the ledger

Google Workspace or your identity providerEmail and sign-in for every student and lecturerStays the identity

What a student sees

One home: what needs them, what is coming, what is in progress. A hold says why it is there and how to clear it. A bill shows billed, approved aid, pending aid and net payable, and the next instalment date.

Student home on a phone: Needs you with a library hold, a request waiting for a reply and a fee to pay — The phone layout: a bottom tab bar, tables as cards

My fees: to pay, overdue, next due, paid this year; billed, approved aid, pending aid, net payable; the instalment schedule — Fees with aid and instalments, on test data

Student home on a laptop with Needs you, Coming up and In progress — A student's home: Needs you, Coming up, In progress

What an office sees

Each office has its own workspace and its own "Needs you": requests near their deadline, replies to read, payments to check, results to approve. Every request has a reference, an owner, a working-day deadline and a timeline.

Registrar's home: students blocked by a prerequisite, a request due within two days, replies to read, holds to review — The Registrar's home, on test data

Service desk listing requests with office, owner, status and deadline — The service desk

Settlements: payments affected by a provider outage, imported settlement files and what still needs checking — Settlement files and exceptions

Finance dashboard: collected against billed this term, financial aid approved, refunds due, settlement lines matched, overdue by age, payments by method — The Finance workspace dashboard: every figure from real records

What is in the product

Every area is demonstrated on test data. Where a connection is simulated, the card says so.

Student services

Requests and holds

Transcript, certificate, correction, waiver, withdrawal, exception requests. Routed to an office with a working-day deadline; evidence attached; sent back for correction; approved with an audit trail.

Finance

Payments that explain themselves

Pending, confirmed, failed, reversed, refunded. A repeated callback credits once. Provider outage: "not charged". Bank and gateway settlement files matched line by line; exceptions owned by a person.

Test gateway in the demo; SSLCommerz and Stripe need the university's accounts

Financial aid

Awards with two signatures

Proposed by Finance, approved by the Aid Office. Billed, approved aid, pending aid and net payable shown apart. Renewal criteria flagged for a person to decide.

Registration

Guidance, not just a form

A blocked prerequisite explained in a sentence, a bill preview before confirming, deadlines per programme and intake, waitlists in order, "ask for an exception" from the rule itself.

Academic planning

Transfer credit and degree audit

Lines decided one by one by the Registrar with a reason; approved equivalences suggested next time, never auto-applied. Audit against the catalogue year.

Exams and results

A trail for every change

Timetable clash detection for students, rooms and invigilators. Results approved before release. Grade changes keep the old value and the approver. Appeals with windows.

Admissions

Corrections and waivers tracked

Online application, dated fee catalogue, correction requests with history, waiver cases with a checklist, QR admit cards with print fallback, test rooms.

Help and policies

Answers that cite the page

Policies with an owner and review date. The assistant answers only from approved pages, shows the source and date, and hands over when unsure. Bangla and English.

Written answers need an API key; search mode works without

Integrations

Canvas and the records system

Rosters in, enrolment changes and released grades out. Approved results sent to the records system once, retried safely, visible to staff when they fail.

Mock records system in the demo until a university's interfaces are shared

Operations

Security and status

Two-factor sign-in with recovery codes, required per role. System status with alerts when a connection fails. Audit log filters for IT. A restore drill that proves backups restore.

AI, optional

Suggests; a person decides

Routing suggestions and summaries on the desk, drafted replies citing approved pages, form reading confirmed field by field, a daily note on unusual figures. Every output logged; figures not in the sources refused.

Off by default; needs an API key

Also

Workload, research, records

Faculty workload against a norm. Ethics reviews, grants and milestones. Document version history, retention rules and legal holds; nothing disposed of automatically.

Working alongside, in practice

The records system screen shows what was read, what is waiting to be sent, what failed and why. Staff retry; nothing is sent twice. Until a university shares its interface, a clearly labelled mock stands in, so the whole journey can be shown today.

The same goes for the rules: tuition per credit, instalments and late fees, refund windows, drop deadlines, the grade scale, probation and aid retention are entered as settings. Nothing is hard-coded. See how it is set up.

Records system screen: connection status, results sent when approved, sends waiting and failed, people linked across systems — The records system connector, with the test-data mock labelled as such

Evidence, not claims

What the build is checked against

327automated server tests pass on every change

6 of 6proof-of-concept scenarios pass end to end, with a written report per build

32 of 32accessibility page checks, keyboard and screen reader, desktop and phone

100students registering at once for 20 seats: no overbooking, waitlist in order

4.7 sto back up, restore into a scratch database and compare all 190 tables

Figures from the proof-of-concept run of October 2026 on a throwaway stack. The report is available on request.

Seven interface languages

English · বাংলা · සිංහල · தமிழ் · ខ្មែរ · ລາວ · Tiếng Việt

Each person chooses their language; dates and numbers follow it. Notifications and emails go out in the reader's language. Administrators can correct any translated wording and it applies at once.

See it on test data, then talk to us

Open the demo, or tell us about your university and we will show you the parts that matter to you.

See the demo Talk to us