Availability
June 27, 2026 · View on GitHub
The canonical reference for where to get Ketesa.
Note: community-maintained and third-party entries can lag behind official releases. When in doubt, prefer the official release tarballs, containers, or the hosted instance.
Self-hosting or managed?
Ketesa is open source (Apache-2.0) and fully self-hostable; self-hosted and managed run the same admin UI. If you want full control of your stack and no recurring cost, and you have the capacity to run a Matrix server yourself, self-hosting is the right call. This repo plus the guides in the documentation index are everything you need.
etke.cc, the company that maintains Ketesa, matrix-docker-ansible-deploy, and the MASH playbook, also runs Matrix hosting as a managed service. It handles the operations for you (monitoring, updates, backups, TLS, support) and adds the etke.cc-exclusive features: live server monitoring, one-click server actions, in-app billing and support. Those need the etke.cc platform behind them, which is why they aren't part of the self-hosted build. Choose managed hosting if you'd rather not run the infrastructure yourself.
Official channels
| Channel | Type | Maintainer | Best for | Notes |
|---|---|---|---|---|
| etke.cc | Managed hosting | Official | Fully managed deployments | Ketesa is a core component installed by default |
| cloud.ketesa.app | Hosted instance | Official | No installation needed | Always on the latest development version |
| GitHub Releases | Static builds | Official | Self-hosting behind any web server | Includes ketesa.tar.gz and ketesa-subpath-admin.tar.gz |
| GHCR | Container image | Official | Docker and OCI-based deployments | Main image registry |
| Docker Hub | Container image | Official | Docker-first users | Mirrors the official container images |
| matrix-docker-ansible-deploy | Ansible integration | Official | Operators using the MDAD playbook | Maintained by the etke.cc team |
| etkecc/ansible | Ansible integration | Official | etke.cc-flavoured self-hosted automation | Maintained by the etke.cc team |
| Source repository | Source code | Official | Building from source or contributing | For custom builds and development checkouts |
Prebuilt distributions
Ketesa publishes two static distributions:
ketesa.tar.gzfor root path deployments such ashttps://admin.example.comketesa-subpath-admin.tar.gzfor/adminsubpath deployments such ashttps://example.com/admin
For custom prefixes other than /admin, build from source with yarn build --base=/your-prefix/
or pass the BASE_PATH Docker build argument.
Nightly and development builds
To get the latest unreleased changes:
- Use cloud.ketesa.app for the hosted development version
- Pull
latestorlatest-subpath-adminfrom GHCR or Docker Hub - Download
dist-rootordist-subpath-adminfrom the latest successful GitHub Actions run - Build the
mainbranch from source
Distro packages
| Channel | Type | Maintainer | Best for | Notes |
|---|---|---|---|---|
| Nixpkgs | Package index | @Defelo | Nix and NixOS users | |
| YunoHost | App catalog package | @Josue-T | YunoHost-based deployments |
Community-packaged options
| Channel | Type | Maintainer | Best for | Notes |
|---|---|---|---|---|
| IPFS | Mirror / alternative delivery | Fеnикs (@fenuks:sibnsk.net) | Content-addressed distribution | See the IPFS section below for addresses |
| ketesa | Arch Linux AUR | @Marcool04 | Arch users who prefer AUR packaging | maintained outside this repository |
| ketesa-git | Arch Linux AUR | @drygdryg | Arch users who prefer AUR packaging | maintained outside this repository |
IPFS
Maintained by Fеnикs (@fenuks:sibnsk.net)
Latest version: /ipns/ketesa.sibnsk.net
(dnslink key /ipns/k51qzi5uqu5dj91scsxoqu0ebmy7uqajrt9ohl98vs7fl7l429h0chgozk58i2)
Archive: /ipns/ketesa-archive.sibnsk.net
(dnslink key /ipns/k51qzi5uqu5dhxwc36sld1hn6jn935k71ww8rdyqomrnqcqucixy7re08qeu7z)
Want your package listed?
If you maintain a Ketesa package, mirror, or deployment integration, open a pull request. We welcome all distribution channels. Please include:
- the package or project link
- whether it is official, community-maintained, or a third-party mirror
- who maintains it
- any important caveats, especially if it still uses legacy
synapse-adminnaming