Pricing

One rate, every module, no per-seat arithmetic

Priced on enrolment and nothing else. Both tiers include all sixteen modules and every first-party integration — the choice between them is who operates the system, not what it is allowed to do.

Licensed self-hosted

You run it, on your servers, with your own operations team.

Request a quote per student, per year

Annual licence. Priced on enrolment, not on modules — turning on Contracts in March does not change the invoice.

Request a quote
  • All 16 modules and every first-party integration
  • Unlimited staff, students, buildings and external users
  • Single-tenant: your server, your database, your backups
  • Signed releases and a documented upgrade path
  • Deployment runbooks and full administrator documentation
  • Email support during business hours
  • Your team installs, upgrades, backs up and monitors it
  • No named contact or guaranteed response time — that is the Managed tier

Co-op & consortium

Several districts, an ESC or a service co-operative sharing one arrangement.

Request a quote quoted per consortium

Each district keeps its own instance and its own data. What is shared is the agreement, the onboarding and the rate.

Talk to us
  • Everything in Managed, for each member district
  • Separate single-tenant instances — no shared database
  • One agreement, one invoice, one renewal date
  • Banded per-student rate that improves with the size of the group
  • Consortium-wide onboarding and shared training sessions
  • Migration help from the systems members are leaving
  • Input on the roadmap proportional to the group

Quotes are written against your actual enrolment and the modules you intend to turn on in year one. We would rather scope it properly once than send a number that changes after the board approves it.

The honest version

Which tier you want

The licence fee is the same either way. The question is only whether your technology department has capacity to own another production system properly — backups tested, upgrades applied, certificates renewed — or would rather that were somebody else's pager.

Operations, not licences

Installs, upgrades, monitoring and restore drills. The work that is invisible when it is done and catastrophic when it is not.

Configuration that fits your district

Approval chains, thresholds, claim-to-role rules and site imports written for how your district is actually organised — the part that takes longest to get right alone.

A person who answers

A named contact with a written response commitment, instead of a forum thread and a hope. Districts under audit or in a crisis need this and cannot manufacture it in the moment.

Procurement questions

The ones that come up every time

Is there a free tier?

No. CampusLink is commercial software and every tier is licensed. What we do not do is hold features back: both tiers include all sixteen modules and every first-party integration. The difference between them is who operates the thing, not what it can do.

What happens to our data if we stop paying?

The data is unambiguously yours. It sits in a MariaDB instance you administer, on a server you own, and it can be exported or dumped at any point without asking us. What happens to the software licence itself at non-renewal is set out in the agreement — ask us to walk you through that clause before you sign rather than after, and we will put the answer in writing.

Can our security team review the source?

No — the source is not distributed, including under NDA. What we do provide is the architecture documentation, completed security questionnaires, the FERPA compliance summary and the accessibility statement. If your procurement process has a hard source-escrow or source-review requirement, tell us early, because that is a genuine constraint rather than something to discover in week six.

Do we pay per module?

No. Per-module pricing pushes districts into buying the three they are certain about and living without the rest — which recreates exactly the fragmentation the platform exists to remove. Enrolment is the only variable.

What does implementation actually involve?

A clean install is about thirty minutes. What takes real time is your data and your decisions: importing buildings and rooms, writing the SAML claim rules, agreeing approval chains and thresholds, and training staff by role. Plan on weeks, not months, and plan to start with two or three modules rather than sixteen.

Can we start with one module?

That is the usual path, and the recommended one. Most districts start with the IT helpdesk or facilities because the pain is sharpest and the data is easiest, then add modules a term at a time. Toggling a module on later needs no migration.

Do you charge for the PowerSchool plugin or the integrations?

No. Every first-party App is part of the platform, at both tiers. If your SIS is one we do not ship, talk to us — the API and webhook surface is documented and available to licensees, and where a new connector is genuinely needed we will scope it rather than pretend the generic API covers it.

Is there a discount for a multi-year agreement?

Yes, and it is worth asking about early. Districts that can commit for three years get a materially better rate, and it makes budgeting predictable on both sides.

What about migrating off our current systems?

Included in Managed onboarding for the common cases — device inventories, building and room lists, contract registers, asset histories in CSV or Excel. Genuinely awkward migrations get scoped and quoted honestly before anyone signs.

Something not answered here? Email [email protected] and you will get a straight answer, including when the answer is that CampusLink is not the right fit.

Get a quote you can take to the board

Send your enrolment, the modules you would start with, and your renewal timeline. We will come back with a written figure and what it covers.