Update, 28 August 2026: this is now out of date. OSBot has stopped taking payments and is winding down once existing subscriptions expire. The analysis below still explains why — but for what it means for your accounts, read OSBot is closing, and what to do next.
OSBot is still up.
That is not the same as safe.
OSBot alternative · OSRS bot client shutdowns · injection vs native automation
Let us start with the thing everyone checks first: osbot.org still loads. The forum is there, the client downloads, people are still posting. So why is this page called what it is?
Because 2026 was not about websites going offline. It was about one architecture becoming a liability, and OSBot is built on it. This page explains which architecture, why it mattered, and what your options are — written by a competitor, so check the claims rather than taking them on trust.
2026 did not come
for every client.
It came on a specific date. On 28 January 2026 Jagex discontinued the Legacy Java Client as a standalone option, and said plainly why — describing it as part of their efforts to reduce “illicit activity such as botting”. RuneLite and HDOS were explicitly unaffected. The Java client that bots injected into was not.
That way is injection. The client attaches to the running game process, reads its memory or hooks into it, and drives the game from the inside. It is fast, it is precise, and it leaves something attached to the game that should not be there.
Anti-cheat does not have to infer anything from your mouse movement when there is a modified client sitting in front of it. The client itself is the evidence. That is the single sentence that explains 2026.
RuneMate, DreamBot, TriBot and PowBot all built on that surface, and all came off the board. OSBot built on it too — and rather than close, they went back to the start and wrote a brand new client from scratch. That is a serious piece of work and worth acknowledging. It also means the thing you would download today is a young product wearing an old name, not the mature one people spent years recommending. The longer version, with sources, is here: what happened to the clients that shut down.
Two designs.
One of them aged badly.
We sell the second one, so read this as a competitor's argument rather than a neutral review. Every row is something you can check yourself.
We do not publish a ban-rate percentage, ours or anyone else's, because nobody can substantiate one. The architectural claim above is checkable; a percentage would not be.
No proxies means
one account.
The rebuilt OSBot client does not support proxies. Not partially, not with a workaround — the feature is not there. The old Java client had proxy settings; the rewrite has not brought them back.
If you run one account for fun, that may genuinely not matter to you. If you run more than one, it is the end of the conversation.
Every account you run goes out of your home IP. Ten accounts, one address, one household — and nobody needs to detect any of them individually to work out that they belong together. Accounts sharing an IP are one of the few things that reliably get actioned in batches, on any client. That is the difference between losing an account and losing a farm in an afternoon.
There is no clever way round it either. You cannot patch a missing feature with better behaviour, and a VPN puts every account on the same shared address, which is its own pattern. Our client handles proxies per instance, and we sell the proxies as well if you would rather get both from one place. How we suggest configuring a farm is in account setup.
Move gradually,
not all at once.
Your OSBot scripts do not transfer — no client's do. That is a real cost of switching and we are not going to pretend otherwise. What transfers is the accounts, which were never tied to a client in the first place.
Straight
answers.
Updated