Jitsi Desktop: a desktop SIP and XMPP client that stopped moving

Jitsi Desktop is not Jitsi Meet, and the README opens by saying so

The first thing the README does is warn readers away from a mistake it expects everyone to make: do not confuse this project with Jitsi Meet, the browser conferencing solution behind meet.jit.si. Jitsi Desktop is a native desktop client written in Java. Its stated purpose is audio, video and chat over SIP, XMPP/Jabber and IRC, and the repository description says the same thing in one line. If you arrived looking for a free group video call link, this repository is the wrong stop.

This code base wants an installed client that logs into an existing SIP registrar or Jabber server and places a call. Different problems, different failure modes.

A Maven tree split into modules, native code and debian packaging

The top level tells you how the client is assembled. Alongside README.md and CONTRIBUTING.md sit debian/ for packaging, docs/, lib/, native/, resources/ and a modules/ directory, with pom.xml and .mvn/ at the root for the build and lombok.config for annotation processing. Having native/ next to lib/ indicates the client mixes Java code with native libraries rather than shipping as a single jar.

For someone deciding whether to fork, that layout is the answer. An .idea/ directory is committed, and the two workflow badges at the top of the README point at java.yml and installers.yml inside .github/workflows/, so build and packaging are automated in-repo.

Debian and Ubuntu need a hand written APT source, and RPM users get nothing

The install story splits three ways and only two of them work. On Windows and macOS you take the installers offered on the project's GitHub releases page. On Debian and Ubuntu a package repository exists at nexus.ingo.ch, but the README insists on the trailing slash after the distro name because that repository carries no components entry. Add the line exactly as it stands:

deb https://nexus.ingo.ch/jitsi-desktop-unstable/ <distro>/

Replace <distro> with your distribution codename and keep the slash. The package manager then needs to reload its index before the client appears in its list. The RPM section is a single sentence: no rpm packages are available, so Fedora, RHEL and openSUSE users have no package manager path. Pre-production builds sit in the unstable channel, which is a different track from a stable one: odd behaviour on such a build is the state of that channel, not the first thing to report.

The README says development has stopped and fixes depend entirely on contributors

The Support section is blunt. Jitsi Desktop is described as the heritage of Jitsi Meet, and the README says the project is not actively developed anymore, with improvements, bugfixes and builds coming entirely from community contributions. It also notes that some components are still in use elsewhere, pointing at Jigasi as an example. The last push landed on 2026-10-29.

Those two facts sit uncomfortably together. Commit activity without a core maintainer means a stranger's pull request is the only path to a fix, and review timing is unpredictable. Plan for unpatched defects rather than for a patch train, and read CONTRIBUTING.md before opening an issue, as the README directs.

Where Jitsi Desktop differs from the conferencing product people search for

Jitsi Meet is a web application you open in a browser and join by link, hosted at meet.jit.si. Jitsi Desktop is an installed client for protocol accounts. One is a service, the other is a program, and the choice between them is decided by where your calls already live.

If your calls sit on a SIP registrar or a Jabber server, the desktop client has a reason to exist. If you want to drop people into a browser room with no account, Meet covers that and Desktop does not. Treating Desktop as a lighter Slack would also be wrong: the documented protocols are SIP, XMPP/Jabber and IRC, not the workspace model.

Help for SIP configuration lives in a wiki and two forums, not in the repository

The Helpful Resources block gives you exactly three destinations: a documentation wiki, a community forum category for the desktop client, and an old website hosted at desktop.jitsi.org, which the repository also lists as the project homepage. Nothing about account provisioning, certificate handling or NAT traversal appears in the README itself.

That gap is the practical shape of the project. The code is a complete client, while the operating knowledge sits in three links.

Three named protocols, and documentation that stops at a wiki

Read the description literally. SIP, XMPP/Jabber and IRC are named, then a vague reference to other useful features. Only those three can be relied on from the README alone.

Check against your own account setup rather than the feature count. If your provider issues a SIP extension and password, the client has a place in the plan. If your requirement is a desktop chat client for a hosted team workspace, nothing here reaches it. Rollback is also undocumented, so there is no stated way back once a snapshot build is installed.

Editorial conclusion

Adopt Jitsi Desktop when your calls already live on a SIP registrar or a Jabber server, you run Windows, macOS or Debian, and you can carry the cost of unscheduled fixes yourself. Do not adopt it for a new deployment, and do not choose it as a lighter Slack: the documented protocols are SIP, XMPP/Jabber and IRC, and nothing in the repository covers hosted workspace chat. Verify the packaging channel first, because RPM platforms have no packages and a Debian install depends on a manually added APT source line with a trailing slash. If that step works and your provider hands out a SIP extension and password, the client has a place in your plan.

Frequently asked questions

Official sources

1. jitsi/jitsi on GitHub
2. License: Apache-2.0
3. Project website
4. README
5. Releases