A substantive expansion and clarification. V2 introduces a new definition for "biological data" and explicitly adds biotechnology as a key area of focus for the network's purposes and node designation. Crucially, v2 adds a new section authorizing $30 million annually for fiscal years 2026 through 2030 to fund the network's nodes, providing a clear financial framework.
National Programmable Cloud Laboratories Network Act of 2025
- Sponsor
- Sen. Fetterman, John [D-PA]
- Committees
- Commerce, Science, and Transportation Committee (primary)
- Last action
- Jul 13, 2026
Bottom line
The bill creates a federally funded network of advanced, remotely programmable laboratories to boost U.S. leadership in scientific research and manufacturing, with a focus on automation, AI, and private sector collaboration.
What it actually does
This bill establishes the National Programmable Cloud Laboratories Network, managed by the National Science Foundation (NSF), to foster advanced experimentation, biotechnology, and AI in scientific research. It authorizes the NSF Director to designate up to six nodes (physical laboratories) and provide grants for their operation, with an emphasis on collaboration, standardization, and long-term financial sustainability. The bill also mandates interagency collaboration with the National Institute of Standards and Technology (NIST) to develop network-wide interoperability and data-sharing standards.
Proponents argue
Supporters argue this bill is crucial for maintaining U.S. leadership in advanced experimentation, biotechnology, and artificial intelligence, which are vital for national security and economic competitiveness. They contend that the Network will reduce research costs through automation, accelerate the transfer of government-funded research to commercial applications, and improve collaboration among diverse research entities, while also supporting workforce development in critical technical fields.
Opponents contend
Critics might raise concerns about the scale of federal investment, arguing that the private sector should primarily drive such infrastructure development, or that a network of only six nodes might not be sufficiently broad to achieve the stated national goals. Some might also question the long-term sustainability of the nodes without continued federal funding, despite the bill's emphasis on self-sustainability plans.
The bill is relatively concise and structured logically, making it accessible for an informed reader to understand its core provisions and implications within a reasonable timeframe.
Section 3(b)
Establishment of the National Programmable Cloud Laboratories Network and Awards
This section directs the Director of the National Science Foundation (NSF), in consultation with the National Institute of Standards and Technology (NIST), to establish and oversee a network of not more than six 'programmable cloud laboratories' (nodes) within one year. The NSF Director is authorized to award grants of up to $5,000,000 per fiscal year for a period of up to five years to each designated node to support the Network's operations.
Supporters argue
Proponents argue that establishing a limited number of well-funded, high-capacity nodes will concentrate resources effectively, ensuring the network can achieve critical mass and deliver transformative results in advanced experimentation and AI-driven research. The grant structure provides stable, multi-year funding essential for developing and maintaining complex infrastructure.
Critics contend
Some might argue that limiting the network to 'not more than 6 nodes' could restrict geographic diversity or exclude many deserving institutions, potentially concentrating federal investment in a few already well-resourced areas. Concerns could also be raised about the long-term sustainability once the initial five-year grant period concludes.
Tradeoffs
The bill balances the desire for broad impact with the need for focused investment. Limiting the number of nodes aims to ensure quality and resource concentration, but risks limiting accessibility and diversity across the national research landscape. The five-year grant period provides initial stability but necessitates robust sustainability planning.
Section 3(d) and (e)
Application, Selection, and Evaluation Criteria for Nodes
This section outlines the process for eligible entities (institutions of higher education, non-profits, private-sector research entities, or consortia) to apply for node designation. Applications must include a technical plan, a long-term self-sustainability plan with metrics, and evidence of non-Federal cost share. The selection process will be competitive, merit-based, and transparent, evaluating factors like existing infrastructure, capacity for cloud-enabled workflows, sustainability likelihood, collaboration ability, research security protocols, and user interest.
Section 3(f)
Designation Preferences and Biotechnology Focus
When designating nodes, the NSF Director is directed to give preference to applicants demonstrating meaningful third-party cost share and pre-existing infrastructure. Additionally, to the extent practicable, at least one node must demonstrate the capability to support cloud-enabled biotechnology research, including automated experimentation or quality control workflows.
Section 3(g)
Responsibilities of Designated Nodes
Each designated node is tasked with supporting the Network's purposes, facilitating collaboration, and actively participating with NIST in developing network-wide interoperability, data-sharing, cybersecurity, and AI-assisted experimentation standards. Nodes must also provide secure digital infrastructure, engage in public-private partnerships for technology transfer, develop financial sustainability plans, establish performance metrics, and leverage commercially available hardware and software where practicable.
Section 4
Interagency Collaboration for Standards Development
Within 180 days after all nodes are designated, the Director of NIST, in cooperation with the NSF Director and participating entities, must develop and promulgate standards for interoperability across Network nodes. This includes standards for instrumentation, data infrastructure, communication protocols, and experiment execution systems. NIST is also tasked with establishing secure data-sharing protocols and defining minimum technical requirements for remote experimentation and AI-assisted workflows, with periodic updates in consultation with partners.
Section 7
Funding Allocation
This section allocates $30,000,000 annually to the National Science Foundation (NSF) for each of the fiscal years 2026 through 2030 to carry out the provisions of this Act. This funding is subject to the availability of appropriations.
The definition of 'artificial intelligence' is not provided directly within this bill but is instead referenced to section 5002 of the William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021 (15 U.S.C. 9401).
Section 2(1)
Why it matters:This is standard legislative practice to avoid redundancy and ensure consistency with existing legal definitions, especially for complex technical terms that have been thoroughly debated and defined elsewhere.
Case for: Referencing existing definitions streamlines legislative drafting and ensures legal consistency across different statutes, preventing conflicting interpretations of key terms.
Case against: For a casual reader, this requires an extra step to fully grasp the scope of 'artificial intelligence' as intended by the bill, potentially hindering immediate comprehension.
Estimated impact: Ensures that the application of AI in the Network aligns with a broad, established federal definition, impacting the types of technologies and research supported.
The Director shall award a grant to each node, in an amount not greater than $5,000,000 per fiscal year for a period of not more than 5 years, to support the National Programmable Cloud Laboratories Network.
Section 3(b)(1)(B)
Why it matters:This is standard legislative practice, detailing the specifics of grant awards within the authorizing language for the program itself. It's not evasive but requires careful reading.
Case for: Setting a clear per-node funding limit ensures fiscal discipline and allows the NSF to plan its budget effectively across the maximum number of nodes. The 5-year period provides stability for long-term planning.
Case against: Some might argue that a fixed cap of $5 million per year might not be sufficient for all types of highly complex or capital-intensive programmable cloud laboratories, potentially limiting the ambition or scope of certain nodes.
Estimated impact: This provision directly limits the financial support each node can receive, influencing the scale and ambition of the projects undertaken by the designated laboratories. It also sets the maximum number of nodes to six, given the total appropriation.
Each node selected by the Director shall develop and maintain a financial sustainability plan to reduce long-term reliance on Federal funds, including through user fees, licensing, consortia membership, or other revenue-generating models.
Section 3(g)(7)
Why it matters:This is a substantive programmatic requirement placed on grant recipients, and its placement within the 'Responsibilities' section is logical. It's not intended to be hidden but is a detail within a longer list.
Case for: This provision ensures that federal investment leads to self-sustaining research infrastructure, maximizing the long-term impact of taxpayer dollars and preventing perpetual reliance on federal grants. It encourages entrepreneurial approaches to research funding.
Case against: Some might argue that requiring nodes to become financially self-sufficient could shift their focus from fundamental research to revenue generation, potentially compromising academic freedom or prioritizing commercially viable projects over foundational science.
Estimated impact: This mandate fundamentally shapes the operational model and long-term viability of each node, pushing them towards diverse funding streams and market engagement.
The National Programmable Cloud Laboratories Network, including all authorities, programs, and funding provided under this Act, shall terminate on September 30, 2031.
Section 78
Why it matters:Sunset clauses are often placed at the end of bills. While not inherently evasive, their placement can make them less prominent than other provisions. It ensures a re-evaluation of the program's effectiveness before potential reauthorization.
Case for: A sunset clause ensures that the program undergoes a rigorous review after a defined period, allowing Congress to assess its effectiveness, efficiency, and continued relevance before deciding on reauthorization. This promotes accountability and prevents programs from continuing indefinitely without scrutiny.
Case against: Critics might argue that a sunset clause creates uncertainty for long-term planning and investment, potentially discouraging private sector partners or making it harder for nodes to secure long-term commitments if the program's future is not guaranteed beyond 2031.
Estimated impact: This provision sets a hard expiration date for the entire program, including its funding and authorities, after five fiscal years of operation (FY2026-2030 funding, sunset Sept 30, 2031).