Develop great apps, bots, and bridges. Focus on what you do best. Let the SDKs
do all the heavy lifting.
SDKs are pieces of software meant for developers, that take care of the
technical Matrix protocol calls behind the scenes. They allow them to focus on
where they can add the most value. If you're not a developer, this section of
the website is probably not for you.
There are two fundamental types of SDKs: clients and appservices. This
distinction is quite academical, and we went for a more pragmatic approach. You
will find below SDKs by type of product you may want to create (namely: clients,
bots, bridges). Don't be surprised if the same SDK appears in several sections!
If you are a developer and are not sure what the difference between clients and
appservices is, please head to the developers documentation.
Client SDKs are used to develop clients humans will interact with. They handle
all the Matrix heavy lifting and leave it up to the developer to implement a UI.
The SDK can support any of the maturity levels checked.
Select -
The client can support any of the licences checked.
Select -
The client must support any of the languages checked.
Bot SDKs are used to develop bots no humans will interact with. They handle all
the Matrix heavy lifting so the developer can focus on what the bot is actually
useful for.
The SDK can support any of the maturity levels checked.
Select -
The client can support any of the licences checked.
Select -
The client must support any of the languages checked.
Bridge SDKs are used to develop appservices meant to either connect a Matrix
community to a third party chat platform, or to exchange data with another
platform.
The SDK can support any of the maturity levels checked.
Select -
The client can support any of the licences checked.
Select -
The client must support any of the languages checked.
Select -
matrix-rust-sdk
Stable
The Matrix.org Foundation
Apache-2.0
Rust
An implementation of a Matrix client-server library in Rust.
