Anubavam Wants
the Campus
to Talk

The revealing detail in a university software purchase is sometimes the paperwork. In October 2016, JIS College of Engineering placed an order with Anubavam for Creatrix Campus. The stated total was ₹920,000, including installation and tax, across a two-year engagement. The scope covered admissions, academics, faculty reporting, invoicing and accreditation work. The implementation plan allowed three to four months. Buying the software was only the beginning.

Anubavam occupies an interesting corner of the technology business. It builds software, sells a higher education platform and helps organizations change how they operate. Its flagship offers an answer to a familiar institutional puzzle: how can every department have a computer system while the institution still struggles to share information?

01 / The gap between two good systems

Founded in 2006 by Sivakumar Veerappan, Anubavam grew from web, mobile and content-management work into education software. Its public history places Creatrix’s education focus in 2014. That background matters. A company accustomed to building around a client’s requirements approached universities as collections of processes that needed connecting.

At a 2023 education summit in Malaysia, Veerappan described the pattern: “universities often approach their technological needs in a fragmented manner.” An admissions team buys a CRM. Teachers get a learning platform. Quality teams acquire accreditation tools. Each purchase addresses something real. Together, they can leave information stranded between departments.

In that diagnosis, the first thing to break is the handoff. A student crosses from applicant to enrolled learner, but the record must follow. An assessment becomes evidence of a learning outcome, but somebody must establish the connection. Software can automate a department while leaving people to carry information across its boundaries.

The first thing to break is the handoff.Our reading of Anubavam’s central argument

Veerappan also singled out faculty as underserved by systems designed chiefly around students. That broadens the problem from record keeping to the working life of an institution: teaching allocations, research, performance reviews and the rules connecting them.

02 / Follow the record, all the way through

Creatrix Campus now calls itself an Academic Operating System. The phrase describes its ambition: connect institutional activities through a shared platform. Its product range includes student information, admissions CRM, curriculum management, scheduling, examinations, learning management, student finance, faculty management, outcomes and accreditation.

Consider curriculum mapping. A pharmacy school must connect what it teaches with competencies and professional standards. Creatrix’s account of its work with the University of Otago describes curriculum mapping, placement planning, scheduling and faculty workload management. Those are specific academic jobs, rather than a generic promise to make education digital.

In that company-published account, Stephen Duffull, identified as the pharmacy school’s dean, praised its “curriculum mind mapping based on learning outcomes, competency standards, and graduate attributes.” The attraction is traceability. An academic team can examine how teaching, assessment and expected capabilities fit together, instead of treating each as a separate document.

The company’s more recent example is i-CATS University College in Kuching, Malaysia. Creatrix reports a student information system launch on April 6, 2026, intended to unify student data and academic operations. Its account also describes implementation support and training before go-live. The work includes getting people ready to use the system.

The institution can also keep a narrow starting point. A registrar may need reliable records; a quality team may need traceable evidence; a dean may need a clearer picture of teaching commitments. Creatrix markets these as different routes into the same platform. For a buyer, that makes the sequencing important: decide which department will prove the approach, and what evidence will justify adding the next.

03 / The invoice has a second lesson

The JIS order divided responsibilities. The college had to supply academic data, define fees and validate reports; Anubavam handled configuration, imports, testing and training in specified areas. The useful lesson is how much institutional knowledge a rollout requires from the buyer.

Today, Creatrix describes an annual subscription shaped by selected workflows, institution size, deployment requirements and support. Implementation, migration and training receive separate quoted line items. Buyers can begin with selected areas and add others. The business combines recurring platform revenue with the services needed to make adoption practical.

That model places Anubavam between a software vendor and an implementation partner. A useful buying exercise is to choose one journey, such as application to enrollment, and ask the vendor to demonstrate it using the institution’s actual rules. Include exceptions. A beautiful demonstration of an uncomplicated case tells procurement surprisingly little.

04 / AI arrives after the filing cabinet

Anubavam’s current offering extends beyond education. AI Data Studio addresses data connectivity, analytics and orchestration. Its low-code platform offers application building and workflow automation. Consulting services cover AI strategy, custom development, integration and cloud transformation. Higher education supplies the clearest example of the company’s broader interest in connected operations.

This puts Creatrix in a market that includes Ellucian and Workday Student, alongside institutions’ existing combinations of specialist applications. Integration is a crowded argument. Anubavam’s proposition rests on its mix of configurable academic workflows, outcomes and accreditation work, plus implementation services. Whether that fits depends on the institution’s requirements.

There is an instructive cultural detail here. In June 2025, Creatrix announced an internal learning session with Malaysian higher education practitioners about distance-learning regulation. Listening to registrars discuss accreditation is less glamorous than unveiling an AI feature. It is also a way to learn which rules software must accommodate.

The company’s approach requires departments to agree on definitions, ownership and permissions. If nobody can settle what a record means or who may change it, connecting systems can spread confusion faster. The copyable idea is to map the handoffs first, assign responsibility and test one complete workflow before expanding. Anubavam’s most useful promise begins with that ordinary work: helping the campus carry a record from one desk to the next.