The key system is not a feature, it is friction. shinobi resolves it server-side: one tap on “receive key”, about eight seconds, and the session is yours for 24 hours.
The client intercepts the key hand-off and talks to our resolver directly — no wrapper, no tutorial image.
No browser tab, no redirect chain. The link goes straight to the resolver.
Our backend walks the checkpoint chain. Most of the wait is the upstream cooldown, not us.
The key is copied and the 24-hour session is stored. Reopen the executor whenever you want.
Everything here exists because it removes a step — not because it looks good in a screenshot.
The resolver ships with the client. Nothing extra to configure.
Repeat unlocks hit a 24-hour cache and return in milliseconds.
Assets are versioned and re-applied on launch, so an update never leaves a half-styled UI.
The client polls /version and links you straight to the new build.
No companion app, no second download, no “install this helper first”.
| Area | SHINOBI |
|---|---|
| Unlock | One tap, fully automatic, about 8 seconds |
| Session | 24 hours per unlock |
| Reopening the app | Straight to the executor |
| Ads and offer walls | None |
| Extra downloads | None — one APK |
Once per 24 hours. The unlock lasts a day, then one more tap refreshes it.
No. The resolver only receives the authorization link you submit and returns a short-lived key.
It is the full client build with the executor kernel inside. Trimming is on the list.
The resolver has to follow. The app tells you when a new build is out.
Anonymous usage signals only, to keep the resolver healthy — full text in the Agreement.
Android 8.0+ · — · —