Self-Hosted vs Cloud (SaaS) Course Evaluation Software: A European Deployment-Model Buyer's Guide (2026)
For most European universities, EU-hosted SaaS delivers the same GDPR and data-residency outcome as self-hosting — without the security, patching, accessibility and uptime burden. Here is when self-hosting still wins, where EvaSys, LimeSurvey, Explorance Blue, Qualtrics and Koji sit, and why AI-native evaluation is effectively cloud-only.
Koji Education Team
Product · August 15, 2026
For most European universities in 2026, a cloud (SaaS) course evaluation platform hosted in the EU/EEA under a signed Article 28 data-processing agreement delivers the same GDPR and data-residency outcome as running the software on your own servers — without the security, patching, accessibility and uptime burden that self-hosting quietly transfers onto your own IT team. Self-hosting still wins in a narrow set of cases: a binding on-premise procurement mandate, an air-gapped or ministry-restricted network, or an institution that already operates a mature, well-staffed survey infrastructure it has good reason to keep. And one capability tilts the whole decision: AI-native evaluation — adaptive, AI-moderated student interviews — is, in practice, cloud-only.
This guide is about a decision that sits underneath the "which vendor" question and is often confused with it: where the software runs and who operates it. Two universities can buy the same product and deploy it in completely different ways, with completely different cost, risk and compliance profiles. Getting the deployment model right matters more than most feature comparisons, because it determines who carries the operational risk for the next seven years.
Deployment model is not the same question as "open source"
Buyers routinely collapse three separate decisions into one:
- Licensing — proprietary vs open source (is the code free to use and modify?).
- Deployment — self-hosted/on-premise vs vendor-hosted SaaS (where does it run?).
- Data residency — which country/region stores the personal data?
These are independent axes. You can self-host proprietary software (EvaSys on your own servers). You can buy open-source software as a managed cloud service (LimeSurvey Cloud). You can get EU data residency from a US-headquartered SaaS vendor. If you have already read our open-source and free course evaluation guide, this article is the orthogonal decision: not is it free, but who runs it and where.
The three deployment models, defined
On-premise / self-hosted. The institution installs the application on servers it owns or rents, inside its own data centre or virtual private cloud. Your IT team owns the operating system, database, backups, patching, penetration testing, TLS certificates, accessibility conformance of the deployed build, and uptime. You control the data locus absolutely.
Self-managed cloud (IaaS). A hybrid: you deploy the vendor's software onto cloud infrastructure you rent (Azure, AWS, a European provider such as OVHcloud or Hetzner). You still operate the application, but the hardware layer is someone else's. This is common for institutions that want EU residency and elastic capacity without a physical server room.
Vendor SaaS (managed cloud). The vendor operates the application as a multi-tenant or single-tenant service, handles all patching, scaling, monitoring and security certifications, and gives you an admin console and integrations. You sign a Data Processing Agreement under GDPR Article 28; the vendor is your processor. This is now the default model for new procurements across European higher education.
Deployment model comparison
| Attribute | On-premise / self-hosted | Self-managed cloud (IaaS) | Vendor SaaS (managed) |
|---|---|---|---|
| Who patches & secures it | Your IT team | Your IT team (app layer) | Vendor |
| Data locus control | Absolute | High (you choose region) | Contractual (EU/EEA residency clause) |
| Upfront cost | High (servers, setup) | Medium | Low (subscription) |
| Ongoing staff burden | High | Medium–high | Low |
| Security certifications | You must earn/maintain | Shared | Vendor holds (ISO 27001 / SOC 2) |
| Accessibility (EN 301 549) burden | You verify the deployed build | You verify the deployed build | Vendor's responsibility to conform |
| Time to first survey | Weeks–months | Weeks | Days |
| Uptime / disaster recovery | Your responsibility | Your responsibility | Vendor SLA |
| AI-native interviewing | Not available | Not available | Available |
| GDPR processor DPA needed | No (you are controller-operator) | No (infra DPA only) | Yes (Article 28) |
What self-hosting actually costs you
The subscription line item on a SaaS quote is visible; the operating cost of self-hosting is not, which is why self-hosting looks cheaper than it is. A fair total-cost-of-ownership comparison for an on-premise course evaluation platform has to include:
- Infrastructure: production and staging servers, database licences, storage, backup targets, and the refresh cycle.
- Security operations: OS and application patching on the vendor's release cadence, TLS certificate management, vulnerability scanning, and periodic penetration testing. A public-facing survey system that holds student personal data is an attack surface you now own.
- Accessibility conformance: the European Accessibility Act (in force 28 June 2025) and, for most public universities, the Web Accessibility Directive 2016/2102 require your course evaluation instrument to meet WCAG 2.1 AA via EN 301 549. With SaaS, conformance is the vendor's job and their VPAT/accessibility statement is your evidence. Self-hosted, you are responsible for verifying that your deployed build conforms — every upgrade. (See our accessibility compliance guide.)
- Availability: evaluation windows are spiky and deadline-driven. A server that falls over during the last 48 hours of the semester's evaluation window costs you response rate you cannot recover.
- Staffing: the hidden line. Someone has to own all of the above. In a small QA or IT team, that person is also doing five other things.
None of this makes self-hosting wrong. It makes self-hosting a staffed operational commitment, not a licence purchase — and that is the honest framing procurement often misses.
The GDPR myth: residency is not the same as on-premise
The most common reason European universities give for wanting to self-host is data protection. It is worth being precise, because the premise is usually mistaken.
GDPR does not require personal data to live on your own hardware. It requires a lawful basis, appropriate technical and organisational measures, and — for processors — a compliant Article 28 contract. A SaaS platform that (a) hosts in the EU/EEA, (b) signs an Article 28 DPA with the eight mandatory clauses, (c) names its sub-processors and flows the obligations down, and (d) holds ISO 27001 delivers a stronger documented compliance posture than most self-hosted deployments, because the security controls are certified and audited rather than assumed. Our Article 28 DPA and sub-processor checklist is the due-diligence artifact that makes this concrete.
Where self-hosting genuinely helps is the narrow question of data locus certainty — some ministries, medical faculties, or defence-adjacent programmes operate under rules that mandate on-premise or air-gapped storage. If that is your constraint, it is a real one. If your constraint is simply "GDPR", EU-hosted SaaS meets it.
Where the major platforms sit
Deployment options change; verify the current model in the vendor's contract before signing. As of publication:
| Platform | On-premise / self-hosted | Vendor SaaS / managed cloud | Notes |
|---|---|---|---|
| Koji | No | Yes (EU-hosted) | AI-native moderated interviews; cloud-only by design |
| EvaSys | Yes | Yes (managed cloud on Azure, ISO 27001, GDPR, daily backups) | Long-standing on-premise heritage in DACH; now offers both |
| LimeSurvey | Yes (Community, GPL) | Yes (LimeSurvey Cloud) | Open source; the classic self-host choice |
| Explorance Blue | Yes | Yes | Available in both cloud and on-premise deployments |
| Qualtrics | No | Yes (cloud only) | Enterprise SaaS; no on-premise option |
Two patterns stand out. First, the traditional SET incumbents (EvaSys, Explorance Blue) and the open-source option (LimeSurvey) all support self-hosting — which is exactly why data-sovereignty-conscious institutions in Germany, Austria and Switzerland have historically favoured them (see our German-market guide). Second, the two AI-forward platforms in the table (Koji, Qualtrics) are cloud-only, because the analytics and — in Koji's case — the conversational interviewing depend on models that run as a managed service.
When self-hosting is the right call
To be fair to the model this guide is skeptical of: choose self-hosted or on-premise when
- you have a binding on-premise or air-gapped mandate from a ministry, hospital trust, or research-security regime;
- you already run a mature, funded survey platform (a LimeSurvey or Qualtrics instance with dedicated staff) and course evaluation is one more study on it;
- your institution has an explicit policy that no student personal data may leave hardware it physically controls; or
- you need to modify the source for a workflow no vendor supports, which realistically means open-source self-hosting.
In every one of those cases, an AI-moderated interview platform is not the tool for you, and a self-hostable SET system or open-source survey engine is the honest recommendation.
When SaaS is the right call
For the large majority of European universities — those whose real constraint is GDPR compliance, accessibility conformance, integration with Canvas/Moodle/Banner/SITS, and not wanting to run yet another public-facing service — vendor SaaS with EU/EEA residency is the lower-risk, lower-total-cost choice. It moves the security, patching, accessibility and uptime burden to a party that is contractually accountable for it, and it is the only path to AI-native evaluation. If you want the deeper technical view of how a SaaS platform plugs into your identity and student systems, our integration and SSO technical guide covers SAML, SCIM and LTI 1.3.
A short deployment-model procurement checklist
- Is there a written mandate requiring on-premise/air-gapped hosting? If no, do not self-impose one.
- Do you have funded, named staff to patch, pen-test and accessibility-verify a self-hosted build for the full contract term?
- Does the SaaS option host in the EU/EEA and sign an Article 28 DPA naming its sub-processors?
- Does the vendor hold ISO 27001 / SOC 2 and publish an EN 301 549 / WCAG 2.1 AA accessibility statement?
- What is the uptime SLA during evaluation windows specifically?
- Do you need AI-moderated interviewing or advanced text analytics? If yes, the decision is effectively cloud.
Koji is a cloud-native, EU-hosted platform built around AI-moderated student interviews and automatic thematic analysis — the same interview engine that powers customer and user research on the main koji.so platform. It is the right fit when your constraint is compliance and qualitative depth, not a hard on-premise mandate. Where a genuine on-premise requirement exists, we will tell you a self-hostable SET system is the better match — because with this audience, honesty about fit is what earns the shortlist.
Frequently asked questions
Is self-hosted course evaluation software more GDPR-compliant than cloud?
Not inherently. GDPR requires a lawful basis, appropriate security measures, and an Article 28 contract for processors — not on-premise hosting. An EU/EEA-hosted SaaS platform with ISO 27001 and a signed DPA usually has a stronger documented, audited compliance posture than a self-managed server. Self-hosting only wins the narrow question of absolute data-locus certainty, which matters when a ministry or medical/defence rule mandates it.
Does self-hosting save money?
Often no, once you count total cost of ownership. The subscription price of SaaS is visible; the cost of self-hosting — servers, patching, penetration testing, accessibility verification every upgrade, disaster recovery, and above all dedicated staff time — is real but hidden. Self-hosting is an operational commitment, not a one-off licence purchase.
Can I get EU data residency without self-hosting?
Yes. Most established course evaluation vendors offer EU/EEA hosting regions. Combined with an Article 28 DPA that names sub-processors and, ideally, EU-only data storage, this satisfies data-residency requirements without you operating any infrastructure.
Why is AI-native course evaluation cloud-only?
Adaptive, AI-moderated interviewing and large-scale thematic analysis run on models that are delivered as a managed service. Self-hosted and on-premise deployments of traditional SET tools do not include this capability, so if AI-moderated interviews are a requirement, the deployment decision is effectively made for you.
Which vendors let me self-host?
As of publication, EvaSys (on-premise and managed cloud), LimeSurvey (Community edition, open source), and Explorance Blue (cloud or on-premise) support self-hosting. Qualtrics and Koji are cloud-only. Always confirm the current deployment model and residency in the contract before signing.
We have a mature LimeSurvey/Qualtrics instance already — should we still look at a dedicated tool?
If your existing platform meets your accreditation, accessibility and qualitative-depth needs and is well staffed, keeping it is reasonable. Look at a dedicated or AI-native tool when your constraint is thin open-text feedback, low response rates, or the manual cost of analysing comments — problems a static survey engine does not solve regardless of where it runs.