UltimateAntiCheat

UltimateAntiCheat is a Windows usermode anti-cheat project for developers studying or adapting detection code. It is most suitable for open-source projects that can work with its licensing terms. Its range of process checks is useful as a reference, but it is not a turnkey commercial service.

Overview

The project focuses on common game-hacking vectors inside processes, with configurable checks and prevention options. Its maker positions it as educational rather than commercial software, and recommends integrating it into a game or application as source code or a static library—not as a standalone DLL. That makes it a better fit for developers prepared to inspect and adapt C++ code than for studios seeking a packaged anti-cheat deployment.

Its stated privacy approach avoids file-system scanning: it checks byte patterns in processes already open or created while the anti-cheat is running. That is a meaningful boundary, but not a guarantee of error-free detection. The maker specifically cautions against checking process window names and text in live use because of false-positive risk.

Key features

• Process and memory detection: Checks cover memory integrity, manually mapped and unsigned modules, debugger activity, process creation, and handles opened to the protected process. This gives developers several common attack vectors to study, but it does not provide server-side detection.
• Prevention controls: Options include remapping protected sections, blocking certain new threads, hiding threads from debuggers, and applying mitigation policies. These controls let integrators choose measures for their software; they do not make the project a complete hosted protection service.
• Optional heartbeat: A client-server mechanism can send clients a simple heartbeat every minute, and networking can be switched off in settings. This is a narrow networking function, not server-side cheat detection.
• Optional kernel approach: Settings support a hybrid kernelmode and usermode design, but users must supply or build their own driver. That adds substantial responsibility and makes the option unsuitable for teams expecting a bundled kernel client.
• Build and configuration: The C++ project supports CMake, with an LLVM/clang-cl option on a branch the maker warns may lag or contain errors. Settings are compiled into the program and edited in main.cpp or Common/Settings.hpp, so changing configuration requires source-level work and a rebuild rather than an external settings file.

Pricing

The UltimateAntiCheat plan costs nothing. It is an open-source educational project under AGPL-3.0, with no free trial. The zero price suits developers who can work with the source and its terms; it does not buy a commercial license or a managed service. The maker says projects using the code must also be open source, so closed-source commercial games should look elsewhere.

Platforms

UltimateAntiCheat is self-hosted and targets Windows PCs. Windows targeting is configurable at compile time; the README gives Windows 10 and Windows 7 or later as examples, while noting that some features need newer Windows versions. The project is not a kernel-level client by itself, and its hybrid option requires a separately provided driver.

Who it's for

This is best for developers learning about usermode anti-cheat techniques or adapting code for an open-source Windows game or application. It is less appropriate for teams that need a developer SDK, server-side detection, hardware bans, or a ready-to-deploy kernel client: those are not part of the stated offering. Teams should also be comfortable evaluating false-positive risks and maintaining source-level configuration.

Pros and cons

• Pro: A broad set of process and memory checks provides a concrete educational reference for common attack vectors.
• Pro: Optional prevention controls and configurable networking give integrators choices about what to enable.
• Pro: Avoiding file-system scanning may suit projects seeking a process-focused approach.
• Con: AGPL-3.0 terms require projects using the code to remain open source, ruling it out for many closed-source commercial integrations.
• Con: No SDK, server-side detection, hardware bans, or bundled kernel client limits its role as a complete production anti-cheat solution.
• Con: Compiled-in settings and the warning about false positives from window-name and text checks demand care from integrators.

Alternatives

Choose Easy Anti-Cheat if you want a freemium option with a free plan for studios of any size and broader listed platform support, including mobile, Linux, macOS, and web; its Core plan uses custom pricing.

Epic Online Services is a free-to-use alternative across several platforms, with no royalty or hosting fees, though service usage restrictions may apply. For single-player or offline games, AGINUZ Anti-Cheat Infrastructure offers a free Protected plan with per-player unique binaries and struct-field shuffling; its stated scope makes it a more focused choice for that use.

RoSentry has a free-forever web plan capped at 100 concurrent players and one active game, with community support and no moderation dashboard. Anybrain, GuardingPear Anti-Cheat, Byteria Game Anti-Cheat, and BattlEye are other options to compare; their listed platform and pricing models differ, but the stated facts do not support a more specific fit comparison.

For more options, browse Game Anti-Cheat Software.

Verdict

Choose UltimateAntiCheat if you want a free, source-level Windows reference for usermode checks and can keep your project open source under AGPL-3.0. Its educational scope, configurable controls, and process-focused approach are the main reasons to consider it. Look elsewhere if you need closed-source commercial integration, server-side detection, a supplied kernel client, or a packaged service.