01
Sell the instrument
Set a price, publish updates, and grow a catalog over time.
Sell and distribute
Build the instrument. Then choose where to sell or share it.
Offer it as a plugin, publish the code, or adapt the same instrument for hardware.
You probably started with a sound, a missing control, or a utility you were tired of rebuilding. Finishing it for yourself is an achievement. A release lets other people use it.
One instrument
browser → plugin → hardware
After it works, choose how to release it.
A tool that helps you can help others too.
The best small audio tools often begin as personal solutions: a filter that lands where your hands expect, a sequencer that follows the way you think, or an instrument that does one thing beautifully.
Once it works, you have choices. Sell it. Give it away. Publish the source and invite collaborators. Keep the code private and share finished builds.
Choose the path that fits: sell it, give it away, publish the code, or keep the code private and sell ready-to-use versions.
01
Sell it
Charge for the finished instrument, updates, presets, or support.
02
Share it
Give other musicians a tool you already trust.
03
Publish the code
Let people study it, improve it, and contribute.
04
Show it
Use a finished instrument to show what you can make.
Choose what happens after you finish the instrument.
A release can earn money, bring in contributors, grow your audience, or put a useful tool in more hands.
Turn a finished instrument into something people can use on their own.
02
Let people try it
A browser demo lets people hear the instrument before they download it.
03
Invite contributors
Share the code, presets, or a public release with people who want to help.
04
Share a useful tool
If it solved a problem for you, it may solve the same problem for someone else.
Choose where to sell or share your instrument.
Choose a specialist store, your own site, or a public code page. Each release needs files, a demo, images, compatibility details, and a clear way for users to get help.
01
MuseHub
Store and installationApply to sell plugins and audio apps through a music software store. It handles product listings, downloads, updates, and customer support.
Best for
A finished product when you want the store to handle downloads and updates.
How it starts
Partner application and approval
02
Plugin Boutique
Large plugin storeApply to sell your plugin through an established audio software retailer. You will need working files, a product page, screenshots, and support details.
Best for
Finished paid plugins with product and support pages ready.
How it starts
Resale request form and selective review
03
KVR Audio
Marketplace and plugin directoryCreate an account to list your product, share release news, and apply to sell through the KVR Marketplace.
Best for
Public plugins, free or paid.
How it starts
Developer account and editorial submission
04
Gumroad
Direct salesCreate a product page, upload builds, issue license keys, send updates, and sell directly to the audience you bring.
Best for
Independent launches, paid downloads, and small catalogs.
How it starts
Self-serve digital product publishing
05
itch.io
Creator marketplacePublish free, paid, donation-supported, or early-access versions with a page you control and a creator community nearby.
Best for
Unusual tools, free releases, or pay-what-you-want experiments.
How it starts
Self-serve creator publishing
06
Your own site
Your own storeRun the product page, checkout, email list, customer support, and update schedule yourself. Keep other listings when they help people find you.
Best for
An established audience, bundles, and long-term brand building.
How it starts
Your release process and commerce stack
07
Publish the source
Open collaborationPut your code on a public site under the license you choose, with a playable demo and clear instructions for contributions.
Best for
Shared utilities, teaching tools, research, and portfolio work.
How it starts
Your chosen public site and license
Give buyers everything they need to use it.
The plugin or app is only the start of a release. You also need a product page, playable demo, screenshots, presets, compatibility details, version history, and a clear way to get help.
Let people try the actual instrument before they download or buy it.
Files for each system
Name each file so buyers know which system it works on.
Playable demo
Let people hear the actual instrument before they install it.
First preset
Give the instrument a sound that shows what it does in a few seconds.
Release artwork
Show the real instrument and its controls in the product image and screenshots.
Compatibility details
List the music programs, file types, systems, and known limits.
License and price
Explain the price and what buyers and contributors are allowed to do.
Changelog
Tell existing users what changed and whether they need to update.
Support
Give users one clear place to ask questions or report problems.
A credible release needs evidence, not marketplace badges.
The Syntho creator marketplace is not part of the current private beta. Release through an established store, your own site, or a public code host using facts buyers can verify.
A browser demo is useful evidence, but it does not prove every native format. Name only the builds and systems you have actually tested.
Build evidence
Run the project checks and target-specific validation for every format you plan to distribute.
Product truth
Use the real interface, playable demo, and representative presets. Do not advertise a mockup or an unverified target.
Release record
Publish compatibility details, a version number, changelog, license, known limits, and one support contact.
Commercial clarity
Confirm the current written sales permissions and long-term rights before taking payment from customers.
Make one instrument work in every place your users play.
Keep the sound separate from the app or device. Then adapt the same instrument for a browser demo, desktop plugin, audio files, or hardware.
Available now
available now
Web + AudioWorklet
Let anyone play the instrument without installing anything. A browser demo is the quickest way to hear it.
VST3 and CLAP
Use the same instrument in a desktop music program.
Standalone and offline render
Ship a small app or create audio files for sound packs, tests, or other releases.
Building next
in progress
Windows plugins and apps
Bring the same instrument to Windows when your audience needs it.
Linux plugins and apps
Bring the instrument to Linux music programs, including Ardour.
Files and publishing
Prepare the files needed for each system and publish them safely.
On the horizon
planned
AUv3 for iPad and iPhone
Use the instrument in music apps on iPad and iPhone.
AAX for Pro Tools
Reach Pro Tools users with AAX.
Give each version only what it needs.
A focused product should not carry an entire workstation inside it. Each version gets only the sounds, controls, and files it needs.
That keeps each version focused on the instrument. You make it once; each version gets the files it needs.
01
Your sound
Make the instrument, effect, or MIDI tool in the editor you already know.
02
The same instrument
Keep the sound separate from the browser, plugin, or device that runs it.
03
The physical product
Add the controls, connections, memory, and case the device needs.
One instrument, ready for every place your users need it.
SoonHardware options
Put it on hardware.
Build the instrument once, then bring it to a physical product with its own controls, connections, memory, and case. Design the device around the instrument instead of making it again from scratch.
For makers
Keep your attention on the sound and controls. Bring the same instrument to hardware instead of making it again from scratch.
For players
Try it in the browser or a music program, then use the same idea in a device you can touch.
For buyers
A hardware release should feel like the same instrument in a new form. The sound, controls, presets, and name should carry across.
Choose the kind of device that fits your product. The hardware version needs its own controls, connections, power, memory, and case.
Start with the instrument. Choose the device around it.
Electrosmith Daisy
Pedals, desktop instruments, and Eurorack modules.
Teensy 4.x + Audio
A maker ecosystem for compact instruments and effects.
Bela
Linux hardware for instruments and sensors.
MOD pedal hardware
A route to dedicated pedal hardware.
Raspberry Pi
Small standalone instruments, installations, and custom cases.
Choose how people get your instrument.
Sell the finished version, publish the code, give it away, or share the code and sell ready-to-use versions.
Sell finished builds
01Keep the code private, sell ready-to-use copies, set a price, and support your customers.
Publish the source
02Choose a license, explain how to build it, and invite people to learn, improve, and contribute.
Combine the two
03Share a useful core and sell ready-to-use versions, presets, content, or support.
Give it away
04Release it for free, accept tips, use it in your portfolio, or share it to help solve a problem.
You keep ownership of your module code.
The final license will explain what you can sell, how others can use the code, and whether any exclusivity applies.
Prepare the instrument for release.
Study working examples, build the interface, add your sound, create files for each system, and release it under clear terms.
The toolkit covers the path from first idea to a release ready for customers: reusable parts, a real interface, sound tools, files for each system, and everything people need to install and use it.
Examples and release templates
Finished instruments, effects, MIDI tools, interfaces, presets, and release examples you can study and adapt.
Controls and displays
Controls and displays that keep interface work in familiar web tools.
Audio and controls
A clear way to connect sounds, controls, events, saved settings, and files.
Add custom sound code
Add your own sound-building blocks when the included ones are not enough.
Create plugin and app files
Create the files needed for each kind of plugin or app.
Commercial terms before release
Confirm the current sales permissions, limits, and long-term rights in writing before charging customers.
Pricing and license details are not published yet.
We will share the price, update policy, sales rights, and support terms before version 1.0.
For now, explore the process and decide whether it fits your next instrument.
Your next release
Build the instrument once. Adapt it for the places your users play.
Start with the tool you wish already existed. Build it in the browser, ship it as a plugin, then choose whether to sell it, share it, publish the code, or adapt it for hardware.
We are building the stack from idea to instrument, and the network that helps good instruments find people.