> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/project/about.md).

# 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 — discovery, ownership, planning, documentation, and sharing in one place instead of five.

## 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, and sharing without rebuilding the same context from scratch every time. For the shipping surface behind that intent, see [Press / media boilerplate](/project/press-release.md) and [Development status](/project/development-status.md).

## 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.

The public policy for AI crawlers and downstream tooling lives on [AI and open data](/project/ai-and-open-data.md).

## How it is built

Patcher is an open-source web app built on Angular and TypeScript, with a Supabase backend and served through Vercel.

## 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)
* [Development status](/project/development-status.md)