AI Booster
What AI Booster is, every platform it ships on, the protocols it reads, and where to go next — the entry point to the AI Booster documentation.
AI Booster
AI Booster is a connection client. You supply a profile — a node link or a subscription from a provider — and it routes your traffic through it, either by proxying the applications you point at it or by tunnelling the whole device.
It does not come with a network. Which endpoints you reach, and who operates them, is decided entirely by the profile you import.
Where to start
📦 Install
Per-platform guides, with the permission each one asks for
📋 Add a profile
Subscriptions, node links, and the difference between them
🔧 Settings
Service modes, ports, TUN — what actually gets routed
🔍 Troubleshooting
Connected but nothing loads, and the rest
Every platform
| Platform | Store | Direct |
|---|---|---|
| iOS / iPadOS | App Store | — |
| macOS | App Store | DMG, from the download page |
| Android | Google Play | — |
| Windows | Microsoft Store | Installer, from the download page |
| Linux | — | GitHub Releases |
Two platforms ship two different builds. On macOS, the App Store version tunnels through a sandboxed app extension while the DMG uses a system extension you approve once. On Windows, the Store and installer versions are separate codebases with independent version numbers — the Store build is native on ARM64 and the installer is not. The installation guides cover both.
The Linux client is open source — the interface, not the tunnelling engine, which is a separate program under a different licence. See aibooster-linux.
What it reads
Individual node links, by scheme:
vless:// · vmess:// · trojan:// · ss:// · hysteria2:// (also hy2://,
hy://) · tuic:// · wg:// · ssh:// · warp://
Plus a WireGuard configuration pasted as text, recognised by its [Interface]
header, and an http:// or https:// subscription URL that is fetched and can
be refreshed.
Support is not identical on every platform or every build. If a specific protocol matters to you, confirm it in the app you have rather than assuming from this list.
Where your traffic goes
This is the part worth reading before you import anything.
Traffic routed through a profile reaches the endpoints, DNS resolvers and other services that profile names. Those operators can see and process your connection data under their own terms — not ours. AI Booster is the client; it does not change who is on the other end.
So the profile is the trust decision, not the app. Import from a provider you have a reason to trust, and treat a subscription URL as a credential: anyone holding it can use your service.
Never import a configuration file from an untrusted source. A profile can point your traffic anywhere and set the resolvers that decide what a name means.
Plans
Feature availability and pricing are shown in the app and on the final purchase sheet, which is what controls the price you pay. See pricing for the current plans.