Divest OS
Privacy-focused Android ROM with hardening.
Open the official app on divestos.org
This tool is hosted by its maintainers. Click below to open divestos.org in a new tab — it's their official demo.
Browse developer tools →What's next with Divest OS?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Divest OS?
DivestOS is an open-source mobile operating system designed to provide enhanced privacy and security for users seeking alternatives to mainstream mobile platforms. Built on a modified Android framework, it targets users concerned about data collection, surveillance, and lack of control over their device ecosystems. The project emphasizes customizability and transparency, allowing developers to tailor the OS to specific privacy needs. By archiving its build repository in 2024, the project shifts focus to long-term archival rather than active development, leaving its operational viability uncertain. It addresses the problem of proprietary mobile OSes prioritizing corporate interests over user autonomy, offering a framework for building secure, privacy-first mobile environments.
How it works
DivestOS is a mobile OS built on a forked Android framework, aimed at users prioritizing privacy and security over proprietary control. Its primary purpose is to provide a customizable, open-source alternative to mainstream mobile operating systems. The project's focus on privacy includes features like data minimization, encrypted storage, and reduced tracking capabilities. It caters to developers and advanced users seeking to replace commercial OSes with a system that prioritizes transparency and user control. DivestOS enables customizability through modular components, allowing developers to replace proprietary services with open-source alternatives. It includes tools for managing app permissions, encrypting communications, and limiting metadata exposure. The project also provides prebuilt applications and configuration templates for streamlined deployment.
How to use it
- 1Clone the archived DivestOS-Build repository from GitHub. 2. Install required build tools and dependencies for Android-based OS development. 3. Modify configuration files to customize privacy settings or add third-party apps. 4. Compile the OS image using the provided build scripts. Practical tips include verifying hardware compatibility and ensuring all dependencies are up-to-date before attempting a build.
What it can do
- privacy android rom
Use cases
Assumptions and limitations
Assumptions
- source: https://github.com/Divested-Mobile/DivestOS-Build
- license: Apache-2.0 — free to use
- privacy: Self-hosted — you control your data
Limitations
- The project is no longer actively maintained due to the archived repository
- Lack of recent updates may render it incompatible with modern hardware or software standards
- Limited community support and documentation compared to mainstream OS projects
- Potential security risks from unpatched legacy code in archived versions
- Requires advanced technical knowledge for customization and deployment
Understanding the result
Privacy-focused Android ROM with hardening.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (Apache-2.0).
- Built with
- (Divested-Mobile/DivestOS-Build)
- License
- Apache-2.0
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with Divested-Mobile/DivestOS-Build. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- Apache-2.0
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- Apache-2.0 License
Upstream project
Frequently asked
What is DivestOS and how does it differ from mainstream mobile OSes?
DivestOS is an open-source mobile OS designed with privacy and security as core priorities. Unlike mainstream OSes that prioritize ecosystem integration and monetization, DivestOS focuses on minimizing data collection, offering customizable privacy controls, and providing transparency in its codebase. It targets users who want to avoid proprietary tracking mechanisms and maintain full control over their device environments.
How does DivestOS achieve enhanced security compared to Android?
DivestOS enhances security through modified Android frameworks that reduce reliance on proprietary services. It incorporates features like default encryption, restricted app permissions, and optional removal of telemetry systems. The project also allows developers to replace core components with open-source alternatives, creating a more auditable and customizable security foundation compared to stock Android implementations.
How can I build DivestOS on my own hardware?
To build DivestOS, first clone the archived DivestOS-Build repository from GitHub. Install Android build tools and dependencies, then modify configuration files to suit your hardware and privacy requirements. Use the provided build scripts to compile the OS image, ensuring all dependencies are up-to-date. Note that this process requires advanced technical knowledge and may not support modern hardware due to the project's archived status.
How does DivestOS compare to alternatives like LineageOS or GrapheneOS?
Unlike LineageOS, which is a standard Android-based ROM, DivestOS focuses explicitly on privacy features like data minimization and telemetry reduction. Compared to GrapheneOS, which emphasizes security through hardware-based protections, DivestOS prioritizes software-level customization. All three projects are open-source, but DivestOS's archived status and limited active development set it apart from more actively maintained alternatives.
What should I do if I encounter build errors with DivestOS?
Build errors with DivestOS may stem from outdated dependencies or hardware incompatibility. Verify that all build tools are correctly installed and updated. Check the repository's archived issue tracker for known problems. If hardware compatibility is suspected, consult the project's documentation for supported devices. Since the project is no longer maintained, some errors may require manual code adjustments or alternative solutions.