New York’s RAISE Act Portal Is Live: What Frontier AI Labs Must File by January 1, 2027

Starting January 1, 2027, a large frontier AI developer may not develop, deploy or operate a frontier model in New York State without a current disclosure statement on file under the state’s RAISE Act. The state opened its registration portal on November 10, and developers must register by that January 1 date.

Who Counts as a Large Frontier Developer

The act, formally the Responsible AI Safety and Education Act, uses two tests. A frontier developer is a person or company that has trained, or begun training, a foundation model using more than 10^26 integer or floating-point operations of computing power. That total includes later fine-tuning and reinforcement learning as well as the original training run. A large frontier developer is a frontier developer that, together with its affiliates, had annual gross revenues above $500 million in the preceding calendar year.

The $500 million line only marks the top tier. Every frontier developer must report critical safety incidents and publish a transparency report for each new or substantially modified frontier model, and large developers carry extra duties on top. DIGIT, the Office of Digital Innovation, Governance, Integrity and Trust inside the New York State Department of Financial Services (DFS), runs the program. It urges smaller frontier developers to open a portal account early so they can file an incident report quickly.

The state’s announcement names no companies. TechCrunch reported that large frontier developers such as OpenAI and Anthropic must register.

How Registration Works

Registration starts with a free NY.gov ID account, which unlocks the RAISE Portal. A large developer first certifies that the person filing can act for the company, supplying the entity’s legal name, country and street address plus the filer’s name, job title and contact details. DIGIT can ask for clarification before it approves the account.

Approval opens the disclosure statement itself. It asks for the principal place of business, any New York offices, primary, secondary and tertiary contacts, and beneficial ownership information where the law requires it. Under the statute, privately or closely held developers must list everyone who beneficially owns 5 percent or more of the company, along with anyone who held a stake that size in the company or its predecessors in the preceding five years. Developers must renew the statement every two years, after a transfer of model ownership, or after a material change to what they reported, whichever comes first.

Registration also costs money. The statute has DFS assess large developers in pro rata shares to cover the program’s operating expenses. DIGIT’s guidance page says developers must pay applicable assessments but gives no amount or schedule.

What the Act Requires After January 1

Once the act takes effect, it sets four recurring duties: two for every frontier developer and two for large developers only.

  • Incident reports (all frontier developers): Report a critical safety incident to DIGIT within 72 hours of determining that one occurred, or of learning facts that give a reasonable belief that one did. If an incident poses an imminent risk of death or serious physical injury, the developer must also tell an appropriate law enforcement or public safety agency within 24 hours.
  • Transparency reports (all frontier developers): Publish a report on the developer’s website before or when it deploys a new or substantially modified frontier model. It covers contact details, release date, supported languages and output types, intended uses, and restrictions on use. Large developers must add summaries of their catastrophic risk assessments, the results, and how far third-party evaluators took part.
  • Safety frameworks (large developers only): Publish a framework that describes how the developer defines, assesses and mitigates catastrophic risk, responds to incidents, secures unreleased model weights and governs its own implementation. Review it at least once a year.
  • Quarterly summaries (large developers only): Send DIGIT a summary of the developer’s assessment of catastrophic risk from internal use of its frontier models. DIGIT’s guidance sets the deadline at 30 days after each calendar quarter ends.

The trigger for an incident report is specific. The statute counts four events as critical safety incidents: unauthorized access to model weights that results in death or bodily injury, harm from a catastrophic risk materializing, loss of control of a frontier model that causes death or bodily injury, and a model using deceptive techniques against its developer to subvert controls in a way that shows materially increased catastrophic risk, outside an evaluation designed to elicit that behavior. Catastrophic risk, subject to statutory exclusions, means a foreseeable and material risk that a frontier model will materially contribute to the death of or serious injury to more than 50 people, or to more than $1 billion in property damage, in a single incident.

Penalties and Enforcement

The New York attorney general enforces the act in court. Against a large frontier developer that fails to publish or transmit a required document, fails to report an incident, or makes a materially false or misleading statement about catastrophic risk or its compliance with its framework, the attorney general can seek civil penalties of up to $1 million for a first violation and up to $3 million for each later one. A good-faith statement that was reasonable under the circumstances is not a violation. The act creates no private right of action.

Failing to follow a framework the developer itself published is also a listed violation, so a published framework binds the company that wrote it. Separately, DFS can fine a developer $1,000 per day for failing to file a disclosure statement or keep it current, after notice and a hearing.

Lawmakers originally passed higher penalties: up to $10 million for a first violation and $30 million for later ones. Governor Kathy Hochul secured the current figures through a chapter amendment she signed on March 27, 2026. TechCrunch reported that the state can take enforcement action against companies that fail to register, and that a state spokesperson declined to give specifics.

What It Means for Companies That Buy From These Labs

The act places its duties on developers, and the statute imposes none on the businesses that buy or deploy their models. What those businesses gain is visibility, with limits. Frameworks and transparency reports go on developers’ public websites. Individual incident reports stay out of public view: the statute exempts them from public disclosure. Starting January 1, 2028, DFS must send the governor and legislative leaders an annual report built from anonymized, aggregated incident data. Members of the public will also be able to report suspected critical safety incidents through the RAISE Portal.

My take: the published framework is the document worth asking vendors about, because the attorney general can penalize a large developer that does not follow it. Procurement and risk teams can request the current framework and the latest transparency report during vendor review. They can also note that New York’s 72-hour incident window is shorter than the 15 days that California’s SB 53, in effect since January 2026, allows.

The executive order that US President Donald Trump signed in December 2025 directed the US Department of Justice to set up a task force to challenge state AI laws, but the order does not itself override them. Hochul framed the November 10 launch as New York acting while the federal government does not.

The first real test arrives in January, when large developers must publish their frameworks and the New York Center for AI Responsibility and Research at Binghamton University is set to review them alongside DIGIT. Two administrative questions stay open until then: DIGIT has published no assessment amount, and the state has not said how it will enforce the registration deadline.

The post New York’s RAISE Act Portal Is Live: What Frontier AI Labs Must File by January 1, 2027 appeared first on DataFLOQ.

Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe to our Newsletter