FiveM’s future deserves scrutiny, but a prediction of its downfall is not a verified operating status. As checked on 10 September 2026, Cfx.re has released FiveM for GTAV Enhanced in early access and published further development and testing updates. This article separates those records from older reporting about the acquisition.
What the 2024 report established—and what it did not
GTA Focal’s 6 August 2024 report described alleged workplace problems using unnamed former staff and other sources. It also offered an estimated purchase price and predictions about a separate Rockstar modding project. Those are attributed reports and projections, not figures or outcomes independently verified by RPCrate. The report said Rockstar had not responded to its request for comment.
That reporting should not be rewritten as an official admission or dismissed merely because later products were released. It also does not establish that FiveM has closed, that all developers left or that a forecast replacement shipped on schedule. The previous version of this page blurred these distinctions and used unrelated historical embeds; those have been removed.
A confirmed change: parts of Enhanced become closed source
In March 2026, Cfx.re announced that some portions of FiveM would move from open to closed source for GTAV Enhanced, citing deeper integration with the base game. This is a concrete change for developers who depend on inspecting or modifying the platform. It reduces public access to those portions; it is not proof that every community script becomes closed source.
Cfx.re’s source-code change announcement
Continued development does not eliminate migration risk
The official 21 July 2026 release made Enhanced early access available and warned of bugs and missing features. Its July development update described networking, runtime and diagnostic changes. The August public stress-test calendar invited further testing. These document ongoing work, while performance benefits remain something each operator should measure on their own workload.
Official Enhanced early-access release
For a practical decision, keep a working backup, test critical resources on a separate instance and record failures reproducibly. Evaluate documentation, support responses, source availability and release changes over time. Avoid treating either promotional benchmarks or a dramatic headline as a substitute for that evidence.