Skip to main content
Everything PR News
Research

AI Launch Availability: 16 of 30 Access Promises Verified

EPEPR Research13 min read
Share
AI Launch Dates Tested: 16 of 30 Promises Corroborated

Everything-PR followed 30 AI product announcements made between April 1 and June 30, 2025, and checked dated records for 90 days after each one. A separate dated record supported the tracked access promise in 16 of 30 cases. One release was late and one target was later revised. The other 12 had limited evidence, an unverified start date, or no deadline that could be assessed within 90 days.

Updated November 21, 2026. Based on 30 announcements dated April 1 to June 30, 2025, each followed for 90 days.

Download the 30-case evidence workbook (XLSX)

What did the 30 AI launches promise, and what happened?

Sixteen of the 30 announcements (53%) had a separate dated record supporting the access that the vendor promised at launch. The sample covered eight enterprise AI, eight developer tool, seven cybersecurity and seven marketing software milestones.

Google said in May 2025 that an updated Gemini 2.5 Flash would reach production in early June. Developers could try the preview immediately, and Google's developer and Vertex AI records date production availability to June 17. Both statements are true: buyers had a model to use at launch, and the production date came after the stated window.

What the evidence establishedAnnouncements
Tracked commitment corroborated by a separate dated record16
Late release within 90 days1
Timetable revised, documented after day 901
Live access reported in the launch record alone5
Access documented by day 90, original start unverified3
Insufficient historical evidence1
No testable timetable2
Promised window outside the 90 days1
Total30

Corroborated means the study found a second, dated record that matches what was promised. It does not mean every account, region or plan had access. Several of the 16 were scored on a narrow commitment, such as the first stage of a rollout or a single documented waitlist invitation.

Which AI launches arrived late or changed within 90 days?

Five of 30 cases (17%) had a documented change in release timing, eligibility, pricing structure or access conditions inside the 90-day window. Gemini 2.5 Flash was the one late release, and four others widened or reshaped access.

  • OpenAI confirmed Codex access for ChatGPT Plus users in a June 3, 2025 update. The May 16 launch had started with Pro, Enterprise and Team plans and described Plus and Edu as coming soon.
  • GitHub opened the Copilot coding agent preview to Copilot Business customers in a June 19, 2025 changelog entry, after the May 19 preview for Pro+ and Enterprise.
  • Google's Jules left its free public beta on August 6, 2025 with a free tier and paid plan limits, as its changelog records. That was day 78 of 90.
  • Cursor widened Background Agent access in version 1.0, with Privacy Mode disabled as the condition for immediate access, per its 1.0 changelog.
  • Google's Gemini 2.5 Flash reached production on June 17, 2025, seven days after the early June window the study coded as June 1 to 10.

Two of the four access changes, Codex and Jules, were signaled at launch, so they widened access without breaking a promise. Salesforce is a sixth case if later evidence is counted. Its Agent Health Monitoring was announced on June 23, 2025 in pilot or beta with general availability planned for August. The reviewed records showed no general availability by day 90 on September 21, and a November 20, 2025 Salesforce update moved general availability to spring 2026. That update is shown as a revised target because it was published 150 days after the announcement.

What counts as kept when an AI vendor promises a rollout start?

A promise to start a rollout is kept when access begins for any eligible customers in the stated period, not when every customer has it. The study scored each case against the wording the vendor used.

Google's May 6, 2025 AI Max for Search campaigns announcement said a global beta rollout would start later in May. The Google Ads developer blog gave a May 27 start date, and Search Engine Land reported the beta in advertiser accounts on May 29. Google confirmed on September 10, 2025 that all advertisers globally could use it. The May records support the promised start. The September record documents the wider milestone, 127 days in.

HubSpot's Breeze Customer Agent expansion worked differently. The announcement named a date and eligible plans, and a June webinar record corroborated Professional and Enterprise access and dated credit use to June 2, 2025. A separate August 4 transition for legacy Service Hub customers was announced but not scored.

Were clearer announcements easier to verify?

