About
Built by a developer who
needed it first.
PlayProbe is made by Jakub Gabčo, a Unity developer of nine years working as Drages Studio in Brno, Czechia. It grew out of eight years of contract work in VR, where getting usable playtest feedback turned out to be harder than building the thing being tested.
Who builds PlayProbe
I've worked in Unity for about nine years. Before that I was a Node.js developer, which is why the web side of PlayProbe doesn't feel like a game developer's first website.
For the last eight of those years I've worked as a contractor for Sense Arena, a VR sports-training company — roughly 95% VR development, the rest web and React Native. Most of that time went into NHL Sense Arena.
Through Grip Studios I also worked on Redfall, the co-op shooter from Arkane Austin, supporting their AI team — I'm in the end credits. A good deal of the rest of my work sits under NDA and can't be listed here.
Drages Studio is the name I work under, not a company with staff behind it. PlayProbe is solo-built: I write the code, answer the support email, and make the calls.
Why PlayProbe exists
At Sense Arena we tried to playtest properly, and getting good feedback back was consistently hard — especially for multiplayer sessions, where you can't sit behind every player and watch. Sessions would finish and the useful detail would already be gone, leaving a form nobody wanted to fill in.
So we built some in-game feedback: ask the question inside the session, at the moment it's relevant, instead of hoping someone reconstructs it afterwards. That worked far better than the surveys had, and it's where the idea for PlayProbe came from.
That's still the core of it. Surveys before and after, feedback captured during, and the results aggregated so you're reading a pattern rather than a pile of opinions.
Bootstrapped, no VC
No investors, no growth targets set by someone else. PlayProbe has to earn its keep from people who find it useful, which is the only reason it needs to exist.
No dark patterns
The free plan is genuinely free and stays that way. Cancelling is not a maze, and nothing is designed to get testers to hand over data they didn't mean to.
Built on a real problem
PlayProbe started because I needed it at work, not because playtesting looked like a good market. Every feature so far has come from a session that went badly.
What's next
The Unity SDK is the one that exists today. Unreal and Godot SDKs are what I want to build next, so mid-game feedback isn't Unity-only — I'm not putting a date on them, because I'd rather ship them late than promise them early. Everything else is driven by what people actually ask for.
Who you're dealing with
PlayProbe is operated by Jakub Gabčo, trading as Drages Studio — a self-employed sole trader (OSVČ) registered in Brno, Czechia, IČO 06831109. If you'd rather read the specifics than take my word for it, they're in the Terms, Privacy Policy and Data Processing Agreement.
Questions, bugs, or a feature you need — email [email protected] and it comes straight to me.
Try it on your own game
The free plan covers 1 game, 3 tests and 20 sessions per test — enough to see whether the feedback is any better than what you're getting now.
Start free