GegoK12 · School ERP
GegoK12 school ERP: how it is built, and who customises it
GegoK12 is an open source school management system for K-12 institutions, written in Laravel by GegoSoft and in production since 2021. A single school can run it without us. This page is about the other case: when it needs to fit something the standard product does not do yet.
Looking for modules, features, pricing or the live demo?
Go to gegok12.com →- Stack
- LaravelPHP 8.4, MySQL
- Deployment
- Self-hostedYour server, your database
- Core licence
- MITFree, open source
- Add-on modules
- CommercialSource included
- In production since
- 2021Built in Madurai, India
- Mobile
- Parent & teacher appsIncluded with the core
Architecture
One school, one codebase, one database
GegoK12 is deliberately single-tenant. Each school runs its own installation against its own MySQL database, which means no shared schema, no data sitting alongside another institution's, and no upgrade that arrives because someone else needed it.
01
Modules are self-contained
Every module carries its own routes, migrations, models and views. That is why a school with no buses can switch transport off entirely, and why a new module installs into a running system without disturbing what is already there.
02
Settings before code
Academic years, terms, grade schemes, report card formats, fee structures and roles are configuration. Most board-specific requirements turn out to be a settings change rather than a fork, and we tell you which yours is before any work starts.
03
Written and maintained by one team
The engineers who release GegoK12 are the engineers who do the customisation work. There is no gap between product and services, which is why a change to core behaviour is a decision rather than an escalation.
Scope
A single school needs nothing from us
That is the honest position, and it is worth stating before anything else on this page. The open source core is complete enough for one school to install, configure and run on its own server without engaging GegoSoft at all.
Out of the box
One school, self-hosted
Download it, install it on your own server, configure academic years, classes and grade schemes, and run it. Free under the MIT licence, with no per-student fee and no time limit.
Add-on modules are bought individually if and when the school needs them, with the source code included either way.
Where we come in
Groups, trusts and chains
A multi-branch group is a different shape: branch structure, consolidated reporting across schools, and shared administration. That is a customisation rather than a setting, and it is work we have scoped before.
The same applies to anything the standard product does not do yet. Talk to us before you assume it cannot be done.
Customisation
What institutions actually ask us to change
Not a menu of services. These are the requests that come up repeatedly, and each one is normal engineering work because we hold the source and the people who wrote it.
Board-specific reporting
Report card formats, grading models and statutory returns that follow your board rather than a generic template. Some of this is configuration; the rest is code.
Local payment gateways
Fee collection through the gateway your school already banks with, rather than the one the product happened to ship with.
Integration with systems you already run
Accounting packages, biometric attendance devices, SMS providers, existing student databases. Built against the API rather than bolted onto the database.
Interface rebrand or replacement
Restyled to your institution, or a front end rebuilt against your own design system. Our team designs the screens before the API is written, then builds to what was agreed.
New modules
Something no school has asked for yet. Built as a self-contained module so it installs cleanly and survives future releases.
Migration off what you run now
Student records, historical academic years and fee ledgers moved across from a legacy ERP, spreadsheets or paper. Effort depends on the state of the source data.
If it is not on this list, ask anyway. The list describes what has been requested, not what is possible. A short call is usually enough to tell you whether something is a setting, a module, or a change to core behaviour we would rather not make.
Beyond K-12
Colleges and technical institutions are a customisation, not a different product
The academic model is where GegoK12 assumes a school. It is built around classes, sections, subjects and terms. Colleges, technical institutions and higher education run on departments, semesters, credits and electives instead.
That difference sits in the academic structure rather than in the rest of the system. Admissions, staff, attendance, fees, library, transport and communication all carry over largely intact. Reshaping the academic layer is work we have scoped before, and the same approach covers multi-branch groups and trusts.
One thing worth being clear about: GegoK12 is a system of record, not a learning management system. It holds students, attendance, examinations, fees and communication. It does not deliver courses or host teaching content. If that is what you are looking for, this is the wrong starting point and we will say so on the first call.
Next step
Two different questions, two different places
If you are evaluating the product itself, everything you need is on the product site. If you are evaluating whether it can be made to fit your institution, that conversation is with us.
Tell us the institution, what you run now, and the one thing the standard product does not do. That is enough for a first answer.