wrong timing
Pursue the relationship now. Do not claim application readiness yet.
The Service Partner Program is the correct Unreal analogue to ForgeFX’s Unity relationship, but Epic’s current program is invitation-only. ForgeFX now has credible, current Unreal delivery evidence and a strong simulation specialization. The published experience threshold and four-project-per-practitioner threshold are not yet proven. The winning move is a sponsor-led qualification conversation, followed by a deliberate evidence-building year.
The published bar is higher than “we use Unreal”
Epic says every Service Partner is vetted through skills assessment and technical interviews. Applications are not open; organizations are invited by Epic after relationship-building and qualification.
Not yet documented
Current evidence does not clear this bar
One flagship case; portfolio still thin
Strong strategic fit
Relationship needs a named owner
ForgeFX is directly in-category
There is a real Unreal story now
The strongest proof is no longer a hypothetical capability statement. It is a completed enterprise simulation engagement with production architecture, client feedback, and follow-on demand.
Government-funded mixed-reality training
ForgeFX delivered Unreal Engine-based digital equipment simulations under an ARA subcontract. The work translated existing Unity behavior into C++ and Blueprints, rebuilt interaction/state logic, integrated with the host training platform, and packaged reusable Unreal assets.
Complex systems, not a beauty render
The scope included baseline project setup, API and communication pipelines, state-machine behavior, custom interactions, device accessories, UI, animation, QA, packaging, and client integration support. That aligns directly with Epic’s tool-builder and problem-solver criteria.
Client wants the next phase
Production reporting says the client was happy with ForgeFX’s work and was discussing more devices and deeper behaviors, including new digital twins built directly in Unreal. Final delivery was scheduled for July 31, 2026.
Qualification scorecard
| Program dimension | ForgeFX evidence | Read |
|---|---|---|
| Industry expertise | 25 years in custom simulation; defense, industrial, medical, equipment, XR, training systems. | Strong |
| UE project delivery | One substantial Unreal engagement covering multiple interactive device modules and integration work. | Credible, not broad |
| UE team tenure | Internal sources identify experienced simulation and C++ talent, but no verified roster proving a four-year UE median. | Unproven |
| Projects per practitioner | No defensible evidence that every hands-on UE team member has four completed Unreal projects. | Gap |
| Public portfolio | A public ARA announcement creates a case-study anchor, but Epic will likely expect several polished UE case studies and a reel. | Gap |
| Client satisfaction | Positive client feedback and follow-on interest are strong reference signals. | Strong |
| Tools / reusable IP | State machines, communication pipelines, APIs, XR interaction architecture, device simulation patterns, and production QA. | Strong, package it |
The important distinction
Multiple modules inside one subcontract demonstrate complexity and scale. They should not be represented as four separate Unreal projects unless Epic explicitly agrees. Padding the count would damage credibility during technical vetting.
Unreal demand is appearing across the pipeline
Defense and CBRN
Proposal history repeatedly connects Unreal to high-fidelity mixed-reality training, digital twins, LiDAR/geospatial inputs, immersive scenarios, C++/Blueprint ports, and interoperability with customer platforms. The ARA work converted this from pipeline interest into production delivery.
Industrial and enterprise training
Other proposals considered Unreal for steel-mill safety, cyber training, real-time location-linked experiences, and immersive equipment simulation. These are opportunities, not completed Unreal references, and should stay out of the qualification count until delivered.
Team capability
Internal records show C++ engine development, Unreal Engine 4/5 exposure, real-time rendering, simulation architecture, physics, optimization, XR interaction, and technical art. A formal practitioner matrix is still required to prove Epic’s exact experience thresholds.
Strategic pull
Unity licensing friction has made Unreal a real contingency for new programs. That increases the value of an Epic relationship, but the Service Partner pitch should lead with customer outcomes and Unreal depth, not dissatisfaction with Unity.
Who ForgeFX should approach
Start with simulation-specific technical and business contacts. Do not cold-submit a generic form; there is no open application. Ask for a candid qualification review and the milestones needed to earn an invitation.
Nikola Jancovicova
Best-fit business-side entry point. Public bio: Epic Games focus on Unreal Engine for simulation, real-world 3D pipelines, intelligent digital twins, LiDAR, SLAM, and photogrammetry. ForgeFX’s simulation and device-digital-twin work maps directly.
Alban Bergeret
Best technical sponsor. Epic Developer Community lists him as Unreal Engine Solution Architect Director with 22+ years in simulation, from C++ development through architecture, digital twins, military training simulators, geospatial visualization, and XR.
Mark Collins
Likely defense/simulation relationship lane based on public industry presence. Verify current title and contact route before outreach; use him as a secondary path, not the only bet.
Existing Epic commercial/support relationship
Internal Slack says Dave previously worked with someone at Epic and would identify the person. The Outlook audit found Epic organization setup, licensing receipts, and automated support messages, but no named individual relationship in the accessible mailboxes searched. Recover Dave’s contact before describing ForgeFX as already connected.
Official Service Partner route
Once a named Epic contact validates readiness, use [email protected] as the formal routing address referenced by Epic’s own FAQ.
Earn the invitation in four moves
Ask for a qualification conversation
Send a concise ForgeFX capability note to Nikola and Alban: 25 years of simulation, completed Unreal mixed-reality delivery, C++/Blueprint integration, client satisfaction, and a request for an honest gap review. The ask is not “accept our application”; it is “tell us what evidence would make ForgeFX invitation-ready.”
Build the evidence packet
Create a verified UE practitioner matrix: employment status, years of Unreal experience, four project references per hands-on person, exact responsibilities, customer reference availability, and public/private status. Epic’s employee wording matters; contractor-heavy staffing may need explicit clarification.
Turn production work into a portfolio
Publish a sanitized ARA case study, an Unreal capability reel, and two technical artifacts: one showing the device-simulation architecture and one showing the integration/tooling pipeline. Add at least two more completed Unreal customer projects or genuinely independent internal reference projects with production rigor.
Request the invitation
Return to the Epic sponsor with the completed matrix, portfolio, client references, commercial pipeline, and proof of recurring UE demand. Target an in-person review around I/ITSEC or Unreal Fest, where Epic’s simulation team already convenes.
The one-sentence positioning
ForgeFX is the specialist Unreal simulation partner for high-consequence training systems where digital twins, real equipment behavior, XR interaction, integration, and measurable learning outcomes matter more than entertainment spectacle.
What not to say
Do not present ForgeFX as a broad Unreal studio, count modules as separate projects without Epic’s agreement, claim an established Epic relationship before recovering the named contact, or lead with Unity licensing frustration. The strongest narrative is specialized simulation expertise becoming proven Unreal delivery capability.
What “partner-ready” looks like
CORYS is a useful benchmark
Epic’s public CORYS relationship shows the pattern: a multi-year Unreal transition, dedicated R&D capacity, proprietary production tools and pipelines, a commercial deployment, Epic technical sponsorship, conference visibility, and a clear simulation specialization. ForgeFX does not need CORYS’s scale, but it does need the same density of verifiable Unreal proof.
ForgeFX’s differentiation
ForgeFX can own a narrower lane: high-consequence procedural training, interactive equipment and instrument digital twins, mixed reality, defense/industrial workflows, and full custom delivery from instructional design through deployment. That is distinct from general visualization, film, or games service shops.
Sources and confidence
External sources
- Epic Games — Unreal Engine Service Partner Program: official qualifications, invitation-only process, vetting, scope, and formal contact route. FAQ content was verified from the page’s structured data.
- Unreal Engine Service Partner Directory: active ecosystem categories and 136 listed providers at time of review.
- Laval Virtual — Nikola Jancovicova: current public simulation focus.
- Epic Developer Community — Alban Bergeret: Epic title, simulation background, projects, and technical focus.
- Epic Games at I/ITSEC: simulation team presence, co-simulation, interoperability, AI/XR training, mixed-reality simulation, and partner presentations.
- CORYS × Epic Games case study: relationship and portfolio benchmark.
Internal sources reviewed
- ForgeFX proposal and sales Slack channels containing Unreal project discussions, technical feasibility, SOW development, staffing, and delivery planning.
- ForgeFX production and general Slack evidence covering team onboarding, delivery challenges, client satisfaction, final delivery timing, and follow-on demand.
- The final full-scope Unreal port SOW from ForgeFX SharePoint, used to verify architecture and delivery scope. Commercial figures and sensitive program details were intentionally omitted here.
- Outlook searches across accessible ForgeFX leadership, operations, and production mailboxes for Epic Games, Unreal Engine, service partner terms, and named contacts.
Email finding: automated Epic correspondence was present, including organization setup and licensing transactions. No defensible named Epic relationship or direct person-to-person thread was found in the mailboxes searched.