Berty is an open, secure, offline-first, peer-to-peer and zero trust messaging app
TLDR : Install it!
To compile and run the mobile application on your device, see js/README.md.
go run or
go install the CLI tool located in
The two main command line utilities are:
berty mini: a CLI messaging app using the Wesh Protocol.
berty daemon: a full node manageable through the Wesh Protocol API.
Warning: Berty is still under active development and should not yet be used to exchange sensitive data.
- Secure and private :
- Messages are end-to-end encrypted by default
- Metadata is kept to a minimum
- No phone number or email address is required to create an account
- Built to retain its properties even when used on adversarial networks
- Open :
- Free forever and open-source
Berty is designed to be used as an everyday messaging application. Nonetheless, it was built to primarily serve the following use cases:
- When you need to share sensitive information over untrusted networks, for instance while traveling
- If you want to communicate anonymously
- If you want full control over your data and thus don't want to rely on third-party servers
- In countries that actively monitor and temper with their network, restricting its use and censoring some of its contents
- In areas with weak or no connection at all
Berty is currently developed by Berty Technologies, a French nonprofit organization.
Note: this project is led by a small team made of humans, who make mistakes. Please do not hesitate to point out bugs or missing features. See the contribute section below.
We cannot promise we will offer you the best application, but we dedicate ourselves to doing our best to create a great one.
The philosophy behind Berty
We want to contribute to a world where free and secure communications are common and fear of censorship or surveillance are not.
We believe that open-source is more secure, as anyone can examine the code and improve it: this is why we rely on and build open and free software.
As the founding team, our ultimate goal is to progressively relinquish control over Berty and to make it become a truly global community project.
More info on berty/community.
The current Berty implementation is using the Wesh Protocol, which means the encryption technique is safe, and it works as a peer-to-peer app!
Alas, Berty has not yet been hardened, so please avoid using it on devices with weak sandboxes, such as unpatchable devices that use old Android versions.
The current Wesh Protocol is partially implemented.
The API will continue to evolve in the near future. As such, we cannot yet guarantee none-breaking changes, or any kind of API stability. Be prepared for a rough ride if you start rolling the Wesh Protocol in your application.
We will have an open beta for the different packages and applications soon, so anyone will be able to give it a try. Subscribe to our newsletter if you wish to be notified.
Note: The repositories are being opened progressively, and there will be additional modifications and updates soon.
Under the hood
The Wesh Protocol comes with a generic, but full-featured SDK allowing developers to write peer-to-peer applications. You can just focus on high-level features for your app, we will take care of the rest (encryption, identities, network routing, group management, account management, device management, application lifecycle).
The main concept of the Wesh Protocol is called the "group", a virtual place where multiple devices can share messages and metadata using OrbitDB, which itself relies on the InterPlanetary File System (IPFS)
git clone https://github.com/berty/berty
The Berty Messenger
Main items in the repo
- ./go: Where all the Golang code lies.
- ./go/framework/bertybridge: The gomobile entrypoint.
- ./go/cmd/berty: The main Berty CLI:
berty daemon: Runs the whole Wesh Protocol instance.
berty mini: Simple CLI messenger application using Wesh Protocol.
- ./go/cmd/rdvp: A Rendez-Vous Point server.
- ./go/cmd/welcomebot: An onboarding bot used during the early phase.
- ./go/cmd/testbot: A bot used by integration tests and developers.
- The Berty Messenger application, written in React Native.
- ./docs: Mostly auto-generated documentation.
We welcome contributions! Your input is deeply appreciated and extremely valuable to us. We thank you in advance for it.
There is no small feat: everyone is encouraged to do what they can to help, based on their ability and interest.
There are plenty of ways to get involved and to help our community, which can roughly be divided in two distinct parts: everything that is related to the code and everything that is not.
To put it simply:
- Code-related = GitHub
- Not code-related = Open a task
Everything about contribution is summed up here: CONTRIBUTING.MD
Stargazers over time
- Official website: https://berty.tech
- Assets: https://assets.berty.tech/
- Application assets & mockups: https://assets.berty.tech/categories/app__v2.4/
© 2018-2023 Berty Technologies
Berty is the main CLI entrypoint to manage the Berty ecosystem (client, server, relay, dev).
|Berty is the main CLI entrypoint to manage the Berty ecosystem (client, server, relay, dev).|
Package mini contains main helpers to start a term-based Berty mini client.
|Package mini contains main helpers to start a term-based Berty mini client.|
rdvp is a service to hold Berty's rendezvous point for faster peer discovery.
|rdvp is a service to hold Berty's rendezvous point for faster peer discovery.|
Package bertybridge is the main gomobile entrypoint, used to generate iOS and Android frameworks.
|Package bertybridge is the main gomobile entrypoint, used to generate iOS and Android frameworks.|
discordlog is an unsafe package used during development to log info directly on the Berty's Discord server.
|discordlog is an unsafe package used during development to log info directly on the Berty's Discord server.|
nolint // file imported from go-gorm sqlite driver
|nolint // file imported from go-gorm sqlite driver|
Package grpcutil contains gRPC lazy codecs, messages and a buf-based listener.
|Package grpcutil contains gRPC lazy codecs, messages and a buf-based listener.|
Package testutil contains testing helpers (logging, slow skipping).
|Package testutil contains testing helpers (logging, slow skipping).|
Package tools ensures that `go mod` detect some required dependencies.
|Package tools ensures that `go mod` detect some required dependencies.|
Package accounttypes is a reverse proxy.
|Package accounttypes is a reverse proxy.|
Package banner generates ASCII picture of the Berty logo with a message.
|Package banner generates ASCII picture of the Berty logo with a message.|
Package bertybridge is a reverse proxy.
|Package bertybridge is a reverse proxy.|
Package bertymessenger contains the top-level API that uses the Berty Protocol to implement the Berty Messenger specific logic.
|Package bertymessenger contains the top-level API that uses the Berty Protocol to implement the Berty Messenger specific logic.|
Package directorytypes is a reverse proxy.
|Package directorytypes is a reverse proxy.|
Package errcode contains the list of Berty error codes.
|Package errcode contains the list of Berty error codes.|
Package messengertypes is a reverse proxy.
|Package messengertypes is a reverse proxy.|