We build for the unglamorous parts of running an institute.
Acadelogy started from a familiar scene: an admissions register, a fee spreadsheet, a WhatsApp group and three people reconciling them at month-end. The software exists to replace that with one record per student and one ledger per rupee.
- Where we work
- Bengaluru, Karnataka
- Who we build for
- Indian institutes, colleges and education groups
- Deployment
- One platform, per-institution data boundaries
- Languages
- English today, Hindi next
The problem is rarely effort. It is fragmentation.
Most institute offices are not short of software. They are short of a single place where a student, a guardian, a fee plan, an attendance register and a receipt agree with each other. Every extra tool adds a handoff, and every handoff adds a chance to lose a payment or a parent.
Acadelogy takes the opposite approach: one platform, scoped by role, with the boundaries enforced in the API rather than the menu. Admissions, teaching, accounts and communication read and write the same records, so the group dashboard is not a report assembled by email at the end of the month.
India is not an afterthought in the design. Sessions run April to March, fee heads follow how institutes actually bill, receipts are numbered per institution, and online collection works with UPI through a gateway that confirms settlement server-side.
Three positions we do not compromise on.
Isolation is not a feature
A tenant is a data boundary. Institution scope is checked on every request, and files, exports and reports follow the same rule as the interface.
Money must be traceable
Fee balances derive from charges, allocations and adjustments. A receipt always points at a payment, and an online payment always points at a signed gateway event.
Teachers are not data entry staff
Attendance, homework and marks should fit inside a free period. If a workflow needs training and a manual, it belongs in the admin office, not the staffroom.
What ships in the platform now.
These modules are implemented and used end to end, not roadmap bullets. Physics is not the limitation; institute calendars are.
Deliberately not claimed: statutory board filings, payroll compliance and a full LMS. Those need verified requirements before we put them on a page.
- Tenancy and subscription limits
- Roles, permissions and scoped logins
- Academic years, classes, sections, subjects
- Students, guardians and admissions
- Staff directory and teaching assignments
- Attendance with corrections and audit
- Timetables and holiday calendars
- Fee plans, dues, receipts and concessions
- Razorpay online payments and webhooks
- Exams, marks and result publication
- Notices, homework and notifications
- Student, teacher and parent portals
- Institution and group dashboards, CSV exports
- Hostel blocks, rooms and monthly charges
- College programmes, semesters and credits
Shipped in order of what institutes actually ask for.
We add depth in the workflows that already exist rather than opening new modules that are half-finished.
Operational core
- Admissions and SIS
- Attendance and timetable
- Fees, receipts and UPI
- Exams and portals
- Group reporting
Automation and reach
- WhatsApp and SMS templates
- Fee reminders and late fees
- Certificates and ID cards
- Hindi interface
- Library and transport basics
Premium modules
- Payroll and HR
- Advanced analytics
- Placement workflows
- White label and SSO
- Validated compliance exports
Want the honest version of what setup looks like?
Tell us your campuses, board and how fees are collected. We will reply with the modules you need and the ones you can skip.