Why independent creators and educators are moving away from Unity and Unreal
There is a quiet but accelerating shift happening in European universities, design schools and public sector creative programmes. Institutions that spent the last decade building curricula around Unity, Adobe, and Autodesk are actively evaluating alternatives - not because those tools stopped working, but because the terms on which they work have changed.
The institutional problem with proprietary 3D tools
Universities and public sector creative teams have always had a complicated relationship with proprietary software. For years, the capability advantage of tools like Unity, Unreal and Autodesk Maya outweighed the costs and risks of proprietary dependency. Three things have changed that calculation.
Licensing volatility
Unity's announcement of the Runtime Fee in September 2023 - a per-install charge retroactively applied to games already shipping - sent a clear signal to any institution that had built infrastructure on Unity: the terms of your dependency can change unilaterally, at any time, without notice. For a university that had built a three-year game design curriculum around Unity, this was not an abstract concern. It was a demonstration of what vendor lock-in actually means in practice.
Autodesk's shift to subscription-only licensing in 2021 created similar pressure. Institutions that had purchased perpetual licences found themselves facing mandatory recurring costs with no opt-out. Educational licensing discounts exist, but they expire, they have conditions, and they require ongoing negotiation with a vendor whose interests are not aligned with yours.
Data sovereignty and GDPR compliance
European institutions operate under GDPR and increasingly under the EU Data Act, which creates specific obligations around where data is processed, stored, and by whom. Cloud-based proprietary tools - where project files are stored on US-based servers, processed by US-based companies, and subject to US legal jurisdiction - create compliance complexity that legal and IT departments are increasingly unwilling to absorb.
Digital sovereignty as EU policy
The European Commission's Digital Decade policy targets include explicit goals around open-source adoption in public sector infrastructure. The EU Open Source Strategy and its successor framework explicitly position open-source software as a strategic priority for public institutions. Institutions applying for EU digital innovation funding increasingly find that open-source tooling is a criterion, not a preference.
What European educators specifically need from 3D tools
The requirements of a university game design programme or a public sector digital production team are different from those of a commercial studio. Understanding those differences explains why tools built for commercial production are often a poor institutional fit.
- Accessibility without installation barriers - browser-based tools eliminate IT overhead and work on any device
- Fast time-to-result for teaching - students need a visible, shareable result in their first session
- Shareable outputs that work for everyone - a URL anyone can open replaces the build-and-host overhead
- Institutional data control - student work must belong to students and the institution, not the platform
When the output is a URL anyone can open in a browser, the feedback loop between student, teacher, and peer reviewer changes completely. Work-in-progress sharing, critique sessions, and portfolio presentation all become frictionless.
Performance benchmarks: what 'lightweight' actually means
The word 'lightweight' appears in a lot of marketing copy for 3D tools. It is worth being specific about what it means in practice, because the numbers matter for institutional deployment.
anitya scenes are built on Godot's WebGL export pipeline. Published scenes are self-contained WebGL applications. The following benchmarks reflect production data from Q1 2026, not best-case theoretical performance.
Because scenes run client-side in the browser, there is no infrastructure cost that scales with concurrent viewers. A scene shared with 1,000 people simultaneously has the same infrastructure footprint as a scene shared with 1. This is a meaningful difference from server-rendered approaches like Unreal's Pixel Streaming.
The open source advantage: why Godot specifically matters
anitya is built on Godot, which is open source under the MIT licence and maintained by the Godot Foundation - an independent non-profit based in the Netherlands. For European institutions, this combination of facts has specific value.
EU-based governance: The Godot Foundation is a Dutch foundation, subject to EU law and governance. The engine's development roadmap is determined by the community and the foundation, not by a US-listed corporation's quarterly earnings requirements.
MIT licence - no usage restrictions: There are no per-seat licence fees, no runtime fees, no audit rights for the licensor, and no conditions on commercial use. An institution can build its entire 3D curriculum on Godot-based tooling without a licence agreement.
Auditability: For public sector institutions with security and compliance requirements, the ability to audit the source code of the tools you run is increasingly a procurement requirement. Proprietary engines cannot satisfy this requirement. Godot can.
No platform risk: The Godot engine cannot be acquired and relicensed. It cannot introduce a runtime fee. Even if the Godot Foundation ceased to exist, every institution using Godot would retain full rights to the software under the MIT licence. This is a categorically different risk profile from Unity or Unreal.
How European institutions are using anitya today
Game design and interactive media courses: Students build and publish interactive 3D prototypes as course deliverables. Browser-based publishing means project presentations, peer critiques, and portfolio reviews all happen through shared URLs - no builds, no executables, no IT overhead.
Architectural visualisation for design schools: Architecture and interior design students use anitya to create interactive walkthroughs of spatial concepts. Fast load times and mobile compatibility mean work can be reviewed on a phone during a studio critique.
Digital heritage and cultural institutions: Museums and heritage organisations create browser-accessible 3D experiences for collections and exhibits. The no-install requirement means public audiences can access experiences without technical barriers.
EU-funded digital innovation projects: Several projects funded under the European Media Programme and Horizon Europe digital strand use anitya as the publishing layer for interactive 3D content, specifically because the open-source foundation and data ownership model satisfy funding body requirements around open access and data sovereignty.
Teacher training and digital literacy programmes: The low barrier to entry makes anitya suitable for digital literacy programmes targeting educators who are not engineers. Participants consistently report being able to produce a publishable result in their first session.
The data ownership question
One of the most consistent concerns raised by European institutions evaluating 3D tools is data ownership. The question takes different forms - 'where are our student files stored?', 'can we export our content if we stop using this tool?', 'does the platform claim any rights over content created on it?' - but they all resolve to the same issue: who owns the work?
anitya's answer is structurally enforced, not just policy-stated. All content is exportable in open formats. The platform does not claim ownership of or licence rights to user-created content. The underlying engine is open source. A scene built in anitya today can be exported and run independently of anitya's servers.
For institutions evaluating tools under GDPR, the EU Data Act, or internal data governance policies, this architecture simplifies the compliance question considerably.
Practical considerations for institutional adoption
Getting started costs nothing: anitya has a free tier that includes scene creation, AI asset generation credits, and publishing to a unique URL. For a pilot module or a single course, there is no procurement process and no IT deployment.
No installation required: anitya runs entirely in the browser. Students need a modern browser and an internet connection. There is no software to install, no system requirements to verify, and no IT ticket to raise.
Student work is portable: All student projects can be exported. If a student or institution stops using anitya, their work leaves with them in open formats.
GDPR compliance: anitya operates under EU data protection law. User data is not sold to third parties. Content created on the platform belongs to the creator.
Educational pricing: For institutions requiring team features, custom domains, and higher generation volumes, educational and institutional pricing is available.
Frequently asked questions from institutional decision-makers
Can anitya replace Unity in a game design curriculum?
For courses focused on interactive experience design, rapid prototyping, and web-based game development - yes, for the majority of learning outcomes. For courses specifically preparing students for studio employment on commercial console and PC titles, Unity or Godot directly remain more appropriate for professional workflow preparation. Many institutions are finding a hybrid approach useful: anitya for foundation modules and rapid prototyping, direct engine work for advanced students targeting industry employment.
What is the maximum scene complexity we can publish?
Scenes with up to approximately 500k total polygons, 20 active lights, and 50MB of compressed assets run well across target devices. For most educational and institutional use cases - interactive architectural models, game prototypes, digital exhibition pieces - this ceiling is not a constraint. Very large heritage digitisation projects with photogrammetric assets at full resolution will require asset optimisation before web publishing.
Is anitya suitable for students with no 3D experience?
Yes. The tool is specifically designed for creators without a game engine background. Students with no prior 3D experience consistently produce publishable scenes in their first session. The AI asset generation pipeline further lowers the barrier - students who cannot yet model in Blender can still create and populate a 3D scene using text prompts.
How does anitya handle GDPR and institutional data requirements?
anitya operates under EU data protection law. Project data is stored in accordance with GDPR requirements. Content belongs to the creator and is fully exportable. We are happy to discuss data processing agreements (DPAs) with institutions that require them for procurement.
What does institutional licensing look like?
We offer educational and institutional licensing at preferential rates, including department site licences and multi-year arrangements for public sector organisations. Contact us at anitya to discuss your institution's requirements.
The broader shift
The move toward open-source 3D tools in European institutions is part of a larger pattern. The European Commission's push for digital sovereignty, the maturation of open-source alternatives to every major creative tool, and the demonstrated platform risk of proprietary dependency are all converging at the same moment.
The practical question is not whether open-source tools are good enough - they are. The question is how to make the transition without disruption, and which tools offer the capability, the support, and the institutional fit to make the switch worth doing.
For 3D creation and publishing on the web, anitya is built specifically to answer that question for European educators and creators.
anitya is a browser-based 3D creation and publishing platform built on Godot open-source technology, operated under EU data protection law. Free to try at anitya.space. For institutional and educational licensing enquiries, contact us directly.