About
Built by people who had to run the district too
CampusLink is made by Melton Electronics for public school districts. It did not start as a product idea. It started as two applications that were already in use, and the realisation that adding a third department would mean maintaining a third copy of the same district.
How it happened
Unification was the product decision
Two applications, two of everything
Rackline handled custodial inventory. ReserveIt handled facility rentals. Each had its own user table, its own buildings list, its own audit log, its own auth stack, and its own port. Two systems, two sources of truth about the same district — and every new department wanted a third.
Unify rather than integrate
Integrating them would have meant a third system syncing the first two, with three places for a building to be spelled differently. Instead both were rebuilt into one schema: one core_users, one core_sites, one audit log, one RBAC engine, one session.
Sixteen modules on that foundation
Every module added since — helpdesk, facilities, safety, HR, transportation, records, contracts, badging — went onto the same directory and the same permission model. Adding the seventeenth costs a fraction of what adding the second did. That is the entire argument for having done it this way.
How we work
Six positions we do not trade away
These are not values on a wall. Each of them costs something — engineering time, revenue, or a comfortable answer in a sales call — and each is worth it.
The district owns the data
Single-tenant and self-hosted, on infrastructure you control. Not because it is easier — it is not — but because student records should not sit in a vendor database that a district cannot inspect, migrate or keep.
A record beats a recollection
Almost every module exists to turn something that used to be remembered into something that is written down: who approved it, when, and on what basis. That is the whole product, applied sixteen times.
Customers are configuration, not forks
Every district runs identical code. If a requirement cannot be expressed in a profile, we extend the profile for everyone rather than branch for one — which is why a fix on Tuesday reaches every district on Tuesday.
Say the uncomfortable part
Self-hosting means you own the backups. Free-text fields can leak student names. We are not WCAG certified. A vendor who omits these is describing a surprise, not a service.
Friction where it belongs
Four-eyes co-sign, MFA on irreversible steps, expiring grants. Controls that can be talked around in the moment are not controls, and the moment is exactly when they are tested.
Documented in plain language
Help written per role rather than per feature, runbooks that assume competence and do not pad, and a decision log recording what was rejected and why. Documentation is where most district software quietly gives up.
Fit
Who this is for — and who it is not
CampusLink suits a public school district that runs its own technology department, has a SAML identity provider, and is tired of the seams between departments.
- Districts running several disconnected systems that each know a different half of the truth
- Districts that need an audit trail to survive a board question, a records request or an inspection
- Districts with data-residency or procurement constraints that rule out multi-tenant SaaS
- Co-operatives and ESCs that want one arrangement across member districts
Probably not a fit
- A single school with no technology staff and no identity provider. The platform assumes both.
- Anyone looking for a student information system. CampusLink integrates with your SIS; it does not replace it.
- A district that needs one department solved brilliantly and cares nothing for the rest. A specialist tool will beat us on depth in its one area.
Melton Electronics
A technology company working with K-12 districts. CampusLink is our platform: we build it, we operate it for districts that would rather not, and we run it against real district workloads rather than a demo dataset.
- Product CampusLink K-12 operations platform
- Licence Proprietary — commercial licence, per district
- Model Licensed self-hosted, or fully managed on your infrastructure
- Sales [email protected]
- Support [email protected]
- Security [email protected]
Tell us the seam that hurts most
Most districts can name it in a sentence — the queue nobody owns, the approval that happens by email, the number nobody trusts. Start there and we will show you that part first.