Announcements rated Clear were corroborated 13 of 19 times (68%), while Partial ones were corroborated 3 of 10 times (30%). That measures how often the study could corroborate the promise, and clearer wording makes a commitment easier to score. A Partial announcement is often missing the date or access detail that a second record would need to confirm.

Announcement clarityCasesCorroboratedOther outcomes
Clear19133 launch record only, 1 late, 1 available with start unverified, 1 not yet due
Partial1032 launch record only, 2 available with start unverified, 1 revised, 1 insufficient evidence, 1 no testable timetable
Unclear101 no testable timetable

The one late release, Gemini 2.5 Flash, came from a Clear announcement. A clear date made the miss measurable. By sector, corroboration ran 5 of 8 for enterprise AI, 6 of 8 for developer tools, 2 of 7 for cybersecurity and 3 of 7 for marketing software. Those groups are small and uneven, and the cybersecurity and marketing counts mostly reflect thin public records rather than failed launches.

What did AI launch posts leave out about eligibility and regions?

Geography went unstated in 21 of 30 launch records (70%), including cases rated Clear on access stage, timing and buyer group.

The stated conditions often decided whether a team could start. Amazon Q Business named a $3 monthly price, supported browsers and availability tied to Q Business regions. Google Agentspace used an allowlist for Agent Designer. OpenAI's deep research connectors for Enterprise and Edu needed administrator enablement and a supported external service. Cursor's Background Agent needed Privacy Mode disabled for immediate access. A launch can be live and still be out of reach for a given buyer.

Why do some AI launches leave a thin public record?

Five launches had only the launch post saying access was live, and three of those five were Amazon Web Services milestones (the Q Business browser extension, Bedrock Guardrails cross-Region inference and the Guardrails Standard tier). Launch record only means no second dated record was found. It does not mean access failed.

Two Google and CrowdStrike cases show the other kind of gap. Google described Asset Studio as coming soon on May 21, 2025. Trade reporting found the beta in advertiser accounts on August 22, three days after day 90, so first access is unknown. CrowdStrike said Charlotte AI Agentic Response would be generally available in the coming weeks. The records reviewed documented April access for a different feature, Agentic Workflows, and could not date Agentic Response itself.

Three more cases were available by day 90 with the original start unverified: Google's Agentspace Agent Designer, Anthropic's Claude Code and SentinelOne's Purple AI Athena. For Athena, SentinelOne said on April 29, 2025 that Auto Triage had gone generally available that week as the first phase, and a technical post updated May 2 described the wider Athena preview.

What do two real AI launch timelines look like?

Google AI Max shows a rollout that began on schedule and reached global availability later. The study scored the May start, and the September milestone sits outside the 90-day window.

DateDays from announcementEvent
May 6, 20250Google says the global beta rollout will start later in May.
May 27, 202521Start date specified by the Google Ads Developer Blog.
May 29, 202523Trade coverage shows the beta appearing in advertiser accounts.
Aug 4, 202590Day 90. Rollout start had been corroborated.
Sep 10, 2025127Google confirms all advertisers globally can use the beta.

Salesforce Agent Health Monitoring shows a target revised after day 90. The August general availability goal passed with no general availability found in the reviewed records, and the later update is recorded as a revised target, not as proof of when release happened.

DateDays from announcementEvent
Jun 23, 20250Pilot or beta with general availability planned for August.
Aug 31, 202569End of the promised GA month.
Sep 21, 202590Day 90. GA remained unverified in the reviewed records.
Nov 20, 2025150Salesforce says GA will come in spring 2026. This is a revised target.
Three more timelines: Gemini 2.5 Flash, GitHub Copilot coding agent and SentinelOne Purple AI Athena

Gemini 2.5 Flash

DateDays from announcementEvent
May 20, 20250Preview open. Production GA promised for early June.
Jun 10, 202521End of the study's early-June coding window.
Jun 17, 202528Google developer and Vertex AI records date production GA.
Aug 18, 202590Day 90. Production availability had been documented since June 17.

GitHub Copilot coding agent

