Two Giants, One Chokehold: How Synopsys and ANSYS Tried to Corner the Future of Tech

What These Companies Actually Do, And Why You Should Be Terrified

If you have ever used a smartphone, driven a car with a chip in it, or relied on any electronic device made in the last two decades, you have used products designed with tools made by either Synopsys or ANSYS. Synopsys makes the electronic design automation software — the digital workbench — that engineers use to design semiconductor chips. ANSYS makes simulation software that lets engineers model how physical objects behave under stress, heat, light, and electricity before a single prototype is ever built.

These are infrastructure-level tools. Engineers at aerospace companies, chip fabs, defense contractors, and medical device makers do not just prefer this software; they depend on it the way a city depends on water pipes. The market for these tools is not a consumer app store where someone can just switch to a competitor overnight. The learning curves are steep, the integrations are deep, and the customer lock-in is severe.

On January 15, 2024, Synopsys and ANSYS signed an Agreement and Plan of Merger. The deal would have created a single company controlling dominant positions across multiple categories of engineering software simultaneously. The FTC looked at that combination and concluded it had reason to believe it would violate federal antitrust law.

The Two Markets They Wanted to Lock Down

The FTC’s concern zeroed in on two specific product categories. The first: Optics and Photonics Design Products, which are the specialized tools engineers use to design and simulate optical systems, from laser components to complex photonic devices. The second: RTL PCA (Register Transfer Level Power Consumption Analysis), which is the software engineers use to analyze how much power a chip design will consume before it is manufactured. Both of these are high-stakes, narrow-market tools where losing a competitor is not a nuisance; it is a market failure.

Synopsys owned the Optics and Photonics suite. ANSYS owned PowerArtist, the RTL PCA tool. A merged company would have held both, serving the same engineering customers across complementary workflows, with fewer competitive alternatives than before. The FTC decided that was unacceptable without surgical removal of the overlapping assets.

The Non-Financial Ledger: What the Numbers Miss

The Engineers Who Became Bargaining Chips

The Consent Order dedicates an entire section to employees — the actual human beings who built the Optics and Photonics software and the PowerArtist tools. These workers, the document calls them “Relevant Employees,” were defined as any full-time, part-time, or contract worker at either business as of specific dates in 2024. Their job titles, salary figures, performance reviews for the past three years, bonus histories, and benefit details were all packaged into “Employee Information” to be handed over to Keysight within 10 days of a request.

Think about what that means for a working engineer. You spend years building expertise on a specialized product, cultivating institutional knowledge, and establishing yourself within a company culture. Then, one day, your entire employment history gets bundled into a corporate transfer document and handed to a new employer you never agreed to work for, as part of a federal antitrust remedy. The Order does protect workers from having noncompete clauses enforced against them by the new entity, but the workers had no seat at the table when any of this was negotiated.

Synopsys is barred from poaching those workers back for three years, and it is barred from making counteroffers when Keysight approaches them. But the Order also makes clear: Synopsys is under no obligation to tell employees any of this proactively, and nothing in the Order prevents Synopsys from continuing to employ anyone who simply does not get approached. The workers’ futures were decided by lawyers and regulators, in rooms the workers never entered.

The Customers Caught in the Middle

The Order also reveals the existence of “Shared Contracts,” which are agreements that cover products in both the divested businesses and the parts of the company that Synopsys gets to keep. These contracts cover real customers, real companies that signed deals for bundled services spanning multiple product lines. The full list of those customers is redacted from the public record, hidden in Nonpublic Appendices F and G.

Those customers were sent written notifications informing them their contracts were being transferred and that they could terminate the relevant portion at no cost. The Order gives customers the legal right to walk away. But the reality of enterprise software contracts is that walking away from a tool that is embedded in your engineering workflow is enormously disruptive. The “right to terminate” is, for many companies, a theoretical right that costs far more in operational disruption than it saves in contract fees.

Meanwhile, the financial details of what Synopsys is paying Keysight to compensate for the period before each customer formally transfers to Keysight, laid out in Nonpublic Appendix H, are completely hidden. The public, including those affected customers, cannot see whether the compensation arrangement adequately protects Keysight’s ability to serve them during the transition. The FTC knows. The corporations know. Everyone else is excluded.

The Software Products That Carry Names, History, and Teams

The Optics and Photonics Business being handed to Keysight includes products with real engineering legacies: Code V, a decades-old optical design program with a global user base; LightTools, an illumination engineering software suite; RSoft, a photonics design toolkit; and LucidShape, used in automotive lighting design, among others. These are not generic code modules. They each have communities of engineers who have built careers around them, who have written documentation, trained on them, and integrated them into multi-year product development pipelines.

