Three independent cloud providers filed suit against the Commerce Department on November 21 over the remote-access rule published five days earlier, and their argument is narrower and stronger than the industry's public complaints have been. They are not saying the rule is bad policy. They are saying the department regulated a service and called it an export.

What the rule does

The interim final rule extends export controls from chips to remote access. An overseas data centre that provides more than 12 million aggregated TPP of compute to a firm headquartered in a D:5 country or Macao now needs a licence. It also repeals the 2025 AI Diffusion Rule and adds five countries to the licensing list.

The providers in the suit — CoreWeave, Lambda and Crusoe, all with substantial capacity outside the United States — argue three things. That the Export Control Reform Act authorises controls on the export of items, and a rental of compute is not an item. That the department used the interim-final-rule route to skip notice and comment, which requires a showing of good cause the filing says is absent. And that the 12-million-TPP threshold is not defined precisely enough to apply, since TPP depends on the precision at which a cluster is benchmarked.

Why the jurisdiction argument is the strong one

The other two claims are procedural and could be cured by a revised rule with a comment period. The jurisdiction claim cannot. If a court accepts that compute rental is a service rather than an export, the department's authority over the transaction collapses and it has to go to Congress.

The government's counter is that the statute covers technology, and that access to compute is functionally access to the technology. That is a plausible reading, and it is the same reading that has sustained controls on deemed exports of technical data for decades. The question is whether a court extends the analogy from data to machine time.

The commercial reality underneath

Whatever the court does, the contracts have already stalled. Three providers we spoke to describe the same pattern: foreign customers with signed letters of intent have paused, not because they were refused a licence but because nobody can tell them how long one takes. The rule sets no processing timeline, and the licensing office has published neither a form nor a fee.

That uncertainty is doing the work the rule was meant to do. A customer who cannot predict a six-month approval moves the workload, and the provider loses the contract either way.

What to do if you are exposed

Three practical steps, none of them legal advice. Audit your TPP calculation now and document the precision assumption you used — if the threshold is challenged, your number will be. Separate contracts so that compute and software licences are priced and delivered separately; if rental is reclassified, a bundled contract has to be renegotiated in full. And put a regulatory-change clause with a defined termination right into anything signed this quarter, because you have more leverage now than in February.

The timeline

No hearing has been scheduled. The rule remains in force while the case proceeds, which means the licensing regime is live and the compliance obligation is real even if the authority behind it is contested. Companies planning to wait for the outcome are planning to be non-compliant for at least a quarter.