patchhaus wiki
patchhaus documentation.
Everything you need to build, design, and ship your own audio plugins — plus a deeper look at how Patchhaus turns your project into sound.
The guide walks you through building and shipping a plugin. Under the hood covers what Patchhaus does with your project — for when you want to go deeper.
Guide
Getting started
Install Patchhaus, sign in, create your first project, and make your first sound.
read page →Building patches
Add blocks, run cables, tweak parameters, play notes, and let the AI assistant do the heavy lifting.
read page →Blocks and modulation
A tour of the built-in block library, plus LFOs, envelopes, and how to make any knob move.
read page →Designing your plugin UI
Lay out knobs, faders, and displays, bind them to your patch, and preview the real plugin interface live.
read page →Exporting plugins
Run the setup check, pick your formats, build the plugin, and load it in your DAW.
read page →Under the hood
How Patchhaus works
The moving pieces behind a Patchhaus session: the desktop app, the live audio engine, your project folder, the AI assistant, and your account on the website.
read page →Your project folder
Every Patchhaus plugin is a folder of plain files — JSON, Svelte, Pole. What each one is, which are safe to edit by hand, and what Patchhaus rewrites for you.
read page →From patch to sound
Every edit to your graph becomes a small DSP program: Patchhaus generates Pole source from your nodes and cables, JIT-compiles it in the background, and hot-swaps the audio without a dropout.
read page →Blocks and custom blocks
A block is a Pole processor plus a JSON manifest. Drop a folder into your project's blocks/ directory and it appears in the palette — knobs, modulation, and live reload included.
read page →Inside your plugin UI
Your plugin interface is a real Svelte app inside your project. The Design Canvas is a visual editor over that source code — and you can edit the same files by hand or let the AI do it.
read page →The patchhaus object
Every method and property on the patchhaus object your plugin UI imports — parameters, live telemetry streams, MIDI output, and the bundled controls built on top of them.
read page →The AI assistant
The assistant doesn't just chat about your plugin — it builds the graph, tunes parameters, writes your UI source, scaffolds DSP blocks, and checks its own work. Here's what it can touch and how to steer it.
read page →What export actually does
Export compiles your plugin for real: what gets snapshotted, why it takes longer than editing, how signing works, and where the finished bundles go.
read page →Troubleshooting
Symptom, cause, fix: no sound, compile errors, dead knobs, frozen modulation, blank previews, failed exports, and plugins that hide from your DAW.
read page →