Comparison
ShintTools vs nunu.ai
nunu.ai runs cloud AI agents that play your build like a human tester. ShintTools lives inside the editor and CI, validating code, assets and performance — with your IP never leaving the studio. Different pipeline stages, different privacy posture.
| Capability | ShintTools | nunu.ai |
|---|---|---|
| 100% local execution (no data egress) | ||
| Runs inside Unity & Unreal Editor | ||
| Validates source code (C++, C#, Blueprints) | ||
| Asset & naming validation | ||
| Performance prediction before build | ||
| Black-box runtime QA (plays the build) | ||
| CI-native gate per pull request | ||
| Deterministic, reproducible output | ||
| Requires uploading build to a cloud | ||
| Multi-platform device testing (mobile, PC) | ||
| Pricing model | Per studio (€39–149/mo) | Cloud usage-based |
Bottom line
Choose nunu.ai when…
You need end-to-end post-build QA (an agent that plays the build on real devices) and your studio can ship builds to an external cloud.
Choose ShintTools when…
You want to catch issues before the build — code, assets, naming and performance — from inside the editor and CI, without IP leaving your network. Ideal for AAA, licensed IP and strict NDAs.
FAQ
Are they direct competitors?
Only partially. They solve different pipeline stages: ShintTools prevents issues inside the editor and CI; nunu.ai catches runtime issues by playing the build. Some studios use both.
Can I use ShintTools under strict NDAs?
Yes. Everything runs on your network. Source code, assets and builds never leave the studio. That's our default posture, not an enterprise add-on.
Does ShintTools also test the runtime build?
Not our focus. ShintTools prevents issues before the build (code, asset, naming validation and performance prediction). For end-to-end runtime QA, nunu.ai is complementary.