Coming soon·Launching soon. The tools are in final testing.

Coming soonVST3AUTray App

Outboard

Outsource DAW plugin processing to external apps on the same machine. Reclaim your CPU.

Price
$14
Lifetime license · Up to 3 Macs · Free updates
In development

This one isn’t released yet.

Outboard · live
−0.0 dBfs
Input
Process
Output

When a mix session has 80 tracks and a dozen heavy plugins, a single DAW process becomes a single point of CPU failure. The fix is obvious: spread the load across more processes.

Outboard is a plugin that, instead of doing the DSP itself, hands the audio off to an independent helper app running outside the DAW. Same machine, same RAM — no network, no cloud, no latency drama.

02 / Signal flow

How it
routes.

Step 01
DAW track
Audio in
Step 02
Outboard plugin
Inserts on track
Step 03
Shared memory bridge
Same-machine, no network
Step 04
Helper app
Hosts VST3/AU
Step 05
Return
Back into DAW
03 / Features

In the
box.

Local-only by design

Audio travels between processes via shared memory on the same machine. No sockets, no LAN, no firewalls to argue with.

CPU isolation

A runaway plugin can't take your DAW down with it. Each helper runs in its own process with its own resource budget.

Drop-in workflow

Insert Outboard on a track, point it at the host app you want to run, and it behaves like any other plugin.

Host your own helpers

The helper app can host any VST3/AU plugin — including the ones that have always crashed your DAW.

Latency-compensated

Reports buffer latency to the DAW so timing stays sample-accurate even with multiple Outboard instances in the chain.

Session snapshot recall

When you open a session, the tray app restores every helper to the exact state it was in when you closed it.

04 / Specifications
Category
BUNDLE
Formats
VST3 · AU · Tray App
Platforms
macOS
License
Lifetime, 3 machines
05 / FAQ

Questions,
briefly.

Is this like AudioGridder?

Same spirit, very different mechanism. AudioGridder uses TCP/IP between machines. Outboard runs purely on one machine and uses shared memory, so there's no networking layer to misbehave.

Does it actually help if I'm on one CPU?

Yes — modern DAWs are bottlenecked by per-process scheduling, not raw CPU. Splitting heavy plugins across processes lets the OS schedule them across more cores.

06 / Keep exploring

Other tools
in the catalog.