Devices¶
Devices for visibility and control
We build devices for people who want more visibility and control over their technology. This section documents how our hardware works, how to configure it, and how to maintain it, so the community can use, review, and improve it over time.
Why We Build Devices This Way¶
Modern mobile devices collect and process a significant amount of information in the background, often without clear visibility into how or why that data is used. As a community, we wanted hardware that behaves differently - something we can inspect, configure, and trust.
Our approach focuses on reducing unnecessary data collection and giving people practical control over the systems that affect their privacy and security. This documentation explains how our devices are designed, what the limitations are, and how we work together with contributors to keep improving the platform.
What Guides Our Hardware Design¶
π‘οΈ Reduced Data Exposure
We avoid telemetry and tracking wherever possible. This doesnβt guarantee perfect privacy - no system can - but it allows the community to understand how the device behaves and what data stays local.
π Open & Transparent
Whenever possible, our software is open-source and auditable. Some components remain proprietary due to industry constraints (for example, modem firmware), and we document those cases clearly.
β‘ Practical Performance
We aim for a balance between performance, security, and privacy. Some design choices involve trade-offs, and we document these so people can make informed decisions based on their needs.
π§ Repair-Friendly
We support device longevity by providing repair information, replacement parts, and maintenance guidance when available. Keeping hardware functional for longer benefits the entire community.
What This Documentation Covers¶
Setup & Configuration¶
- Initial device setup
- Advanced configuration options
- Operating system installation guides
- Software commonly used by the community
Repair & Maintenance¶
- Repair guides
- Compatible components
- Known hardware issues
- Warranty and support details
Supported Operating Systems¶
We document operating systems that run reliably on our hardware. Community ports and experimental builds are included when available.
Device Lineup Overview¶
We maintain documentation for each device model, including hardware specifications, compatibility notes, supported and experimental operating systems, kernel and driver details, and behavior of hardware switches (if applicable). New device documentation will be added as models are released.
Device clusters¶
Devices are organized into different clusters based on the primary purpose they were designed for.
Privacy cluster¶
Objective: devices that protect users from surveillance and data exploitation.
Home automation cluster¶
Objective: single-purpose devices that integrate seamlessly with Home Assistant and prioritize local control.
Community & Support¶
π¬ Community Forums
A space to exchange ideas, report issues, and share solutions. Many improvements originate from community discussions.
π¨βπ» Technical Support
Support is available for setup, troubleshooting, and repairs. We document as much as possible so common issues can be solved collaboratively.
π Contributing to Documentation
If something is unclear or incomplete, contributions are welcome. Documentation improves when more people participate.
Getting Started¶
If you're new to the ecosystem, a typical workflow is:
- Select a device based on hardware capabilities
- Choose an operating system that fits your needs
- Follow the setup guides to configure it
- Join the community to learn, share, or contribute
Our Approach¶
We treat privacy as something that improves when hardware, software, and community align. Our documentation aims to be straightforward and honest - not to make absolute claims but to explain how the devices work and how we try to improve them.
We appreciate every improvement, report, and contribution. This project grows because of the community supporting it.