Breaking Change

Name: Breaking Change
Brand: Breaking Change

AI Native

Breaking Change is a gameplay system-authoring platform that generates simulation-driven systems, supports in-game testing and runtime modification, and exports native code for incremental engine integration.

Est 2025

LinkedIn 218|Website|FTEs 6|HQ Cardiff, Wales, GB

Published Sep 2, 2026

01Common complaints

- If mature, widely-reviewed tooling is required immediately - Breaking Change has limited public customer references and no accessible review-platform footprint; established engine-native tooling or mature middleware may present lower operational risk. - If a studio cannot tolerate integration risk - For late-stage productions, introducing a new systemic runtime/authoring layer can threaten schedule stability. - If the project is not systems-heavy - Narrative-focused games or simpler mechanics may not realize sufficient benefit to justify the workflow shift. - If a formal security/compliance posture is required immediately - Security certifications and enterprise security features are not publicly documented; regulated buyers may prefer vendors with published SOC 2/ISO documentation. - If true engine-agnostic behavior is an absolute requirement - Claims of engine agnosticism should be validated in a POC across the actual engine version(s) and platform targets used by the project. - Current limitations acknowledged by the vendor - The site indicates additional workflow footage and details "will follow," implying incomplete public documentation. - Stated future scope includes progression, economies, crafting, and other systems, but details and delivery timelines are not provided. - Likely limitations (not confirmed publicly) - Documentation depth and support bandwidth may be constrained by a small team size. - Feature completeness for non-physical systems (economy/progression) appears limited or not yet shipped. - Roadmap items (as stated) - Additional detail for progression/economies/crafting is listed as forthcoming (no dates stated).

Deal disqualifiers

Buyers that require published enterprise compliance at contract signing (e.g., SOC 2/ISO)
Projects that cannot tolerate platform or toolchain churn during multi-year production
Projects whose core gameplay is primarily content/quest/dialog-driven rather than systemic simulation

02Why they buy

- Claimed differentiators (vendor statements; limited independent validation) - Vendor messaging emphasizes simulation-first system authoring as an alternative to script-heavy approaches. - The product is described as providing structured, visual, inspectable system representations. - Runtime modification of systems is presented as an authoring workflow capability. - Incremental integration is described (integrate one system at a time) with exported native code as a delivery option. - What is not yet validated publicly - Whether teams measurably reduce engineering time or improve maintainability versus conventional approaches. - Whether the runtime behaves deterministically and efficiently in multiplayer at scale. - Whether the authoring UX is usable for non-engineer roles (technical designers) without substantial engineering support. - Areas where competitors have advantages - Havok: Long history in production and a mature brand for physics middleware. - Engine-native approaches: Deep integration with engine editors, asset pipelines, and debugging tools.

03Field reports

Availability of third-party reviews

- Gartner Peer Insights - No Breaking Change product listing or reviews were found via accessible search results. - G2 - No Breaking Change product listing or reviews were found in accessible search results. - TrustRadius - No Breaking Change product listing or reviews were found in accessible search results. - Capterra - No listing or reviews were found in accessible search results.

Community/Social proof

Reddit
- No clear, product-specific Reddit threads surfaced in accessible searches for the vendor's site; many "breaking change" results are generic software-versioning discussions.
Hacker News
- Searches for "Breaking Change" on Hacker News return generic "breaking change" discussions unrelated to the vendor/product.

Vendor-published material and references

The website emphasizes pilots and hiring but does not prominently display named customer logos, case studies, or independently verifiable outcome metrics on the main page.

What this means

The lack of review-platform presence and public customer references is consistent with an early-stage product in pilot onboarding.
Evaluators should treat marketing claims as directional and perform technical diligence (POC, reference calls, integration spike).

Direct quotes (limited to publicly accessible relevant sources)

Vendor product description (not a customer review, but representative of claimed workflow)
- "Describe a system, generate it, test it in game, and modify it at runtime." (vendor product description)
Vendor differentiation claim
- "Instead of scripts, triggers, edge cases, and approximations, we simulate everything." (vendor differentiation claim)

Case Studies

- Public case studies - None were found on the vendor's public site or in readily accessible sources. - Funding announcement as verification (not a case study) - Third-party business press coverage provides external confirmation of funding components, but does not validate product outcomes or customer ROI. - Recommended requests during evaluation - Reference calls from pilot studios (even anonymized) - A before/after engineering-effort comparison with methodology - A demo project repository (or sample integration) demonstrating: - Runtime editing - Network behavior - Performance characteristics - Exported native code quality

04Best fit

Company sizes

Likely best fit:
- Indie to mid-sized studios with dedicated engineering capacity (small-to-mid sized engineering teams) building systems-heavy gameplay.
- Larger studios may be interested, but enterprise security/compliance requirements and longer procurement cycles can be barriers unless the vendor can provide enterprise assurances.

Industries and verticals

Game development studios building:
- Vehicles, weapons, mechs
- Simulation-heavy worlds
- Systemic sandbox gameplay

Roles and personas

Decision makers
- CTO / Technical Director
- Lead Gameplay Engineer / Systems Engineer
- Production leadership (when tooling impacts schedule risk)
End users
- Gameplay/systems engineers
- Technical designers
- QA (simulation-heavy systems can create complex state spaces)

Pain points the product addresses (based on vendor messaging)

High custom scripting and edge-case handling for complex systems
Long iteration cycles for tuning game feel across arcade-to-simulation spectra
Maintainability challenges across the lifecycle of a live game

Qualification criteria (what makes a strong fit)

Projects that have repeated patterns of complex systems where authoring efficiencies can be amortized
Projects able to allocate engineering time to integrate and validate runtime simulation behavior
Projects that prioritize runtime modification and inspection/debugging as part of the development workflow

05The pitch

What the product does (core value proposition in objective terms)

- Breaking Change is presented as a gameplay system-authoring product focused on building complex, simulation-driven gameplay systems (e.g., vehicles, weapons, mechs, facilities/infrastructure) with an approach intended to reduce reliance on scripting-heavy workflows. - The core workflow described by the vendor is: - Describe a system - Generate it - Test it in-game - Modify it at runtime - The vendor's stated approach is to "simulate everything" (described as an alternative to scripts, triggers, edge cases, and approximations). This functions as a positioning statement rather than an independently validated industry standard; independent validation is limited in publicly accessible sources.

Target market and market positioning

- Primary target appears to be game studios building systems-heavy gameplay (physics-driven or systemic interactions) across indie, AA, and AAA segments. - The vendor describes an authoring tool plus simulation runtime that it presents as "multiplayer-ready" and "engine agnostic," and that supports incremental integration with exported native code. These claims align with a B2B tooling platform rather than a consumer game product; they require technical validation during evaluation.

Get a comprehensive analysis of Breaking Change including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →