Video is one of the most powerful building blocks of the modern web. But the infrastructure behind it is still largely controlled, opaque, and dependent on a handful of platforms.
Embedding video today often means relying on platforms that track users, lock you into proprietary ecosystems, and operate outside your control. What starts as a simple embed quickly becomes a dependency - technically, legally, and operationally.
For many organizations, that dependency is no longer acceptable. And across Europe, we notice the shift in conversation. From convenience to control. From features to sovereignty.
At Mave, we believe video infrastructure should evolve with that shift.
Mave was built to make video simple: a lightweight embed, fast performance, no cookies, and fully hosted in Europe. But simplicity alone is not enough.
As organizations grow, new questions emerge: can we move away if we need to? Can we verify how it works? Or are we locked into a system we don’t control?
These are not just technical questions, they are questions about autonomy.
For a long time, digital sovereignty was reduced to one thing: where your data is stored. But location alone does not create control.
True sovereignty is broader. It requires:
This is where most video platforms fall short today. They may host data in Europe. But the underlying systems remain closed, opaque, and difficult to leave. And that’s where sovereignty breaks.
We are not starting from scratch. Parts of Mave are already open source, like our frontend library that powers our player and our privacy-first analytics tool, which handles how views are processed.
We also build on and learn from strong open-source examples that already prove what this can look like. Projects like FFmpeg are part of the technical foundation of modern video infrastructure, and we rely on them intensively. At the same time, product-focused companies like Proton, Nextcloud, and Cal.com show that openness can also be part of building trusted, usable software that organizations depend on every day.
We are not “switching to open source” overnight. We are building toward a more open, transparent, and portable video infrastructure as a whole. And we do it step by step. Because openness, in this context, is not about making code public alone. It is about reducing dependency, improving inspectability, and giving organizations real control over how video is delivered.
For us, moving toward a more open Mave is grounded in a few clear principles. These principles guide how we design Mave - and how we reduce dependency at every layer of the stack.
Video infrastructure should not trap you.
By prioritizing open standards, we ensure that integrations remain flexible, interoperable, and future-proof. Teams should be able to integrate Mave into their stack and adapt or move when needed.
No lock-in by design. For example: we lean heavy on a protocol like S3, so you could use Garage or Alarik for example to maintain your files.
Closed systems create uncertainty.
We believe organizations should be able to understand how their video infrastructure works, from delivery to data handling.
That’s why we are working toward greater transparency in:
Transparency doesn’t require everything to be public, but it does require everything to be understandable.
Openness does not mean complexity. It means choice.
While we move toward a more open infrastructure, Mave will always offer a fully hosted solution, optimized for fast, reliable video delivery within Europe.
For most organizations, this is the simplest path:
At the same time, we design our platform so you are never dependent on us in ways you can’t control. Because being a partner means more than providing technology. It means offering clarity, reliability, and the freedom to choose what works best for your organization.
Perhaps the most important principle is this:
You should always be able to move.
Whether it’s your data, your workflows, or your integrations - portability should be a given, not a risk.
We design Mave so that:
Because true control only exists when leaving is an option. If you can’t leave, you don’t control it.
The need for sovereign digital infrastructure in Europe is growing.
Organizations are re-evaluating their dependencies. Governments are defining new standards. Teams are looking for technology that aligns with European values - not just in compliance, but in design.
This shift is not about rejecting global technology.
It is about building infrastructure that is:
Video should be part of that foundation.
Open source is often treated as a label. But in reality, it is part of something bigger.
As AI makes code easier to generate and replicate, the value of code alone is decreasing. What matters more is how infrastructure is designed, operated, and trusted over time.
For Mave, that means the real value is not in keeping code hidden. It is in the way we build: with privacy-first principles, reliable European hosting, clear technical choices, and a product organizations can trust.
For Mave, openness is a strategic choice. A direction toward infrastructure that organizations can trust. That developers can understand. And that remains under their control.
We are just at the start of this journey. In the coming months, we will take concrete steps toward a more open Mave. We’ll be sharing more, opening more, and making the platform easier to understand and integrate on your terms.
Not all at once, but deliberately.
Because building truly sovereign infrastructure takes more than releasing code. It requires rethinking how control, transparency, and simplicity come together.
That is the direction we’re building toward: an open, European video infrastructure.
1
2
3
4
5
<script type="module">
import { Player } from "https://cdn.video-dns.com/npm/@maveio/components/+esm";
</script>
<mave-player embed="ubg50Cq5Ilpnar1"></mave-player>
<script type="module">
import { Player } from "https://cdn.video-dns.com/npm/@maveio/components/dist/react.js";
</script>
<Player embed="ubg50Cq5Ilpnar1"></Player>
<script type="module">
import { Player } from "https://cdn.video-dns.com/npm/@maveio/components/+esm";
</script>
<mave-player embed="ubg50Cq5Ilpnar1"></mave-player>