Aster-Privacy/Aster-Mail
Aster-Privacy/Aster-Mail has 117 GitHub stars and 9 forks. GitHot measured 0 stars in 24 hours. Last checked 2026-11-15 15:51 UTC. Last push 2026-11-15.
Measured star growth
- in 24h
- 0
- in 7 days
- Update delayed
- in 15 days
- Update delayed
- in 1 month
- Update delayed
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Cross-platform encrypted email client for Aster
SecurityREADME.md
Original
Aster Mail is a free, open-source, end-to-end encrypted mail service. Every message, subject line, and attachment between Aster users is encrypted locally on your device, and mail to an outside address is encrypted on your device whenever the recipient publishes an OpenPGP key. This means we have no way to read that email and we never will.
You can sign up at astermail.org. A phone number and recovery email are not required.
How it works
All Aster-to-Aster messages are end-to-end encrypted with post-quantum encryption (ML-KEM-768 and P-256 ECDH) inside an X3DH and Double Ratchet protocol, which protects against store-now-decrypt-later attacks. Subject lines are also encrypted. This means that we cannot read your subject lines, unlike other providers. Mail you send outside Aster uses standard OpenPGP (Ed25519 and Curve25519).
Your keys are yours, and they are fully portable. You can export them and use them with GPG or any OpenPGP client. Encryption between Aster users needs no setup. To let people outside Aster find your public key, turn on WKD or keyserver publishing in Settings > Encryption. Both are off by default.
Aster runs on a zero-access architecture located in Germany. Mail that arrives from outside Aster without OpenPGP encryption reaches our servers readable, and we encrypt it with your public key as soon as it arrives. Routing data such as sender and recipient addresses and timestamps stays visible to our servers, because mail can't be delivered without it.
Getting started
Go to astermail.org to create a free account. If you would like to contribute code to Aster, see CONTRIBUTING.md for instructions.
Building from source
You can build Aster Mail yourself from this repository. It builds into a web bundle and a desktop app for Windows, macOS, and Linux. There is no account or API key involved, and you do not need to write a .env file. These are the same steps our release workflow runs.
You will need Node.js 20 or later and a stable Rust toolchain. On Debian or Ubuntu, the desktop build also needs a few system libraries:
sudo apt-get install libwebkit2gtk-4.1-dev libayatana-appindicator3-dev librsvg2-dev libxdo-dev libssl-dev build-essential file
Aster Mail shares its interface components with our other apps through aster-ui, so you will need to clone it next to Aster Mail and build it first. Installing will fail if it is not there:
git clone https://github.com/Aster-Privacy/aster-ui.git
git clone https://github.com/Aster-Privacy/Aster-Mail.git
cd aster-ui && npm install && npm run build
cd ../Aster-Mail && npm install --force
To build the web app:
npm run build
The build is written to dist/. You can serve it with any static web server.
The desktop app updates itself through GitHub Releases, so Tauri asks for a signing key even on a local build. Generate one once. It will only ever sign your own builds, and you can leave the password empty:
npm run tauri signer generate -- -w ~/.aster_updater.key
export TAURI_SIGNING_PRIVATE_KEY=$(cat ~/.aster_updater.key)
export TAURI_SIGNING_PRIVATE_KEY_PASSWORD=""
npm run tauri:build
Installers and binaries are written to src-tauri/target/release/bundle/.
The Android project in this repository is a development wrapper. The app we publish to Google Play is built from Aster-Android.
Code signing policy
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
The Windows app and installers on the Releases page are built by GitHub Actions from the source code in this repository and signed as part of that build. Files built anywhere else are never signed.
- Committers and reviewers: members of the Aster Privacy mail team. Every pull request from someone outside the team is reviewed by a team member before it merges.
- Approvers: the owners of the Aster Privacy organization. An approver reviews and approves each signing request.
Aster Mail connects to Aster servers to send and receive your mail. To learn what data Aster processes and how it is protected, read the Aster privacy policy.
Community
Join our Discord to share feedback, ask questions, and contribute to the privacy community. You can also find us on X and Reddit.
If you have any questions or security disclosures, email us at [email protected] or [email protected]. Do not open a public issue for security vulnerabilities. Read SECURITY.md for the full security vulnerability disclosure process.
Contributing
We welcome contributions of all kinds. Read CONTRIBUTING.md before opening a pull request.
By contributing to any Aster repository, you agree that your contributions will be licensed under AGPL v3.