# Mapped on your device. Explained for everyone.

Feex maps processes, hardware, services, and apps locally on a Windows PC. This public wiki explains those same kinds of things. Your machine readings stay local.

[Search the wiki](https://feex.it/wiki/)[See what Feex maps](https://feex.it/wiki/about/#mapped)

Feex says

I map processes, hardware, services, and apps locally on your machine. Search this public reference to understand a name I can identify. I do not publish your machine readings here.

**Feex**Mapped on this PC

- [svchost.exe: Windows, Windows Process](https://feex.it/wiki/process/svchost.exe/)
- [Intel Core i7-12700KF: Processors, Desktop CPU](https://feex.it/wiki/hardware/cpu/intel-core-i7-12700kf/)
- [Adobe Photoshop: Creative, Application](https://feex.it/wiki/software/adobe-photoshop/)
- [Windows Update: Update, Windows Service](https://feex.it/wiki/service/windows-update/)

## Built around what Feex can map

Feex maps processes, hardware, services, and software locally on a device. The wiki is a separately published reference for those kinds of names and parts.

The article is about the thing: a process name, a CPU, a service, an app. It is not a labeled copy of your machine. Your machine readings stay local.

## Need to know

- **What is this wiki?**: A public reference for what Feex can identify.

  **Where does its information come from?**: Published research and Feex hardware and process reference data.

  **Does my PC appear here?**: No. Machine-specific readings stay local.

  **What can I look up?**: Hardware, software, processes, and services.

## How Feex and the wiki fit together

1. ### 1 Feex maps it locally

   Feex maps the processes, hardware, services, and apps on a Windows PC. Those machine-specific readings remain on that PC.

2. ### 2 You choose a name to look up

   Search the public wiki for a process name, part number, service, or app that Feex can identify. The search does not upload your local reading.

3. ### 3 The wiki explains it

   Published articles provide fast answers first, then specs, paths, relationships, and sources when you want them.

## Everything Feex maps

Hardware, software, processes, services. Same article shape. Different questions. These are the kinds of things Feex can identify locally.

[**Hardware**What a part is, what it means today, and whether an upgrade is actually the next move.5790 parts](https://feex.it/wiki/hardware/)[**Software**Applications as products: who they are for, what they cost the machine, and which processes they leave behind.400 apps](https://feex.it/wiki/software/)[**Processes**You saw a name running. Here is what it is, whether it belongs to Windows or an application, and what not to do first.207 names](https://feex.it/wiki/process/)[**Windows Services**The friendly name and the system name, plus a clear answer on whether you should disable it.16 services](https://feex.it/wiki/service/)

## What you get on a page

A short verdict in about ten seconds. Then the reference: paths, spec sheets, relationships, and sources.

- A process page tells you if the name belongs to Windows or an app, and what not to do first.
- A hardware page tells you what the part is today, and whether an upgrade is actually the next move.
- A software page ties the product to the processes it leaves behind.
- A service page covers what it does on Windows, and when it first showed up.

## What this is not

- Not a dump of your PC. The wiki is public. Your machine-specific readings stay local.
- Not antivirus. A filename alone is not a malware verdict.
- Not a command to break Windows. We do not tell you to delete System32 files or disable critical services as a first step.
- Not live Task Manager. An On your PC block only appears when real local data exists, and it stays separate from the global article.

## How we write

The author is Feex, not a fake expert byline. One fox speech per article, then the reference. We do not invent Feex sensors, remediations, or benchmark scores. Missing values stay Unknown or Not publicly documented.

- Hardware numbers come from vendor sheets first, then the Feex Hardware Database, with the source shown.
- Process and service safety is contextual.
- Verification status and last verified date sit on every article.

## Related

[Wiki home](https://feex.it/wiki/) · [How we research](https://feex.it/wiki/research/) · [Privacy](https://feex.it/wiki/privacy/) · [Terms](https://feex.it/wiki/terms/) · [feex.it](https://feex.it/)

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/about/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)