Configurator · 15 slots

Stack Builder

Pick what you currently run in each slot. The build compares it against the recommended part for your target tier and flags gaps — same idea as a hardware parts list, applied to a security stack.

Target build tier

Desktop platform

Mobile platform

Guessed from your browser — change either if wrong. Affects the two OS Hardening slots below.

Not in this picker: social engineering discipline, physical security habits, and legal/documentation steps aren't product slots — they're behavior, not purchases. The companion OPSEC Field Manual covers exactly that discipline layer as a checklist; see personal-security-playbook.md for the full write-ups on those domains and the incident-response runbooks. Costs shown are rough annual estimates for the paid tier of each option and may not reflect current pricing — verify at checkout.

On the Linux/GrapheneOS recommendations: Privacy Guides and Techlore rate Linux (desktop) and GrapheneOS (Android) as the stronger privacy default because mainstream proprietary OSes ship with telemetry that's genuinely hard to fully remove — see Privacy Guides' Linux Overview and Windows Overview. Neither source treats staying on Windows, macOS, or iOS as a mistake — see Techlore's "The Real Privacy Enemy is Ourselves" on shaming beginners and people who make informed, practical platform choices. Every platform above gets a real hardening ceiling either way.

On the ✓ verified / Legacy tags: this isn't a static list — slots get re-checked against current vendor pricing and source guidance on the project's quarterly cycle (see SOURCES in a generated report). A ✓ verified tag shows the date a slot's figures were last confirmed current; a slot with no tag hasn't been re-checked recently. When a figure changes, the old value isn't silently deleted — it's kept as a Legacy note directly under the current recommendation, so you can see what changed and when.

Your build stays in this browser only, in localStorage — nothing is sent anywhere, so it's still here next time you come back for the quarterly re-audit the Playbook recommends. Reset build clears it.