New York RAISE Act (Responsible AI Safety and Education Act)
Compliance reference — obligations, penalties, applicability, and primary sources. For the full statutory picture in this jurisdiction, see New York AI laws.
Last verified October 12, 2026
Summary
New York's Responsible AI Safety and Education (RAISE) Act takes effect January 1, 2027. Codified as General Business Law Article 44-B (Sections 1420–1429), it requires developers of frontier AI models — foundation models trained with more than 10^26 operations — to publish transparency reports and report critical safety incidents within 72 hours, and requires large frontier developers (over $500 million in annual revenue with affiliates) to publish a frontier AI framework, file a disclosure statement with a new office in the Department of Financial Services, and pay assessments. The Attorney General may seek civil penalties of up to $1 million for a first violation and $3 million for each subsequent violation.
The RAISE Act was enacted in two steps. Governor Hochul signed S6953-B/A6453-B on December 19, 2025 as Chapter 699 of the Laws of 2025, with agreed chapter amendments. Those amendments passed as S8828/A9449 (Gounardes) and were signed on March 27, 2026 as Chapter 96 of the Laws of 2026. The sponsor's memo describes the bill as "a chapter amendment to L.2025, c.699, to repeal the underlying chapter and establish a new regulatory regime": Chapter 96 repeals the Article 44-B text that Chapter 699 added and replaces it, and changes Chapter 699's effective date from the ninetieth day after enactment to January 1, 2027. The 2025 bill's compute-cost thresholds and penalty formula therefore never take effect. [Sources: S8828 text and history, S6953-B history, Governor's December 19, 2025 release, retrieved 2026-10-12.]
The replacement Article closely tracks California's SB 53 (TFAIA): the same 10^26-operation frontier-model definition, the same $500 million large-frontier-developer revenue test, and parallel framework, transparency-report and incident-reporting duties. The differences are the New York oversight office, the disclosure-statement and assessment regime, and higher maximum penalties.
Compliance timeline
| Date | Event | Status |
|---|---|---|
| DateDecember 19, 2025 | EventS6953-B signed as Chapter 699 of the Laws of 2025 | StatusComplete |
| DateMarch 27, 2026 | EventChapter amendment S8828 signed as Chapter 96; Article 44-B replaced; effective date set to January 1, 2027 | StatusComplete |
| DateSeptember 21, 2026 | EventGovernor announces the Office of Digital Innovation, Governance, Integrity and Trust (DIGIT) within DFS and says large frontier developers will be directed to register starting in November 2026 | StatusAnnounced |
| DateJanuary 1, 2027 | EventArticle 44-B takes effect | StatusScheduled |
| DateJanuary 1, 2028 | EventFirst annual report by the office on critical safety incidents | StatusScheduled |
Who is covered
- Frontier model — a foundation model trained using more than 10^26 integer or floating-point operations, counting the original training run and any later fine-tuning, reinforcement learning, or other material modification (§ 1420(9)).
- Frontier developer — a person who has trained, or initiated the training of, a frontier model (§ 1420(8)).
- Large frontier developer — a frontier developer that, together with its affiliates, had annual gross revenues above $500,000,000 in the preceding calendar year (§ 1420(10)).
The Article applies to frontier models developed, deployed, or operating in whole or in part in New York (§ 1425). Accredited New York colleges and universities doing academic AI research, and the Empire AI consortium, are excepted (§ 1426).
Developer duties
| Section | Duty | Who |
|---|---|---|
| Section§ 1421(1) | DutyWrite, implement, comply with, and publish a frontier AI framework covering standards, catastrophic-risk thresholds and assessments, mitigations, deployment review, third-party assessment, framework updates, cybersecurity for unreleased model weights, critical-incident response, internal governance, and internal-use risk | WhoLarge frontier developers |
| Section§ 1421(2) | DutyReview the framework at least once a year; publish a material modification and its justification within 30 days | WhoLarge frontier developers |
| Section§ 1421(3) | DutyBefore or with each new or substantially modified frontier model deployment, publish a transparency report (website, contact mechanism, release date, languages, output modalities, intended uses, use restrictions); large developers add summaries of catastrophic-risk assessments, results, and third-party involvement. A system card or model card can satisfy this | WhoAll frontier developers |
| Section§ 1421(4) | DutyNo materially false or misleading statements about catastrophic risk or framework compliance | WhoAll frontier developers |
| Section§ 1422(2) | DutySend the office a summary of any assessment of catastrophic risk from internal use every three months, or on another agreed schedule | WhoLarge frontier developers |
| Section§ 1422(3) | DutyReport a critical safety incident to the office within 72 hours; disclose within 24 hours to an appropriate law-enforcement or public-safety authority if there is an imminent risk of death or serious physical injury | WhoAll frontier developers |
| Section§ 1428 | DutyFile a disclosure statement with the office before developing, deploying, or operating a frontier model in New York, renew it every two years or on an ownership or material change, and pay a pro rata share of the office's operating expenses | WhoLarge frontier developers |
A catastrophic risk is 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 more than $1 billion in property damage, from a single incident in which the model provides expert-level help with a chemical, biological, radiological, or nuclear weapon, engages without meaningful human oversight in a cyberattack or conduct that would be murder, assault, extortion, or theft if done by a person, or evades its developer's or user's control (§ 1420(3)).
Oversight office and fees
The Article assigns implementation to an office within the Department of Financial Services that reports to the Superintendent (§ 1420(16)) and has rulemaking authority (§ 1429). On September 21, 2026 the Governor named it the Office of Digital Innovation, Governance, Integrity and Trust (DIGIT) and appointed Marc Gilman as Deputy Director for the RAISE Act. The office runs the incident-reporting mechanism, which members of the public may also use, and from January 1, 2028 publishes an annual report. Failing to file a disclosure statement, or leaving false information uncorrected, can bring a civil penalty of $1,000 for each day after notice and a hearing, plus the unpaid assessments (§ 1428).
Enforcement and penalties
The Attorney General may bring a civil action for a penalty of up to $1,000,000 for a first violation and up to $3,000,000 for each subsequent violation, scaled to severity, when a large frontier developer fails to publish or transmit a required document, makes a prohibited false or misleading statement, fails to report an incident, or fails to comply with its own frontier AI framework (§ 1427(1)). The Article expressly creates no private right of action (§ 1427(2)).
Frequently asked questions
When does the New York RAISE Act take effect?
January 1, 2027. Chapter 96 of the Laws of 2026 (S8828, signed March 27, 2026) changed the original Chapter 699 effective date, which would have been the ninetieth day after enactment, to January 1, 2027.
Who must comply with the RAISE Act?
Developers that have trained, or begun training, a foundation model with more than 10^26 operations carry the transparency-report and incident-reporting duties. Large frontier developers, those with more than $500 million in annual gross revenue including affiliates, also carry the frontier AI framework, quarterly internal-use reporting, and disclosure-statement duties.
How fast must a critical safety incident be reported under the RAISE Act?
Within 72 hours of determining that a critical safety incident occurred, or of learning facts sufficient to establish a reasonable belief that one occurred, to the DFS office. If the incident poses an imminent risk of death or serious physical injury, the developer must also disclose it within 24 hours to an appropriate law-enforcement or public-safety authority.
What are the penalties under the New York RAISE Act?
The Attorney General may seek up to $1 million for a first violation and up to $3 million for each subsequent violation. Separately, the DFS office may impose $1,000 per day for failing to file the required disclosure statement. There is no private right of action.
Key obligations
Specific compliance requirements derived from the primary source. Each item links to the relevant statutory section where applicable.
- GovernanceRole: developerN.Y. Gen. Bus. Law § 1421(1)–(2)
Large frontier developers must write, implement, comply with, and publish a frontier AI framework for managing catastrophic risk, review it at least annually, and publish material modifications with a justification within 30 days.
DeadlineFrom January 1, 2027
- TransparencyRole: developerN.Y. Gen. Bus. Law § 1421(3)
Before or when deploying a new or substantially modified frontier model, publish a transparency report; large frontier developers include summaries of catastrophic-risk assessments, their results, and third-party evaluator involvement.
DeadlineBefore deployment
- DocumentationRole: developerN.Y. Gen. Bus. Law § 1422(3)
Report a critical safety incident to the Department of Financial Services office within 72 hours, and within 24 hours to an appropriate law-enforcement or public-safety authority when there is an imminent risk of death or serious physical injury.
DeadlineWithin statutory timeframe
- DocumentationRole: developerN.Y. Gen. Bus. Law § 1422(2)
Large frontier developers must transmit to the office a summary of any assessment of catastrophic risk from internal use of their frontier models every three months or on another agreed schedule.
DeadlineFrom January 1, 2027
- GovernanceRole: developerN.Y. Gen. Bus. Law § 1428
Large frontier developers must file a disclosure statement with the office before developing, deploying, or operating a frontier model in New York, renew it every two years or on an ownership or material change, and pay a pro rata assessment.
DeadlineFrom January 1, 2027
Build a compliance program around these obligations
A single law is one input to a broader program. These guides show how to assign accountability, map every obligation to a control, and split developer-versus-deployer duties across the systems a team operates.
- AI governance: building an AI compliance program
The operating model — owners, committee, decision rights, lifecycle gates — that turns a law into an accountable, auditable program anchored to the NIST AI RMF GOVERN function.
- AI compliance framework: the regulatory control map
How to map each AI system to the laws it triggers, the controls that satisfy them, and the evidence that proves the controls operate.
- Deployer vs developer obligations
Which duties attach to building an AI system versus putting one into use — the split most state AI laws turn on.
Sources
Every fact above is sourced from the official primary source. Independent verification recommended before acting on the information.
- Officialwww.nysenate.gov — N.Y. Gen. Bus. Law §§ 1420–1429 (Art. 44-B), L. 2025, ch. 699, as replaced by L. 2026, ch. 96
- www.nysenate.gov
- www.nysenate.gov
- www.nysenate.gov
- www.governor.ny.gov
- www.governor.ny.gov
Last reviewed October 12, 2026. Reviewed by the AI Compliance Atlas editorial process against primary sources. Source selection, retrieval dates, and update rules are documented in the Atlas methodology.
We may receive referral commissions from recommended compliance tools. Recommendations are based on product fit and not on commission size. Links marked “partner link” include a tracked redirect.