This project aims at delivering a server implementation of both the core and IM parts of the XMPP protocol (as specified in RFCs 3920 + 3921).
“Vysper” is pronounced like in “whisper”.
XMPP is an open, secure and extensible instant messaging protocol which has evolved from Jabber.
It provides interoperability features for communication with other XMPP and non-XMPP servers.
It is used and supported by many IM applications, both client and server.
The protocol and its many extensions (called XEPs) are maintained by the XMPP Standards Foundation (XSF.
In addition to the basic protocol and many small extensions, Vysper currently comes with working implementations for
Multi-User Chat (XEP-0045) 
Publish-Subscribe (XEP-0060) 
You need Apache Maven 2, Maven 2.2.1 or later is recommended. Run
and you should find a number of JAR files in different target/ folders.
The different build artifacts are compiled in dist/.
There are different ways to run Vysper
A ready-to-run setup is created by the build in
you'll find start scripts for Unix/Mac and Windows.
This makes use of the Spring-based server runtime.
Main class is
and the bean configuration is located in
There is a non-Spring runtime, too:
The source code shows how the different components are plugged together.
It can serve as a template for integrating Vysper in any other application.
is built to make the server easily configurable and embeddable.
Vysper uses SSL encryption per default.
For this purpose, an TLS certificate is provided.
It is highly recommended to create and use a self-generated certificate!
There is one preconfigured user (firstname.lastname@example.org). The password for this
user is “CHOOSE A SECURE PASSWORD”. Please change this password before starting!
Please note that the domain vysper.org is not running an XMPP server.
If you go with the default setup and don't configure your own domain name,
please note that you have to configure your Jabber clients to force the host name
(for example the IP or localhost, depending on how you run it).
You can contribute by creating a new issue entry (or working on an existing).
For an overview of all VYSPER related issues, visit https://github.com/apache/mina-vysper/issues
Any contribution is highly welcome. It can be easily reviewed if it comes in form of a Github pull request.
Currently, all coding is done unit test driven. Well, at least it should be ;-)
Please find us on MINA'S developer mailing list email@example.com.