Your F75’s lighting and shortcuts, from one small tray app
F75 Studio sets the AULA F75’s lighting from Windows: the built-in effects, colour, brightness and speed, or a colour for every key, with a live preview of the board. Screen sync turns the keys into an ambilight for whatever is on screen. A visual builder writes your shortcuts as an AutoHotkey v2 script and runs it. It lives in the tray. Free and MIT-licensed; not affiliated with AULA.
The challenge
The F75’s lighting lives in AULA’s own software, and nothing else can reach it: there is no public SDK. Shortcuts are a separate job again, in AutoHotkey scripts written by hand.
The approach
We reverse-engineered the F75’s USB lighting protocol and documented it in the repository. F75 Studio speaks it directly, with every write checked against an allowlist of known-safe commands and the keyboard’s identity; firmware and other risky commands are never sent. Screen sync streams live frames that never touch the keyboard’s flash, and the hotkey builder turns a recorded key and a chosen action into an AutoHotkey v2 script.
Connect the keyboard by USB cable. Over Bluetooth or the 2.4 GHz dongle, settings are saved but not sent.
Choose an effect, a colour or per-key colours, or turn on screen sync; save it as a profile.
Record a key, choose what it does, and Apply. F75 Studio writes hotkeys.ahk and runs it with AutoHotkey v2.
Switch profiles from the tray menu or a hotkey, and manage your other scripts from the same app.
The keyboard’s own effects — Static, Breathing, Rainbow, Ripples, Retro snake, Neon stream, Twinkling stars, Sine wave and more — with colour, brightness and speed, and a live preview of the board. Or give every key its own colour.
Edges mode works like an ambilight: the F-row follows the top of the screen, the bottom row the bottom, the side columns the left and right. Blur mode gives each key the blurred colour of the matching spot on screen.
Save setups as profiles and switch between them from the app, the tray menu, a hotkey, or with --profile on the command line.
Record a trigger and pick an action: send keys, remap a key, type text, run a program or URL, media keys, switch lighting profile, disable a key, or your own AHK code — everywhere or in one app only.
Your other .ahk scripts in one list: start, stop and edit them, run them at startup, with automatic backups.
Every write passes an allowlist of known-safe commands and an identity check, and screen-sync frames are volatile. The capture is shrunk on the GPU to a tiny image; nothing is saved or sent anywhere.
AULA F75 owners
Set the effect, colour and brightness from a small Windows app, and keep a profile for each mood to switch with a hotkey.
Watching and playing
Turn on screen sync and the keys pick up the colours at the edges of the picture, live.
Keyboard-heavy work
Remap a key, type a snippet or launch an app from a recorded shortcut, and read the AutoHotkey code it generates.
What we did
Yes, and open source under the MIT license.
No. F75 Studio is independent and not affiliated with AULA. It talks to the keyboard through a protocol we reverse-engineered and documented in the repository.
Every write is checked against an allowlist of known-safe lighting commands and the keyboard’s identity; firmware and other risky commands are never sent. Screen sync uses live frames that are not written to the keyboard’s flash. It is in beta: the lighting has not yet been checked on every firmware.
Lighting changes need the USB cable. Over Bluetooth or the dongle, your settings are saved but nothing is sent to the keyboard.
For hotkeys and the script manager, yes: they run with AutoHotkey v2. Apply writes Documents\F75Studio\hotkeys.ahk and starts it.
No. Screen sync reads the screen with DXGI Desktop Duplication, shrinks it on the GPU to a tiny image for the key colours, and saves or sends nothing.
Open the product, or talk to us about building something similar for your team.