ReaKit is basically my way of making JSFX in REAPER feel like a real plugin ecosystem, not just a bunch of random scripts.

If you’re a developer (or you’re learning), you already know the problem: you come up with a fire idea… then you spend 80% of your time rebuilding the same boring stuff—knobs, meters, smooth controls, consistent layout, gain safety, all that. And every time you start a new plugin, it’s like starting a whole new project from scratch.

ReaKit fixes that.

It’s two things at once:

It’s a bundle of finished plugins you can mix with right now (the “tools”), and it’s a shared foundation that all those plugins are built on (the “kit”). That foundation is the part that matters to developers, because it lets you build new stuff faster without your plugin feeling homemade.

So when I say “ReaKit,” I’m not just talking about one compressor or one EQ. I’m talking about a consistent look, consistent behavior, and consistent workflow across everything. Same vibe, same feel, same type of metering, same type of interaction. You can open any ReaKit plugin and you’re not lost—you’re home.

And the goal isn’t to make “developer-only” tools nobody uses. The rule is simple: if it’s part of the kit, it shows up in real plugins. Meaning it’s tested in actual sessions, not just theory.

This is also why updates like v1.1 matter. Sometimes the update is a new plugin (like ExpressBus), and sometimes it’s the less flashy stuff—performance, stability, smoother controls, better metering behavior—things you don’t notice until they’re missing. 

If you’re building JSFX and you want your plugins to feel clean and consistent without reinventing the wheel every time… that’s what ReaKit is for. It’s the kit I wish I had when I started trying to make REAPER plugins look and feel like something you’d actually want to use every day.

Welcome to Reaper Remix. More updates coming.