Build it. We will do the rest.
Independent developers and sample makers sell inside Razor Studio, not just next to it. You keep eighty-five percent for the first two years, and you never touch a tax form.
For the first two years
No annual fee either
Of every month
One submission covers all
Move the sliders. That is your number.
No tiers, no negotiated rates, no better deal for someone with a bigger following. Everyone starts at eighty-five percent and stays there for two years.
The parts you did not get into this for.
Most independent developers spend more time on tax registration and refund emails than on DSP. All of that sits on our side of the line.
VAT and sales tax
Charged, collected and remitted in every country we sell to. You never register anywhere, never file anything, never answer a letter from a tax office you have not heard of.
Payouts
On the fifth of each month, for the previous month, from the first dollar. No minimum threshold holding your money hostage until you reach a hundred.
Refunds and chargebacks
We handle the conversation and absorb the chargeback fee. A refund reverses your share, nothing more — you are never out of pocket beyond the sale itself.
Hosting and delivery
Your builds sit on our CDN and download at full speed everywhere. No bandwidth bill that grows the month you get a good review.
Licensing
Licences bind to the buyer account, not to hardware. No serial system to build, no activation server to keep alive at three in the morning.
Invoices and reporting
Buyers get their invoice automatically. You get monthly statements, and the EU seller reporting is filed on your behalf.
Bought here, installed there. One click.
A buyer who already owns your plugin sees a Plug in to Razor button on your page. Pressing it installs and licenses the plugin inside the program — no download folder, no installer, no serial to type, no support email asking where the file went.
That is the difference between selling a file and selling a product. Every step a buyer has to perform after paying is a step where they get frustrated with you rather than with the store.
1
On your product page or inside the program
2
Bound to the account, not to a machine
3
One press — installs and authorises
4
Ready to load, already licensed
You always get a reason and a date.
Submitting into silence is the fastest way to lose a developer. Every submission gets a written result, and every rejection gets a specific list.
Submit
Upload the builds, write the description, add screenshots and demos. You can save a draft and come back.
Technical check
We install it on all three systems, load it in the host, rescan with no instance open, and check that nothing calls home uninvited.
Result, in writing
Approved, or a specific list of what to fix. Never a rejection without a reason — and the list is quoted in your dashboard, not buried in an email.
Live
Your product page goes up with its own address, indexed, with a plug-in button for buyers who already own it.
Published before you submit.
Every check we run is listed here, in advance. A rejection you could have predicted is a week you did not need to lose — and the second time it happens, you stop submitting.
Builds for macOS (universal), Windows x64 and Linux x86_64
Signed and notarised on macOS, signed on Windows
Survives a plugin rescan with no instance loaded
No network calls without an explicit user setting
Samples cleared for commercial use, with proof of licence
Uninstalls cleanly and leaves nothing behind
Send us what you have.
Even if it is not finished. We would rather see a working prototype and tell you early whether it fits than have you spend six months on something we cannot list.
Applications are read by a person, usually within two working days.