For audio software companies

Your plugin UI,
in web tech

JUCE 8 lets a plugin host its interface as a web app. We build that interface in React, ship it inside your AU and VST3, and then run the same code as a signed desktop app, an iOS app, and an Android app. Your DSP stays in C++. From $8,500 in 3 to 5 weeks, fixed scope. You own the code.

001 / The problem

Plugin interfaces are stuck in 2009

Not because your team is slow. Because the tooling was

Most plugin UIs are still hand-positioned C++ components. Every layout change is a recompile. Every resolution and window size is a separate fight. Nobody outside the audio team can touch the front end, so the interface queues behind the DSP work forever and ships looking a decade behind the product.

JUCE 8 changed the constraint. A plugin can now host a real web view and talk to it over a typed bridge, which means the interface can be built by anyone who knows the web, tested in a browser in seconds, and reused everywhere else you ship. The catch is that almost nobody has actually taken that path all the way through signing, notarization, licensing, and a real DAW. We have.

What usually goes wrong
002 / One codebase

Six places the same interface runs

Written once, shipped everywhere your users are
01

The browser

Trials, demos, and a web app your marketing site can link straight into. No install between someone reading about your product and using it.

02

AU + VST3

A JUCE 8 plugin hosting the same interface in a WebView, signed and notarized, loading in Logic, Ableton, Reaper, and Pro Tools.

03

macOS

A native desktop app with Developer ID signing, Apple notarization, a .dmg installer, and an auto-updater feed.

04

Windows

The same desktop app with an Azure Trusted Signing certificate and an installer that gets through SmartScreen.

05

iOS

A real App Store build with native sign-in, in-app review, and the platform behaviours Apple review actually checks for.

06

Android

A signed Play Store bundle from the same source, including the WebView quirks that break most ports.

003 / How it works

Estimate · Fixed scope · Weekly review · Handoff

One bill, then it's yours
01

Free written estimate

Send the repo, a build, or a screenshot of the UI you want replaced. Within 48 hours you get a written read on what it takes, which runtimes are worth doing, and which are not. No call required, no cost.

02

Fixed scope and price

One number and one scope before any work begins. From $8,500. No hourly billing, no retainer, no surprise invoice when the signing turns out to be harder than anyone budgeted for.

03

Weekly review, in a DAW

You get a loadable build every week, not a screenshot. Progress is judged in the host your customers actually use, which is the only place plugin work is ever really done.

04

Handoff, you own it

Full source, the CMake and build configuration, the signing and release pipeline, and a plain-English walkthrough. Your team keeps shipping without us.

004 / Proof

Song Cage · Web, mobile, desktop, and a DAW plugin

Our own product, built exactly the way we'd build yours
Case study · Music software

One React codebase running in six runtimes, including an AU/VST3 plugin with a neural model inside it.

Song Cage is our own songwriting product. The same 166,563 lines of TypeScript run in a browser, in an iOS app, in an Android app, in a Tauri desktop app on macOS and Windows, and inside a JUCE 8 AU/VST3 plugin's web view. The macOS package is Developer ID signed and Apple notarized; the Windows installer is signed through Azure Trusted Signing; both ship behind an auto-updater and an offline licence check that survives with no network.

Inside the plugin it runs a note-level singing transcription model entirely on the user's machine, scoring 76.6% on the standard benchmark against the 73.3% that two human annotators reach agreeing with each other. No audio leaves the computer and there is no inference bill, because there is no server. The word tools work the same way: a full pronouncing dictionary and word database shipped as local data, so they answer instantly in a studio with no internet.

Read the Song Cage case study →
6
Runtimes from one codebase
166k
Lines of shared TypeScript
76.6%
Transcription accuracy, running client-side
005 / Scope

What we take on, and what we don't

Being clear about this saves everyone a call
We build
We don't
006 / Questions

Audio plugin development FAQ

Performance, price, ownership, signing

Can you build a plugin UI in React instead of C++?

Yes, and that is the core of this service. JUCE 8 added a WebBrowserComponent-based UI path so a plugin can host a web front end and talk to the C++ audio thread over a typed bridge. Your DSP stays in C++ where it belongs. The interface becomes a normal web app that any front-end developer on your team can read, change, and test in a browser without opening a DAW. We have shipped this in production, signed and notarized, as both AU and VST3.

What does audio plugin development cost?

Engagements start at $8,500 for a fixed scope, usually delivered in 3 to 5 weeks. One bill, no hourly billing and no retainer. After a free written estimate you get a fixed scope and a fixed price before any work starts, so there is no scope-creep invoice at the end. You own all the code.

Will a WebView UI hurt audio performance?

No, because the audio never goes through it. The web layer draws the interface and sends parameter changes across a bridge; the real-time thread stays in C++ and never waits on the browser. What you gain is hardware-accelerated graphics through the GPU, layouts that reflow properly at any window size, and an interface you can iterate on in seconds rather than on a recompile.

Can the same interface run outside the plugin?

That is usually the point of doing it this way. Once the UI is a web app it also runs as a desktop application on macOS and Windows, as iOS and Android apps, and in a browser for demos and trials. We have one React codebase running in all six of those places at once. You stop maintaining separate front ends for your plugin, your standalone, and your mobile companion.

Do you handle signing, notarization, and installers?

Yes, and it is usually the part that eats a team's week. We handle Developer ID signing and Apple notarization for the macOS .pkg and .dmg, Azure Trusted Signing for the Windows installer, the auto-updater feed, and the offline licence check that has to keep working when the user is on a plane. We have all of it running in production today.

Can you run a machine-learning model inside the plugin?

Yes, on the user's machine with no server. We ship a note-level singing transcription model that runs client-side inside the plugin's WebView and scores 76.6% on the standard benchmark, above the 73.3% that two human annotators manage against each other. No audio leaves the machine, there is no per-conversion inference cost, and it works offline. If you have a model you want in a plugin instead of behind an API, this is the same work.

What do I own at the end?

Everything. The full source, the build configuration, the signing and release pipeline, and a plain-English walkthrough so your team can keep shipping without us. No platform lock-in and no subscription to The Notus.

007 / Also from The Notus

When you need the other side

Same shop, different problem
Pillar one · From $7,500

Apps to production →

A stuck AI-built prototype finished properly and shipped to real users. Auth, payments, database design, and the security pass no AI tool runs for you.

Done for you

Content engine →

Your live product turned into video, social, and blog content on a schedule, with your approval before anything goes out. Built for companies with a real product and no marketing headcount.

Send us your plugin

We'll tell you what a web-tech UI would take.

Free written estimate in 48 hours. No call required.

Get a free estimate →