Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Kushview?
Kushview is an audio software company that builds plugins and Element, an open-source modular host for running them. Its catalog spans small, focused tools — PulseDial DTMF Synthesizer, Witch’s Brew Bitcrusher, Tone Generator and Smoothie — alongside Element, which lets you build custom effect chains and instrument racks with no fixed signal path: you patch the routing yourself. The plugins are offered as VST3, AU, CLAP, LV2 and standalone builds on Mac, Windows and Linux, and Element is free and open-source on GitHub, with paid builds funding continued development. Kushview also works as a JUCE/C++ audio development shop, citing 15+ years of experience and services such as plugin development, CLAP migration, legacy plugin rescue and white-label plugin hosting.
Who it is for
- Producers and sound designers who want modular routing rather than a fixed chain, and small utility plugins for specific jobs.
- Plugin developers and studios needing contract work, format migrations or hosting for existing products.
- Open-source users who prefer to build and run Element from source, or buy a build to support it.
How to choose between the two sides of the site
| If you want… | Start with… |
|---|---|
| A modular host for effects and instruments | Element |
| Individual tools (synth, bitcrusher, tone generator, smoothing) | The plugin catalog |
| Custom development or format migration | The development services page |
A practical next step: if you already use a DAW but find its routing rigid, try Element as a standalone host or plugin inside your DAW, then add one Kushview plugin to test how the patching workflow suits you. If you are evaluating development help instead, note which format you need (VST3, AU, CLAP or LV2) and whether your project is a new build or a rescue of legacy code — those two cases map to different services listed on the site. Related communities and references include GitHub for Element's source and issues, and KXStudio for Linux audio plugin hosting context.
What is Element used for?
Element is a modular host for audio plugins: you load instruments and effects, then patch the routing yourself rather than following a fixed mixer-style signal path. It runs VST3, AU, CLAP, and LV2 plugins, and it is available as a standalone application on Mac, Windows, and Linux. Kushview also describes it as open source, with paid builds funding continued development.
What that means in practice
- Custom effect chains. Instead of accepting a serial insert order, you decide what feeds what. A common use is splitting a source into parallel paths, processing each differently, and summing them.
- Instrument racks. Multiple synths or samplers can be combined into one playable setup, with each layer routed to its own processing before reaching the output.
- Modular routing. Feedback loops, sidechains, and multi-bus layouts become possible because nothing is hardwired.
- Structured plugin hosting. If you already own plugins in several formats, Element gives you one place to host them rather than depending on a single DAW's built-in support.
Who it suits
| User | Why Element fits |
|---|---|
| Sound designers | Parallel and feedback routing for layered textures |
| Live performers | Standalone operation without opening a full DAW |
| Plugin collectors | Hosting VST3, AU, CLAP, and LV2 in one environment |
| Tinkerers | Open-source code and a patchable graph to experiment with |
The trade-off is that a blank modular graph asks more of you than a DAW's default channel strip. If your goal is simply to record a track with a few inserts, your DAW's mixer is faster. If your goal is a routing scheme your DAW cannot express, Element is the point.
A practical first step: install it, load two copies of the same reverb, route a dry source into both with different settings, and blend the outputs. That single exercise shows whether patching your own graph is a workflow you want, or just a feature you like the idea of.
How do I build a custom effect chain or instrument rack in Element?
Element is built around a patchable graph rather than a fixed insert chain, so you build a custom effect chain or instrument rack by adding nodes and then connecting their inputs and outputs yourself. There is no mandatory serial order: the routing is yours to define, which is what makes both a simple guitar-style chain and a parallel or multi-instrument rack possible in the same project.
A practical way to start
- Add your source first. For an instrument rack, that is a virtual instrument or a MIDI input node; for an effect chain, it is an audio input or a track/player node.
- Add each effect or instrument as its own node, one per plugin, rather than stacking several inside one slot.
- Connect source to first node, then node to node, until the signal reaches an output node.
- For an instrument rack, insert a MIDI input or keyboard node ahead of each instrument and route its audio onward to a mixer or output.
- Save the graph once it works, so the same layout can be reloaded for later sessions.
Choosing between a chain and a rack
| Goal | Graph shape | Trade-off |
|---|---|---|
| Classic pedalboard-style effects | One linear path from input to output | Easiest to reason about, but no parallel blending |
| Layered instruments | Several instrument nodes fed by one MIDI source, summed at the output | Rich stacked sounds; needs gain staging so layers do not clip |
| Parallel processing | One source split to two or more branches, recombined later | Flexible blend control; more nodes to manage and more places for a routing mistake |
| Live or modular experimentation | Free patching with feedback-style or reordering changes | Maximum freedom, but harder to reproduce without saving presets |
Decision criteria
If you mainly want to hear one effect after another, keep it linear and resist adding branches. If you want to blend a dry signal with a heavily processed one, split the path and rejoin it at a mixer node. If you are building a playable rack, decide early whether each instrument gets its own MIDI channel or whether they all respond to the same notes, because that choice shapes the whole graph.
Because Element supports VST3, AU, CLAP, LV2 and standalone use across Mac, Windows and Linux, the same graph concept applies whichever plugin formats you happen to own. Kushview also lists audio development services, including CLAP migration and plugin hosting work, which is relevant if your goal is a tailored host rather than a personal setup.
For the exact node types, connection behaviour and download options, work from the official pages: Kushview and the Element project on GitHub.
Which plugin formats and operating systems do Kushview plugins support?
Kushview's plugins and Element host support VST3, AU, CLAP, LV2, and standalone formats, running on Mac, Windows, and Linux.
What that means in practice
That format list covers the main ecosystems you're likely to encounter:
- VST3 and AU — the standard choices for most DAWs on Windows and Mac respectively.
- CLAP — a newer open format, useful if your host supports it and you want modern plugin behavior.
- LV2 — common in Linux audio setups, so it matters if you work in that environment.
- Standalone — lets you run a plugin without a DAW, handy for quick testing or live use.
The three-platform coverage (Mac, Windows, Linux) is broader than many small plugin shops offer, particularly on the Linux side, where LV2 support is a natural fit.
A useful next step
Before buying or downloading, check which format your DAW actually loads. If you're on Reaper, for example, CLAP and VST3 both work; if you're on an older host, VST3 may be your only route. Matching format to host avoids installing something your setup can't open.
For the open-source host itself, see Kushview for details on Element, and GitHub if you want to inspect or build the source directly.
Should I download the free Element build from GitHub or buy the paid build?
The paid build is mainly a way to fund development; functionally, the free Element from GitHub is the same open-source modular host. Choose based on whether you want convenience and to support the project, not on missing features.
What you get either way
Element is a modular plugin host: you patch the routing yourself rather than following a fixed signal path, which suits building custom effect chains and instrument racks. It supports VST3, AU, CLAP, LV2, and standalone operation on Mac, Windows, and Linux. Kushview describes the free version as open-source on GitHub, with paid builds funding continued development, so the core host is available without paying.
How to decide
| Your situation | Better starting point |
|---|---|
| You want to test whether modular routing fits your workflow | Free GitHub build |
| You are comfortable compiling or tracking releases yourself | Free GitHub build |
| You want a ready-to-run build with less setup friction | Paid build |
| You use Element regularly and want it maintained | Paid build |
| You need it for commercial or client work | Paid build, for the support and sustainability |
A practical test
Download the free build first and spend an evening recreating a routing you already do in your DAW, for example splitting a synth into two parallel effect chains and summing them. If the patching model clicks, buy the paid build as a straightforward way to keep it maintained. If you bounce off the interface, you have lost nothing but time.
For other open-source audio tools worth knowing, see Ardour and GitHub.
Can Kushview develop or migrate a custom audio plugin for my product?
Yes. Kushview presents itself as a JUCE/C++ audio development shop with more than 15 years of experience building plugins and audio software, and it lists plugin development (VST3, AU, CLAP, LV2), CLAP migration, legacy plugin rescue, and white-label plugin hosting among its services. So both new plugin development and migration of an existing plugin are in scope for what the site advertises.
What that covers in practice
- New plugins: Building an instrument or effect from scratch in the common formats — VST3, AU, CLAP, LV2 — plus standalone builds, on Mac, Windows, and Linux.
- Format migration: Moving an existing plugin to a newer format such as CLAP, rather than starting over.
- Legacy plugin rescue: Reviving or updating an older codebase that no longer builds, loads, or passes host validation.
- White-label plugin hosting: Shipping a host or hosting layer under your own brand, which is relevant if your product is a container, rack, or plugin-chain tool rather than a single effect.
A realistic scenario
Suppose you have a working VST3 effect but need an AU for Logic users, a CLAP version for Bitwig and Reaper users, and a Linux build that currently fails. That is a migration-and-porting job, not a design job — the useful first step is to inventory what exists: framework (JUCE or otherwise), third-party dependencies and their licenses, copy protection, preset format, and which hosts you must pass. Those details determine whether migration is a rewrite of the wrapper layer or a deeper rebuild.
How to decide
| Your situation | Likely fit |
|---|---|
| New plugin, defined sound and UI | Full development engagement |
| Working plugin, missing formats or platforms | Migration/porting |
| Old project that no longer compiles or validates | Legacy rescue |
| Need a branded host or plugin chain tool | White-label hosting |
Kushview also maintains Element, an open-source modular plugin host for custom effect chains and instrument racks with freely patchable routing. That is a useful reference point: if your product idea resembles a host, rack, or routing tool, reviewing Element's approach tells you how the team thinks about signal flow and format support before you brief them.
To move forward, prepare a one-page spec covering target formats, platforms, host compatibility requirements, existing code and its licenses, and your release timeline, then use the site's "Discuss a Project" contact route. If you are unsure whether you need development or migration, describe the current build's failures to a specific host and version — that detail usually settles the question quickly.
User reviews (0)