Eridius Group is a for-profit organization with a key goal of raising public awareness for the greater internet's privacy and security. All too frequently, big tech companies use your private data—even in Incognito mode—to target you with advertisements, including harmful ones.
We believe this inherent violation of user privacy is immensely unethical, and we believe the public deserves to know how to protect themselves from this abuse of power from big tech.
We fix these privacy violations via two methods. Firstly, we raise awareness. If the public is fully aware of the implications caused by privacy violations, we believe big tech companies will be more hesitant to further their unethical practices. Secondly, we aim to provide alternatives to closed-source, privacy-compromised software, utilizing the strategy of staying ahead of the industry standard.
The software we deliver to consumers is frequently used internally and battle-tested prior to release. By using our own software, we can ensure bugs and security vulnerabilities are patched quickly, and you can be sure our software doesn't do unnecessary tracking or sketchy practices.
The best thing you can do is share the news! Share our posts on social media, send our website to your friends, retweet, repost—anything and everything helps! If you still want to do more, you can buy us a coffee!
We release our source code under a Source Available license. You can see and audit exactly how everything works; however, you cannot modify the code for your own purposes. If you want to use a self-hosted copy of our software, you are free to do so—so long as it isn't for commercial purposes. If you want to use some of our code in an open source and non-commercial project, please contact us first.
There are more details in our Eridius Public License page.
Our company is run by software engineers and privacy advocates. If you have any questions or concerns about our technology stack, feel free to contact our primary team lead at eridian@eridi.us
We use Rust for our backends, using Ntex as a server system and Diesel for database interactions.
We use PostgreSQL for our database, with Redis making a special appearance for caching.
Instead of using session cookies, we often use LocalStorage to store the authentication information.
The data on the server is usually encrypted end-to-end, using a private key that is stored in our Erix One solution. That private key is encrypted with your account password, our server private key, and an additional, cryptographically secure key that is associated with your device.
To add additional devices, you have to pass 2-factor authentication via TOTP, and you have to manually enter a device key or scan a QR code that contains the device key. We also use WebAuthn as a “third factor” for logging in.
To deploy, the Rust code is automatically compiled on GitHub, and a release binary is generated. These release binaries are used for testing, where we run a development build to ensure there are no bugs. If the development build is functional, we tag the release. The tag triggers another build that is specific to the production server, and that build is used at midnight to deploy.