se7en beatlab · local plugin infrastructure
One local engine behind the plugin line.
se7en Engine coordinates compatible plugins, carries internal sidechain groups and lets supported processing run in a separate high-priority process. The local path remains available as fallback.
Local coordination first. Separate processing where it is supported.
Compatible plugins can exchange control signals through se7en Engine and supported processing can move to its separate process. If the engine is unavailable, the local processing path remains available.
The engine is infrastructure, not the product: each plugin still has its own job, interface and local processing path.
The line
Four modules. Four personalities.
Your level, locked. Hands off the fader.
Sailor LUFS
In the lab
Private beta · Launch price USD 49 · VST3 · Windows x64
The Eye watches your stereo field.
Chorus Horus
In the lab
Private beta · Launch price USD 49 · VST3 · Windows x64
The vocal gets space. The beat keeps its punch.
Make Way
In the lab
In development · Launch price USD 49 · VST3 · Windows x64
There is no step four.
-
01
Load the plugin on a track.
The compatible distribution is designed to install the engine alongside the plugin. -
02
The engine shows up on its own.
The plugin authenticates against the server with a cryptographic handshake — an authenticity gate, not a padlock. -
03
A golden S7 sits next to your clock.
That's the whole presence: a tray icon, and a status window if you want to look inside.
Sidechain without cables.
Compatible plugins can exchange sidechain signals through four internal groups (A–D). A vocal can send to group A and Make Way on the beat can listen to A without creating an extra DAW bus. That internal path adds one block of latency; the DAW sidechain takes priority when you use it.
VOZ → GRUPO A
MAKE WAY ← A
INTERNAL SIDECHAIN
What's inside. No smoke.
| Format | VST3 · Windows x64 (the only publicly validated platform) |
|---|---|
| Process | Supported processing can run in a separate high-priority process, outside the DAW audio thread |
| Local fallback | Compatible plugins keep a local processing path available |
| Audio privacy | Audio processing stays on your machine. Telemetry is off by default and never sends audio. |
| Sidechain | 4 internal groups (A–D), +1 block latency on that path; DAW sidechain takes priority |
| Authenticity | Cryptographic challenge-response between plugin and engine — a gate, not DRM theater |
| Interfaces | Each plugin keeps its original frontend — characters, not a generic re-skin |
Built from studio needs
Infrastructure for a plugin line with specific jobs.
The engine grew around coordination and routing needs that appeared in studio sessions. The plugin pages explain each current use, validation and limit.