Open source

You don't have to trust us. Read it.

The plugin running on your server and the relay binary are open source, licensed AGPL-3.0. You can read exactly what we do with your server's connection — line by line.

finderwave / jellyfin-plugin AGPL-3.0

Open-core authentication and sharing layer for self-hosted Jellyfin. Plex-like UX, zero compromise on privacy.

Source on GitHub AGPL-3.0 C#
install the plugin
# add the repository to Jellyfin's plugin catalog
$ jellyfin repo add https://plugins.finderwave.io
Repository added
$ jellyfin plugin install finderwave
Verified signature · sha256:9f2c…a1b7
Plugin installed · v1.0.3
Source matches the published binary. Reproducible build.
Why it's open

Openness, not just security.

A privacy product you can't inspect is a promise, not a guarantee. So the parts that touch your server are auditable.

Auditable

Read what the plugin sends and receives. The connection logic is in the open — no hidden calls, no opaque blobs running on your hardware.

No lock-in

It's AGPL-3.0. Fork it, self-host the control plane, run the relay binary yourself. You're never trapped on our infrastructure.

Reproducible

The published binary matches the source. Build it yourself and compare the hash. The install verifies the signature before it runs.

Open core, honestly

What's open, and what isn't.

"Open core" means some things are open and some aren't. Here's the line, drawn plainly.

Open source (AGPL-3.0)

Everything that runs on your hardware.
  • The Jellyfin server plugin.
  • The relay binary you can self-host.
  • The device-linking and Quick Connect flows.
  • The auth handshake protocol spec.

Hosted by us (proprietary)

The managed service you can choose not to use.
  • The hosted control plane and dashboard.
  • Our managed relay edge network.
  • Billing and account management.
  • Business SSO connectors and audit export.

GNU AGPL-3.0

plugin + relay binary

The Affero GPL means anyone who runs a modified version as a network service has to share their changes back. We chose it deliberately: it keeps the auth layer honest. If someone forks Finderwave and hosts it, the community gets their improvements too — and you always have the source to the thing guarding your server.

Read LICENSE Contributing guide Security policy

Your Jellyfin server deserves better than shared passwords.

Get started free