One engine.
Any plugin.
Design an audio plugin in your browser. Run it in Logic. No code.
RoleFounder, designer, engineer
ScopeProduct, UX, UI, code
PlatformWeb + macOS
StatusWorking beta
Plugin Forge · From signal chain to finished instrument
The problem
Making a plugin takes a team and a year.
Every plugin company builds and ships a separate program for each product. That's slow and expensive, and only engineers can do it.
The idea
Ship one engine. Make each plugin a file.
The engine reads a design file and becomes that plugin. A new plugin is a new file, not a new program.
The architecture · One engine, any plugin
How it works
Three steps.
1. Build the soundSnap together parts like tubes, EQs, compressors and reverb, then tune by ear.
2. Design the faceLay out knobs and meters on a faceplate. What you see is exactly what ships.
3. Run it in your DAWInstall with one click. It opens in Logic like any other plugin.
01 / Build the sound
02 / Design the face
The products
Real plugins, built on it.
Mixing tools and guitar amps, all running on the same engine.
Drum Crusher · Parallel dynamics
Molten · Valve amplifier
Session Scope · Performance monitor
Beyond the plugin
The whole business, end to end.
Plugin ManagerA desktop app to sign in, install and update plugins.
LicensingActivation, trials and seats, with demo mode instead of lockouts.
Describe itType what you want in plain English and get a starting design.
StudioA browser DAW to try plugins in a full mix.
Plugin Manager · Your studio, in one place
By the numbers
0
lines of code to make a new one
What I did
All of it.
Concept, product strategy, UX, interface design, the audio engine, the design tool, licensing and the desktop app.
- Product strategy
- UX & flows
- UI design
- Design system
- Audio DSP
- Front-end
- Native macOS
- Backend