Run your own XMPP server
Prosody or ejabberd on a VPS that never asked for your name, email or ID. JIDs on your own domain, OMEMO between your clients, and a host that keeps no access logs.
- No email or ID
- IPv4 and a routed IPv6 /64
- Pay with Monero or Bitcoin
Why host your own Jabber server
Self-hosting moves your roster, presence and message archive onto a machine you control. On a no-KYC VPS, that machine is not tied to your name either.
Two mature servers
Prosody 13.0.7 is written in Lua, has one configuration file and ships nearly every modern extension as a core module. ejabberd 26.09, written in Erlang, is the usual choice for a clustered public service.
OMEMO needs no server module
The clients encrypt. The server stores device lists and key bundles over PubSub and PEP, and passes the encrypted messages through as ciphertext.
The metadata lives on the server
Rosters, presence, timestamps and the archive sit on whichever server carries your account. When you run that server, the record stays on your machine.
Calls need a relay next door
coturn relays Jingle calls when two clients cannot connect directly. Blackbox has a 10 Gbps port and 2 to 32 TB of transfer per 31 days, and relayed video counts toward it.
Signup asks for nothing
The account is a generated 32-character credential, with no email, phone or name. The whole site works with JavaScript off, checkout included.
Crypto settles on our own nodes
Bitcoin, Monero, Litecoin, Ethereum, USDT, USDC and more are received on nodes we run, with no outside payment gateway. Cards go through Stripe, and cash by mail works in any currency.
Quick start: Prosody 13 on Debian 13
Deploy Blackbox Core with Debian 13, SSH in as root and replace example.com throughout. The commands follow Prosody's own documentation.
# 1. Prosody's own apt repository. Debian 13 ships 13.0.1; this repo
# carries the current 13.0.x point release and its bug fixes.
apt update && apt install -y wget lsb-release ufw certbot coturn
wget https://prosody.im/downloads/repos/$(lsb_release -sc)/prosody.sources \
-O /etc/apt/sources.list.d/prosody.sources
apt update && apt install -y prosody
# 2. Ports. 5222 clients, 5269 federation, 5281 public HTTPS (file upload),
# 80 for the certificate challenge, 3478 and 5349 for TURN, plus coturn's
# default relay range. Components and the console stay on localhost.
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 5222/tcp
ufw allow 5269/tcp
ufw allow 5281/tcp
ufw allow 3478
ufw allow 5349
ufw allow 49152:65535/udp
ufw --force enable
# 3. One virtual host, a MUC component and a file upload component.
cat > /etc/prosody/conf.d/example.com.cfg.lua <<'LUA'
VirtualHost "example.com"
-- Registration is closed by default. Leave it closed and add users by
-- hand, or use invites, unless you mean to run a public service.
allow_registration = false
-- Default archive retention is one week. Keep more if clients need history.
archive_expires_after = "1y"
Component "conference.example.com" "muc"
modules_enabled = { "muc_mam" }
Component "upload.example.com" "http_file_share"
-- Defaults are a 10 MiB limit, a daily quota of ten times that,
-- and deletion after one week. Voice notes and photos want more.
http_file_share_size_limit = 100*1024*1024
http_file_share_expires_after = "31 days"
LUA
# 4. Add the modules mobile clients expect to modules_enabled in
# /etc/prosody/prosody.cfg.lua. All of these ship with Prosody:
# "mam"; "carbons"; "smacks"; "csi_simple"; "cloud_notify"; "turn_external";
# 5. Certificates for the domain and every component host, then import them
# so Prosody can read them without running as root.
certbot certonly --standalone \
-d example.com -d conference.example.com -d upload.example.com
prosodyctl --root cert import /etc/letsencrypt/live
printf '#!/bin/sh\n/usr/bin/prosodyctl --root cert import /etc/letsencrypt/live\n' \
> /etc/letsencrypt/renewal-hooks/deploy/prosody.sh
chmod +x /etc/letsencrypt/renewal-hooks/deploy/prosody.sh
# 6. TURN. Prosody never talks to the relay; it only hands clients a
# time-limited credential derived from this shared secret.
SECRET=$(head -c 32 /dev/urandom | base64)
cat >> /etc/turnserver.conf <<CONF
realm=example.com
use-auth-secret
static-auth-secret=$SECRET
CONF
systemctl enable --now coturn
# Print the two lines to paste into the GLOBAL section of
# /etc/prosody/prosody.cfg.lua, above the first VirtualHost. The secret has
# to match on both sides or every call fails authentication.
echo "turn_external_host = \"example.com\""
echo "turn_external_secret = \"$SECRET\""
# 7. Restart, create the first account, and check everything end to end.
prosodyctl restart
prosodyctl adduser you@example.com
prosodyctl check
prosodyctl check turn -v --ping=stun.conversations.imFrom a bare server to a working JID
DNS comes before certificates, certificates before federation, and TURN before anyone tries a call.
Point DNS at the server
Add an A record for the host, then SRV records on the domain in your JIDs: _xmpp-client._tcp.example.com. 3600 IN SRV 0 5 5222 xmpp.example.com. and the same shape for _xmpp-server._tcp on 5269.
Cover every hostname with a certificate
The domain, the MUC component and the upload component each terminate TLS, and Prosody wants a certificate matching every VirtualHost and Component name. Issue all three and set up the renewal hook before you go further.
Turn on what phones need
Stream management, message archive management, client state indication and push. Without them a phone misses messages while its radio sleeps. XEP-0479 lists push in its advanced mobile tier, for clients on platforms that do not allow long-lasting background connections.
Test the relay
prosodyctl check turn with --ping sends a small amount of data through your TURN server to an outside STUN server and waits for the reply. If that fails, calls ring and never connect. Plain prosodyctl check runs the configuration, DNS and certificate checks together.
Create accounts and keep the server paid
prosodyctl adduser creates one account at a time, which is what you want unless the service is public. Pick any term from 7 to 365 days, prorated by the day. The standard line adds 10% to terms under 31 days.
The extensions clients expect
XEP-0479, the XMPP Compliance Suites 2023, is the reference list. Prosody 13 ships a module for each of these.
| XEP | Prosody module | In Prosody | |
|---|---|---|---|
| Multi-User Chat | XEP-0045 | muc (a component) | Core module |
| Message Carbons | XEP-0280 | mod_carbons | Core since 0.10 |
| Message Archive Management | XEP-0313 | mod_mam | Core since 0.10 |
| Client State Indication | XEP-0352 | mod_csi_simple | Core since 0.11 |
| Stream Management | XEP-0198 | mod_smacks | Core since 0.12 |
| HTTP File Upload | XEP-0363 | mod_http_file_share | Core since 0.12 |
| Push Notifications | XEP-0357 | mod_cloud_notify | Core since 13.0 |
| External Service Discovery (TURN) | XEP-0215 | mod_turn_external | Core since 0.12 |
The core-since versions come from Prosody's bundled module list, linked in the next section.
Releases, ports and storage
XMPP is a core spec plus a stack of extensions that clients assume the server has. XEP-0479 sets the baseline: an IM server carries RFC 6121 plus Multi-User Chat, Message Carbons and HTTP File Upload, with Stream Management, Message Archive Management and PEP native bookmarks (XEP-0402) in the advanced tier. Mobile clients add Client State Indication and Push, and calling clients use External Service Discovery to find the TURN server. Prosody's bundled module list shows the release that brought each one into core.
Prosody 13.0 came out on 17 March 2025 (release notes). It brought mod_cloud_notify and several other popular community modules into Prosody itself, and added a roles and permissions framework and full DANE support for server-to-server links. As of November 2026 the stable release is 13.0.7, a bugfix release from 23 September 2026, and Prosody publishes its own Debian and Ubuntu repository. ejabberd, the Erlang alternative, is at 26.09 from 30 September 2026, a security release its maintainers ask everyone to install as soon as possible.
The default port table is 5222/tcp for clients, 5269/tcp for federation, 5281/tcp for public HTTPS and 5000/tcp for the file transfer proxy, with components and the console on private interfaces. The DNS page gives the SRV records verbatim. Certificates have to match every VirtualHost and Component name, and prosodyctl cert import installs them; Prosody documents it as the certbot renewal hook. mod_http_file_share defaults to a 10 MiB file limit, a daily quota of ten times that and deletion after a week, which photos and voice notes use up quickly.
Prosody's TURN guide names coturn and eturnal as the tested relays and states that "Prosody never communicates with the TURN server." It only hands out credentials, built from turn_external_host and a turn_external_secret that matches static-auth-secret in turnserver.conf (coturn setup). coturn's shipped turnserver.conf documents its defaults: 3478 for UDP and TCP, 5349 for TLS, and a relay range of 49152 to 65535.
What OMEMO does not hide
OMEMO (XEP-0384, still Experimental at version 0.9.1 of 6 April 2026) gives one-to-one and group chats Double Ratchet encryption, so "nobody else except sender and receiver is able to read the content of a message". Its threat model adds that the protocol does not protect against attackers who rely on metadata and traffic analysis.
The server still holds the roster, sees presence, records who sent a stanza to whom and when, and keeps the archive. mod_mam deletes per-user archives after one week by default, so pick the retention on purpose. Push leaks as well: mod_cloud_notify sends a plain wake-up by default, and warns that including message bodies without end-to-end encryption "may expose your message contents to your client developers and OS vendor". To federate with XMPP servers that run as onion services, the community module mod_onions connects through a local Tor SOCKS5 proxy on 127.0.0.1:9050, the same Tor daemon a Tor node runs. Its onions_tor_all option sends every server-to-server connection through Tor, though the module notes that this skips SRV lookups and fails for many servers.
All of that sits with whoever runs the machine, and on a self-hosted server that is you. We ask for nothing at signup, keep no web access logs, and PGP-sign our warrant canary. On Blackbox, the measured boot guide shows how to check what the server booted before you unlock its disk. On the standard line the panel can reset the root password, so trust it as you would any panel-managed server. If you want rooms, threads and a larger client ecosystem, the Matrix VPS page covers Synapse on the same plans.
Keep the archive on Blackbox
Your archive database, rosters and account keys live in the server's memory and on its disk. On Blackbox the CPU encrypts that memory, and the disk can be encrypted with a passphrase that never reaches us.
- No guest agent and no virtio-serial channel, so the host has nothing to run commands through.
- AMD SEV-SNP with debugging disabled, so a host-side memory dump of the archive database shows only ciphertext.
- Optional LUKS2 full-disk encryption on Linux images, unlocked by you over SSH into the initramfs at boot.
- Measured boot: check the firmware and kernel with blackbox-verify before you type the passphrase.
- One IPv4 address and a routed IPv6 /64. We can still power the server off, but we hold no key to its memory, and with disk encryption on, none to its disk.
Plans
| Plan | vCPU | RAM | NVMe | Traffic | Where | Price |
|---|---|---|---|---|---|---|
| Blackbox Core | 2 | 4 GB | 50 GB | 4 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order) | $9.99/mo |
| Blackbox Plus | 4 | 8 GB | 100 GB | 8 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order) | $19.99/mo |
| Blackbox Max | 6 | 16 GB | 200 GB | 16 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order) | $39.99/mo |
| Blackbox Ultra | 8 | 32 GB | 400 GB | 32 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order) | $79.99/mo |
If your server relays a lot of video, the standard VPS line has unmetered bandwidth. It has no IPv6 and no memory encryption.
Deploy your XMPP server
Pay with Monero, Bitcoin or a card, then follow the quick start above to get Prosody answering on 5222.
Questions
How much VPS does an XMPP server need?
Very little CPU. Prosody and ejabberd are event-driven and spend most of the day holding idle connections open. Blackbox Core, with 2 vCPU, 4 GB of RAM and 50 GB of NVMe for $9.99 a month, is plenty for a personal or small-group server.
Prosody or ejabberd?
For one domain on one server, Prosody is the shorter path. As of November 2026 its stable release is 13.0.7. ejabberd, at release 26.09, is the usual pick when a service has to run as a cluster across several machines.
Does the server need special support for OMEMO?
No OMEMO module is needed. The clients do the encryption, and the key material travels over PubSub and PEP, which need persistent item storage and an open access model on those nodes. Prosody handles that out of the box and stores ciphertext it cannot read.
Which DNS records do I need?
An A record for the host, plus SRV records for _xmpp-client._tcp and _xmpp-server._tcp on the domain in your JIDs, pointing at ports 5222 and 5269. You also need certificates for the domain and for each component host.
Do I need a TURN server for audio and video calls?
In practice, yes, because most clients sit behind NAT. Run coturn or eturnal on the same server and open 3478 and 5349, plus coturn's default relay range of 49152 to 65535 UDP.
Can Servury read my messages?
Messages encrypted with OMEMO are ciphertext to everyone outside the chat, including whoever runs the server, which is you. Everything else depends on the server. On the standard line the panel can reset the root password, so treat it like any panel-managed server. On Blackbox there is no guest agent, AMD SEV-SNP encrypts guest memory, and if you encrypt the disk, the passphrase never reaches us.
Does IPv6 work?
On Blackbox, yes: every server has one IPv4 address and a routed IPv6 /64. The standard VPS and VDS line is IPv4 only. IPv6 helps phones on IPv6-only mobile networks.
Is running a public XMPP server allowed?
Yes, it is ordinary self-hosting. Illegal content, fraud, phishing and spam are prohibited, and a person reads every abuse report, so keep a close eye on open registration. Cryptocurrency mining is not allowed on any Servury server.
Guides on this topic
- Self-Hosted Apps vs SaaS: Why Running Your Own Nextcloud, Vaultwarden, or Pi-hole Beats Trusting a Third PartyWhat changes when you run your own Nextcloud, Vaultwarden, or Pi-hole instead of trusting a SaaS provider, and how an anonymous VPS narrows the last privacy...
- How to Set Up a Self-Hosted VPN with WireGuard on a VPSTen minutes from a fresh Ubuntu server to a WireGuard VPN you control: keys, config, forwarding, firewall, a phone client by QR code, and the two settings that...
- Why Developers Are Self-Hosting AI Agents and LLMs Instead of Relying on Cloud AI PlatformsWhy developers are moving language models and agents onto their own VPS, keeping prompts, documents, and agent memory private instead of sending them to a...
- Best Anonymous VPS Hosting ProvidersSix anonymous VPS providers compared and re-verified in September 2026: signup requirements, logging, Monero and crypto support, locations, and real starting...