# About Patcher exists to make modular gear easier to manage in real life, not just easier to admire online. ## The idea Most modular workflows break apart too quickly. One tool helps you browse modules. Another helps you mock up racks. Patch notes live in photos, notebooks, or scattered documents. Manuals disappear into browser history. The context rarely stays connected. Patcher is built to pull those pieces back together. ## What Patcher is now Patcher is a modern workspace for: * browsing a public Eurorack module database * building a personal module collection * planning and comparing racks * capturing patch routing and notes * keeping manuals closer to the hardware you actually use * sharing selected racks and patches through a public profile ## What makes it different The goal is not just storage. It is recall and continuity. Patcher should help you move between: * discovery * ownership * planning * documentation * sharing without rebuilding the same context from scratch every time. ## Open by default on the public side The public module database is meant to stay accessible. Browsing public information should not require an account, and the project remains open-source. That public surface is a big part of the value: people can research, compare, and learn before they decide to build their own workspace. ## Who it is for Patcher is for modular users who want a cleaner system around their instrument: * people planning a first case * people documenting an established rig * people maintaining several rack variants * people who want more reliable patch recall * people who like sharing selected work without turning everything public ## What Patcher is not trying to be Patcher is not trying to replace the instrument itself, replace manuals, or flatten modular practice into a rigid format. It is meant to reduce friction around the parts that are easiest to lose: hardware context, patch memory, and organization. ## Where to go next * [Quick start](/getting-started/quick-start.md) * [Modules](/core-workflows/modules.md) * [User Area](/core-workflows/user-area.md) * [FAQ](/project/the-project.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.patcher.xyz/project/about.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.