Plan without losing the thread
A hardware decision often crosses several calculators. A gaming build may start in the PC Builder, move through GPU comparison and PSU sizing, then return days later. A NAS plan may pair capacity with power cost. Hardware Projects keeps the goal, constraints, supported tool inputs, and dated references under one local project ID.
The workspace does not merge those tools into a new compatibility engine. Each connected tool keeps its own evidence boundary and result language. A product appearing in the project means it was referenced by a tool or template; it does not mean every other saved part works with it.
That boundary matters. I do not treat a saved product list as a compatibility verdict. Suppose an upgrade starts with a graphics-card shortlist, reaches a power estimate, and later needs a motherboard lane check after another drive enters the plan. The project keeps those supported inputs under one title, while each tool still explains what its result establishes, which source or assumption it used, and what the exact manuals and physical inspection must answer before buying or installing a part.
Choose the right way to move a project
Use a limited snapshot link when another person needs the calculator state and product references. The link excludes the use case, private constraints, diagnostic text, and evidence. Opening it creates an unsaved preview with a new ID, so it cannot silently replace a project already stored on that device.
Use the full JSON download for backup or transfer between your own devices. That file includes the private fields omitted from a snapshot. Import also opens a preview and requires an explicit save.
Keep that file private, especially when the constraints or diagnostic notes identify your equipment. Treat it as personal.
Projects are stored in this browser. Clearing browser storage can remove them, and another browser or device cannot see them without a JSON transfer. If browser storage is unavailable, full, or corrupt, the workspace reports the failure instead of replacing the stored record.
Back it up.
Start with a focused route
Start with one decision.
- For a new gaming PC or upgrade, start with PC Builder, compare the exact GPUs you are considering, then run the saved load through the PSU calculator.
- For a storage server, start with the usable-capacity and fault-tolerance tradeoff in the NAS calculator, then carry its state into the power-cost calculator.
- For intermittent faults, open the Diagnostic Workbench from a diagnostic project. Record the symptom, display or hardware path, recent change, tests, and outcome without placing those notes in a shared snapshot.
- For ECC or expansion decisions, attach the dated result from the AM5 ECC checker or NVMe expansion checker. Keep the manufacturer evidence and its stated scope beside the project.