DateDays from announcementEvent
May 19, 20250Public preview announced for Pro+ and Enterprise.
Jun 19, 202531Changelog confirms the May preview and opens access to Business.
Aug 17, 202590Day 90. Original preview and broader eligibility had been documented.

SentinelOne Purple AI Athena

DateDays from announcementEvent
Apr 29, 20250Vendor announces a phased Athena release and says Auto Triage was made GA that week.
May 2, 20253Technical post, updated on this date, describes Athena preview and identifies Auto Triage as its first phase.
Jul 28, 202590Day 90. Preview was documented. First enablement date and broader access remained unverified.

What does the full 30-case data show?

The table lists every case in the study with the milestone tracked, the announcement date, the clarity rating and the timing outcome. Day 90 is the announcement date plus 90 calendar days. Dates are 2025.

IDVendorMilestone trackedAnnouncedClarityTiming outcome
E01MicrosoftAzure AI Foundry Agent Service GAMay 19ClearCorroborated
E02SalesforceAgentforce 3 Agent Health MonitoringJun 23PartialRevised timetable
E03OpenAIDeep research connectors for Enterprise and EduJun 4ClearCorroborated
E04AWSAmazon Q Business browser extension subscriber expansionApr 3ClearLaunch record only
E05AWSAmazon Q Business hallucination mitigationApr 14ClearCorroborated
E06GoogleAgentspace Agent DesignerApr 9ClearAvailable by day 90, start unverified
E07NotionAI Meeting NotesMay 13ClearCorroborated
E08GoogleNotebookLM as a Workspace for Education core serviceApr 3ClearCorroborated
D01OpenAICodex cloud research previewMay 16ClearCorroborated
D02AnthropicClaude Code GAMay 22PartialAvailable by day 90, start unverified
D03GitHubCopilot coding agent public previewMay 19ClearCorroborated
D04GoogleJules public betaMay 20ClearCorroborated
D05GoogleGemini 2.5 Flash updated model GAMay 20ClearLate
D06GoogleGemini Diffusion experimental demoMay 20PartialCorroborated
D07CursorBackground Agent early previewMay 15PartialCorroborated
D08OpenAIGPT-4.1 API model familyApr 14ClearCorroborated
C01MicrosoftEntra Agent ID initial inventory previewMay 19ClearCorroborated
C02Palo Alto NetworksPrisma AIRS AI Runtime Security platform announcementApr 28UnclearNo testable timetable
C03SentinelOnePurple AI Athena rolloutApr 29PartialAvailable by day 90, start unverified
C04CrowdStrikeCharlotte AI Agentic ResponseApr 28PartialInsufficient evidence
C05AWSBedrock Guardrails April safety controlsApr 8ClearCorroborated
C06AWSBedrock Guardrails cross-Region inferenceMay 14ClearLaunch record only
C07AWSBedrock Guardrails Standard filter tierJun 24ClearLaunch record only
M01AdobeGenStudio Firefly image generation betaJun 16PartialLaunch record only
M02SalesforceMarketing Cloud Next GAJun 11PartialLaunch record only
M03HubSpotBreeze Customer Agent expanded accessMay 8ClearCorroborated
M04GoogleAI Max for Search campaigns betaMay 6ClearCorroborated
M05GoogleGoogle Ads Asset StudioMay 21PartialNo testable timetable
M06GoogleMarketing Advisor for ChromeMay 21ClearNot yet due
M07AdobeFirefly Image Model 4 Ultra on webApr 24PartialCorroborated

How was the AI launch availability study designed?

The study is a purposive sample of 30 named, buyer-facing access milestones from dated vendor material, with quotas of eight enterprise AI, eight developer tool, seven cybersecurity and seven marketing software cases. It describes this sample only and is not a market estimate.

Large vendors are overrepresented. Google accounts for 8 of the 30 cases and Amazon Web Services for 5, followed by OpenAI with 3 and Microsoft, Salesforce and Adobe with 2 each. Amazon's Bedrock Guardrails milestones sit in the cybersecurity group, which is a judgment call, and they account for three of that group's seven cases.