The RTL PCA side carries the PowerArtist name, a tool that chip designers use to analyze power consumption at the design stage, before a chip is ever physically produced. Power consumption in chips is a matter of global consequence. It affects the energy draw of data centers, the battery life of devices, the thermal limits of AI accelerators. Engineers who depend on PowerArtist are not just running software; they are making decisions that cascade into the physical world. The Order mandates that Synopsys hand over not just the product but a specific code set, the “Identified Timing Aware Ansys IP,” within 60 days of the divestiture date, to ensure the tool continues to function in Keysight’s hands.

Legal Receipts: What the FTC Actually Put in Writing

Societal Impact Mapping: Who Gets Hurt When Tech Monopolies Merge

The “Cost of a Life” Metric: What This Deal Costs in Human Terms

The critical number buried in this document is not a dollar amount at all. The Order requires Synopsys to divest, “absolutely and in good faith,” at “no minimum price.” That phrase, “no minimum price,” is regulatory-speak for: if no buyer showed up willing to pay full value, Synopsys would still be forced to sell. The FTC prioritized competitive structure over corporate profit. That is how rare this kind of intervention actually is, and how significant it is when it happens.

The Fine Print That Protects Synopsys More Than You

The Redaction Wall: Eight Hidden Appendices

The public version of this Consent Order references eight separate nonpublic appendices, each containing critical details about exactly what was sold, to whom, for how much, and under what conditions. Nonpublic Appendix A holds the full Optics and Photonics divestiture agreement with Keysight. Nonpublic Appendix B holds the full RTL PCA divestiture agreement. Appendix C lists the assets Synopsys gets to keep. Appendix D names specific identified employees with restricted rights. Appendix E defines exact intellectual property being transferred. Appendices F and G list the specific customer contracts being reassigned. Appendix H details exactly how much Synopsys is paying Keysight during the customer transition period.

Every single one of these appendices is redacted from the public record. The FTC published them as incorporated by reference but withheld from disclosure. The public, the engineering customers affected by these transfers, the workers whose jobs were restructured, the smaller competitors in these markets, none of them can see the actual terms. The corporations know. The regulators know. The public is excluded from the details of a deal that restructures a market they depend on.

The Admit-Nothing Escape Hatch

The Consent Agreement includes explicit language stating the signing is “for settlement purposes only and does not constitute an admission by Respondents that the law has been violated.” This is standard in FTC consent decrees, but it is worth sitting with for a moment. The FTC determined it had reason to believe federal antitrust law was violated. The companies agreed to sell off two entire business units, submit to a decade of federal oversight, accept a compliance monitor, and file regular compliance reports. And officially, legally, nothing happened. Nobody broke any laws. This is the architecture of corporate accountability in America.

What Now: How to Push Back

The Watchlist: Who Is Supposed to Be Watching

• FTC Bureau of Competition (bccompliance@ftc.gov) — The office that negotiated this order and receives compliance reports. Contact them if you have evidence of violations.
• S&W Partners LLP — The appointed independent compliance Monitor. They are required to report to the FTC on Synopsys’s behavior and cannot be restricted from doing so.
• FTC Commissioners: Chairman Andrew N. Ferguson, Melissa Holyoak, Mark R. Meador — The three commissioners who approved this order. They can be held accountable for whether enforcement holds.
• DOJ Antitrust Division — A parallel enforcement body with overlapping jurisdiction over merger conduct. If FTC enforcement weakens, DOJ is the secondary lever.
• Congress — The FTC’s budget and authority are subject to Congressional oversight. Representatives on the Senate Commerce Committee and House Judiciary Committee have oversight over FTC activity.

What You Can Actually Do

If you work in engineering software, chip design, or photonics, document any anti-competitive behavior you observe after this merger closes: price increases, feature degradation in the divested products, attempts to steer customers away from Keysight’s versions of these tools, or any contact from Synopsys attempting to recruit employees protected by this order. The FTC has a public comment and reporting process, and evidence from people inside these markets is exactly what gives regulators grounds to act.

If you are part of an engineering school, university, or nonprofit research institution, pay attention to whether University/Educational Contracts, which the Order explicitly excludes from the standard customer transition process, are being honored or quietly rolled back. These institutions are the training ground for the next generation of engineers who will use these tools, and they have less bargaining power than corporate customers.

Support organizations working on tech monopoly accountability, including the American Economic Liberties Project, the Open Markets Institute, and your local mutual aid tech worker networks. Federal regulatory orders are only as strong as the political will to enforce them. Grassroots pressure on Congress and on FTC commissioners is how that will gets maintained. The corporations have lobbyists in every room where these decisions get made. The counterweight to that is organized people who refuse to look away.