G-Helper: a single-exe Armoury Crate replacement for Asus laptops
Lightweight Armoury Crate alternative for Asus laptops with nearly the same functionality. Works with ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook, ROG Ally, and more.
At a glance
- What is it?
- G-Helper controls performance modes, GPU switching, fan curves and battery limits on Asus laptops without installing a service stack. It is a good fit if you dislike Armoury Crate's footprint and a poor fit if you do not own Asus hardware.
- Who is it for?
- Adopt G-Helper if you own a supported Asus laptop and want performance modes, GPU switching and fan curves without Armoury Crate's service stack. Skip it if your machine is not Asus, or if you need the vendor's full software suite.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 28, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The problem G-Helper solves on Asus laptops
Asus ships Armoury Crate to expose performance modes, GPU switching, fan curves and lighting on its laptops. G-Helper positions itself as a lighter replacement that offers "almost same functionality with a much smaller footprint". The README lists supported families: ROG Zephyrus G14, G15, G16, M16, X13, X16, Z13, DUO, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook, and the ROG Ally or Ally X. That is a wide net, but it is still an Asus-only net. The project's own topics include ally, amd, asus, aura, cpu, fan, g14, g16, ghelper, gpu, intel, mux, nvidia, overclock, power, rog, strix and tuf, which tells you the intended audience: people who already own this hardware and want control over it. If you are shopping for a cross-vendor tuning utility, this is not one. The value is in the overlap between what Asus hardware exposes and what the vendor utility charges you in background processes.
How G-Helper talks to the hardware
The README is explicit that the performance modes are not invented by the app. A note states that all modes are "baked into BIOS along with default fan curves and power limits" and are "the same thing" as in Armoury Crate. G-Helper is a front end over firmware settings that already exist. The three built-in modes are Silent, Balanced and Turbo, and each is paired with a matching Windows Power Mode: Silent with Best power efficiency, Balanced (Performance in AC) with Balanced, and Turbo with Best performance. Those pairings are adjustable under Fans + Power. The GPU side has four modes. Eco enables only the low-power integrated GPU, which drives the built-in display. Standard is MS Hybrid, with both iGPU and dGPU enabled and the iGPU driving the display. Ultimate also enables both but lets the dGPU drive the built-in display, and the README notes this is supported on 2022 and newer models. Optimized disables the dGPU on battery and re-enables it when plugged in. On top of that sits an automation layer: performance mode switching on battery versus AC, auto screen refresh rate at 60Hz on battery and maximum when plugged in, and keyboard backlight timeouts. The design is a control surface plus a small set of rules, not a driver stack.
Installing G-Helper and setting a first fan curve
The README's download path is a direct link to GHelper.exe in the latest release, and the advantages section says the app is "just a single exe to run" that "doesn't install anything in your system". So the install story is: download the executable and run it. There is no package manager step documented in the README.
# Download the latest release executable from the project's release page
# https://github.com/seerge/g-helper/releases/latest/download/GHelper.exeThe README does not document a command-line interface, so configuration happens in the window. After launching, the first useful stop is the Fans + Power section, because that is where the BIOS mode to Windows Power Mode pairing lives and where custom fan curves and power limits are edited per performance mode. The README describes a custom fan curve editor, power limits and turbo boost selection for every performance mode. A reasonable first session is to leave Silent and Balanced alone and adjust Turbo only, so you have a known-good fallback. If you want the automation instead of manual switching, the README lists Optimized GPU mode, which disables the dGPU on battery and enables it when plugged in, and auto screen refresh rate, which drops to 60Hz on battery and returns to maximum when plugged in. Both are documented as automation features rather than defaults you must enable by hand, but the README does not spell out the exact toggle names.
Where G-Helper stops being the right tool
The clearest limitation is hardware scope. The README's model list is long but closed: ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook and the ROG Ally. A desktop motherboard, an HP laptop or a non-Asus machine is outside that list, and the repository's own topics reinforce the Asus-only framing. The second limitation is that G-Helper does not replace the firmware. Because the modes are baked into BIOS, the app can only expose and combine what the firmware already supports. If your model's BIOS does not expose a given power limit or fan curve, the app cannot conjure it. Third, features are model-gated in ways the README admits: Ultimate GPU mode is called out as supported on 2022 and newer models, which means older machines get a smaller feature set. Fourth, the README's feature list is broad enough that expectations can run ahead of reality. Anime Matrix or Slash Lighting control only matters if your chassis has that hardware, and XG Mobile control only matters if you own the external GPU. Finally, the README does not document rollback or recovery if a mode change leaves the machine in an unexpected state. The wiki has a Troubleshooting page, but the README does not describe what to do, which is a gap worth knowing about before you change power limits.
G-Helper versus Armoury Crate, and versus the BIOS alone
The honest comparison is not G-Helper against a rival open source project, because the README frames the choice as G-Helper against the vendor utility. Armoury Crate is Asus's own software and is the reference implementation for these settings. G-Helper's stated difference is footprint and packaging: a single exe that installs nothing, versus a full suite. The README also states the modes are the same thing as in Armoury Crate, so you are not trading capability for weight in the mode system itself. What you do trade is the rest of the vendor ecosystem. Armoury Crate bundles update and peripheral tooling beyond what G-Helper lists, and G-Helper's own driver update feature is described only as an automatic BIOS and driver update check in the README, which is thinner than what the vendor suite offers. The second alternative is doing nothing: the BIOS already contains the modes, so you can switch them from firmware setup. That is free and needs no software, but it is a reboot per change and gives you no fan curve editor, no battery charge limit and no automation on AC versus battery. G-Helper sits between those two: more convenient than the BIOS, less sprawling than the vendor suite.
Maintenance, licence and what releases look like
The repository is not archived, and the last push was on 2026-09-21, the same day as the most recent data point. Releases are frequent: v0.285 on 2026-09-20, v0.284 on 2026-09-16, v0.283 on 2026-09-11. That cadence means upgrade cost is low in effort but non-zero in attention, because a single exe has no package manager to pin a version for you. You replace the file. On the licence side, the project is GPL-3.0, which matters if you intend to redistribute it or build on the source in the app/ directory. For personal use on your own laptop, the practical implication is that the software is copyleft and you should read the LICENSE file in the repository root rather than assume permissive terms. The README also links translations into Chinese, Japanese, Czech, Spanish and Korean, which suggests documentation maintenance is distributed across contributors rather than centralised. None of this is legal advice; the repository root contains the LICENSE file if you need the exact terms.
Editorial conclusion
Adopt G-Helper if you own a supported Asus laptop and want performance modes, GPU switching and fan curves without Armoury Crate's service stack. Skip it if your machine is not Asus, or if you need the vendor's full software suite. Before installing, check the model list in the README against your exact machine and read the Requirements and Troubleshooting wiki pages, because the README itself does not document rollback if a mode change misbehaves.
Frequently asked questions
What is G-Helper?
G-Helper is a lightweight Armoury Crate alternative for Asus laptops, described in its README as offering almost the same functionality with a much smaller footprint. It controls performance modes, GPU modes, fan curves, power limits, battery charge limits and lighting.
Which is better, G-Helper or Armoury Crate?
The README states the performance modes are baked into BIOS and are the same thing as in Armoury Crate, so the mode system itself is not a differentiator. G-Helper's stated advantage is packaging: a single exe that does not install anything in your system.
Do I need to uninstall Armoury Crate to use G-Helper?
The README does not say that Armoury Crate must be uninstalled, and it does not describe a coexistence procedure either. It only states that G-Helper installs nothing in your system. Treat this as an open question and check the project's Setup and Requirements wiki page.
Is G-Helper only for Asus?
Yes. The README lists ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook and the ROG Ally or Ally X, and the repository topics include asus, rog and tuf. Non-Asus hardware is outside the documented scope.
How do I install G-Helper on an Asus laptop?
The README points to a direct download of GHelper.exe from the latest release and describes the app as a single exe that installs nothing in your system. There is no package manager step documented in the README.
How do I undervolt the CPU or GPU using G-Helper?
The README lists NVidia GPU overclocking and undervolting and AMD CPU undervolting and temp limits as features, and describes per-mode GPU tweaking including Core and Memory Clock offsets, GPU power, Dynamic Boost and Temperature Limit. It does not give step-by-step undervolting instructions, so the exact controls are not documented in the README.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/seerge-g-helper)