A milestone or publisher review is coming.
You want to know what will break before someone else finds it.
Risks listed while there is time to act
Unreal Engine technical audit
A fixed-scope review of your Unreal project by the people who would fix it. You get a written report with what we found, the evidence, and a prioritised fix list with a rough effort estimate for each item.
1. Summary: the issues that matter most, in order
2. Findings, each with
- evidence: capture, log or code reference
- impact on players or on the team
- recommended fix and rough effort
3. Quick wins that take under a day each
4. Risks to the next milestone
5. Suggested next stepsWhen an audit pays off
You inherited a codebase.
The people who built it have left, and nobody knows which parts are safe to change.
A map of the code and its weak spots
Something is wrong and nobody knows where.
Frame time, bandwidth or build times got worse and the cause is unclear.
The cause found with captures and logs
What an audit can cover
Most audits cover one or two of these areas. We agree the scope, the deliverables and the price before we start.
Code and architecture
Module structure, gameplay framework use, Blueprint and C++ split, and the parts most likely to cause bugs.
Performance
CPU, GPU and memory captures on your target hardware, with the biggest costs ranked.
Networking
Replication cost per actor, prediction, server performance and online services setup.
Build pipeline
How builds are made, how long they take, what is tested and where the process fails.
Content and memory
Texture, mesh and audio budgets, streaming setup and asset validation.
How an audit runs
Agree the scope
Which areas, which builds and which questions the audit has to answer, plus the price and delivery date.
Access and captures
Read access to your repository and a build we can run, then captures on your target hardware.
Review
Code reading, profiling and interviews with your leads where something needs context.
Report and walkthrough
The written report, then a call where we go through it with your team.
Who does the audit
See the whole team.
FOUNDER
David
Founder & Lead DeveloperLeads every audit and reviews code and architecture.
Yura
Multiplayer & Online EngineerJoins for networking and online services.
George
Technical ArtistJoins for GPU, lighting and content budgets.
Andrew
Build & Tools EngineerJoins for the build pipeline and source control.
In practice
What happens during an audit
After the scope call, most of the work is reading code and taking captures; we only interrupt your team when something needs context.
Findings are written down as they come in, each with its evidence, and anything serious is raised as soon as we confirm it. At the end we rank the findings by impact and effort and go through the report with your team on a call.
Technical audit FAQ
Is the audit fixed price?
Yes. The price is agreed together with the scope, before any work starts.
Do we have to hire you to fix the issues?
No. The report is written so your own team can act on it. If you want us to do the fixes, we quote them separately.
What access do you need?
Read access to the repository, a build that runs on your target hardware, and someone on your team who can answer questions for an hour or two.
Related services
Start a project
Tell us about the project
Send us the engine version, where the project is and the work you need done. We reply within two business days with who we would put on it, or tell you it is not a fit.
Prefer email?hello@moduleforge.studio