Rift Companion Review: The Only Native macOS Overlay for League of Legends

For Windows League of Legends players the overlay category has been settled for years. Porofessor, Blitz, and Mobalytics all run on Overwolf, which is a battle-tested overlay framework the community has vetted heavily. If you play on Windows, you have three good options and a bunch of forum debates about which one is best. On Mac, the entire conversation has been 'alt-tab to a browser tab for op.gg.' Overwolf does not run on macOS. So while Windows players have been getting matchup builds pinned to their screen since 2018, Mac players have been context-switching every ten seconds between the game and Safari. Rift Companion is the first product to close that gap natively — no Overwolf, no cross-platform port, no dual-booting workaround. It is a Mac app built for the Mac client.

The three-step onboarding is close to the ideal case: open League, lock a champion, load in. That is the flow. There is no login page. There is no API key to paste. There is no Riot ID field. Rift Companion detects the client on its own; the moment champion select resolves, popular runes and build panels appear pinned beside the game; when the loading screen ends, the panels pin to your live game and stay put. The reason this matters is that overlays only get used if the friction to first-value is close to zero. Anything that asks a player to configure something before their first game will lose them at the sign-up screen. Rift Companion asks for nothing — you download the DMG, drag it to Applications, launch it, and the next time you queue, the panels are there.

Once you are in a match, Rift Companion pins a set of panels to the side of the game window. Champion select is where the value density is highest: popular runes come from op.gg (with rune icons and keystone descriptions pulled from Riot's official Data Dragon), and matchup-specific builds sit alongside a matchup verdict that flags the lane as favored, even, or unfavored, with skill order and summoner spells attached. Every recommendation carries its source and the current patch, so you can see where the pick came from rather than trusting a black-box 'AI recommendation.' The loading screen surfaces a quick opponent scout — ranks, LP, and recent win rate — so you know who you are queuing against before you spawn. In-game, four things earn their keep. First, panels stay pinned in the layout you dragged them to — and Rift Companion remembers the position separately for Summoner's Rift, ARAM, and Arena, which is the kind of small detail that shows the developer actually plays the game. Second, enemy summoner-spell cooldowns are tracked by a manual click when you burn a Flash or a Teleport, with the display format configurable between seconds, m:ss, and full minutes. Third, holding Tab surfaces the gold-lead read: how far ahead of (or behind) your lane opponent you are, with per-champion totals and the team lead broken out by side. Fourth, the build panel is inventory-aware — it shows the next item to buy and the remaining gold once your current items are accounted for. None of this requires you to reach for a browser.

The single most important design decision in Rift Companion is what it does not do. It is read-only. It talks to the League client through Riot's own local APIs. It does not read the game's memory. It does not inject anything into the process. It never sends input to the game — including the cooldown timers, which are marked by your click rather than screen-scraped. And on macOS it needs zero permissions by default; the standard macOS Accessibility grant is optional and only surfaces if you enable a specific hotkey feature. The founder's phrase in the FAQ is direct: 'No. It reads, you play.' That constraint is not arbitrary. Riot's Vanguard anti-cheat shipped as part of the macOS League client in early 2025, and anything that automates gameplay, reads game memory, or injects into the process is likely to trip it. By staying strictly on the read-only side of the line — running as a normal Mac app that reads public Riot data and lays it out on top of the window — Rift Companion sits in the same category as looking at op.gg on your second monitor, just without the alt-tab. Rift Companion is not endorsed by or affiliated with Riot Games; the design posture is what makes it safe to run alongside Vanguard, not any special relationship.

Rift Companion is free. There is no premium tier, no waitlist, no 'sign up for the beta,' and no credit card anywhere in the flow. It is not open source — it is closed-source and distributed as a Developer ID-signed, Apple-notarized DMG that you download from the site — but that is the same trust chain used by Discord, Slack, 1Password, and every other production Mac app that ships outside the App Store. The download-verification steps, SHA-256 checksums for each release, and the changelog are all public on the GitHub repo, and updates ship through Sparkle (the standard Mac auto-update framework) starting with version 1.3. The trade-off in this distribution model is straightforward: the App Store version does not exist, so users who insist on sandbox-only App Store apps will need to look at the verification guide before installing. In exchange, the developer can iterate on features and ship updates without going through App Store review, which for a niche tool with a small audience is the difference between shipping weekly and shipping quarterly. For most players, the Apple notarization is enough.