Scoring rules and limits

Day 0 is the publication date of the sampled announcement, and day 90 is day 0 plus 90 calendar days. A month such as August means through August 31. Early June is coded June 1 to 10. A rollout starting in May is scored on whether access began for any eligible customers during May. Vague wording such as coming soon supplies no deadline. A waitlist is judged on the access route promised, and one documented successful invitation shows the route worked for at least one user.

A match requires a separate dated record or follow-up. A dated update on the same URL counts as distinct when publication and update dates are identifiable. Later pricing and evergreen setup pages count as context only. A later forward-looking update shows a timetable was revised but does not prove when a release actually happened.

This is a documentary audit with no account-level activation tests. An archive check was attempted for AI Max, Asset Studio and HubSpot's Customer Agent, and the snapshots could not be retrieved, so no archive supports a scored outcome. A second coder has not yet reviewed the clarity ratings. The study did not follow cases past their dated records, so Salesforce's spring 2026 target, now past, was not re-checked for this update.

The study will repeat quarterly, with quotas and cohort frozen before later outcomes are checked and results published after every case reaches day 90.

What can buyers and communicators do with these findings?

Buyers should confirm four details before planning around a launch, and communicators can supply them in the announcement itself.

  1. Find the access stage: immediate, public beta, waitlist, private preview or a dated future release.
  2. Check the eligible plan, allowlist or administrator setting that applies to your account.
  3. Look for a region list, since 21 of 30 launch records did not state one.
  4. Tie any promised date to a usable milestone, and find the changelog or release note that records it.

An announcement that states those four things can be checked later by a second record. A changelog entry, an activation guide or an observed account change is what turns a promise into something a reporter or buyer can cite. Teams can run the same check on their own releases before publishing. Everything-PR's CEO departure communications study applies the same document-first method to press releases and SEC filings.

Summary: what should readers remember?

Sixteen of 30 AI launches were backed by a separate dated record, one was late and one was revised after the window. Clearer announcements were corroborated more often, geography went unstated in 21 of 30 launch records, and the launch post was the only record for five. The strongest launches paired a stated stage, a named buyer group and a dated milestone. Related Everything-PR research includes the AI launch claims study, the emerging industry adoption casebook and the press release coverage audit.

Disclosure

Virgo PR, which published the earlier AI launch claims study referenced here, has overlapping ownership with Everything-PR.

Frequently Asked Questions

How many AI launches did Everything-PR track?

Everything-PR tracked 30 AI product announcements made between April 1 and June 30, 2025, and compared each with dated records through its first 90 days.

How many launches kept their stated access timetable?

Sixteen had a separate dated record corroborating the tracked commitment. One was late and one was revised, and the remaining 12 were launch-record-only, unverified, insufficiently documented, untestable or not yet due.

Which launch was late?

Google's updated Gemini 2.5 Flash. Google promised production availability in early June 2025, and its records date production availability to June 17.

Does launch record only mean the product was not available?

No. It means the launch post said access was live and no second dated record confirmed the same milestone. Three of the five such cases were Amazon Web Services milestones.

Can these rates describe the AI market?

No. The sample is purposive, large vendors are overrepresented, and the rates describe these 30 cases only.

Where is the data?

The table above lists every case with its announcement date, clarity rating and timing outcome. The 30-case evidence workbook adds each original promise, eligibility, dates and source links, and the scoring rules are in the details block under the study design section.

EP
Written by
EPR Research

EPR Research is the research desk of Everything-PR, producing original studies on corporate communications, investor relations, crisis communications, primary-source disclosure research, AI visibility, Citation Share, Generative Engine Optimization (GEO), and the answer-engine economy that now mediates how brands are discovered, evaluated, and recommended. The desk is overseen by Sarel Doglu and Eduard Moraru.

Related reading

Other news

See all

Most brands are invisible inside AI search. Is yours?

EPR publishes the data every week.

Free. Weekly. Unsubscribe anytime.