See what launched, what changed, and what it costs.
Track AI product launches, model updates, pricing changes and tested workflows. Each record separates official sources, company claims, Kingy testing and third-party evidence so you can see what is known and what remains unverified.
Editorial submissions and sponsor-fit reviews are separate. Payment does not influence Kingy scores, verdicts, rankings, evidence labels, or publication decisions.
Launch tracker
Browse the AI Launch Tracker
Search source-backed launch records, then use common filters first and advanced filters only when you need a narrower view.
Server-rendered fallback. Checking the live launch index…
Hugging Face introduced Serge on June 12, 2026: an Apache-2.0 GitHub-native pull-request reviewer with repository-owned policy and Action, App or web deployment. The manual web workflow supports editable…
Recheck dueFree: UnknownAPI: UnknownOpen: Yes
Developer-friendly
Repository-owned review rules and editable drafts give maintainers concrete controls. Manual web reviews can be edited, discarded or published; the same deployment's webhook route…
OpenAI announced an agreement to acquire Ona, subject to customary closing conditions, with the stated intent to bring Ona’s secure, persistent, customer-controlled cloud execution and orchestration technology into…
Recheck dueFree: NoAPI: NoOpen: No
Business-friendlyDeveloper-friendly
Ona gives OpenAI a credible route toward persistent, governed execution for Codex, but the announcement is a transaction and product-direction statement, not proof that…
GitHub announced general availability on October 28, 2026, after the June 11 public preview. The update adds nonexperimental cost forecasting and model routing. GitHub lists availability on github.com…
Source-verifiedFree: UnknownAPI: UnknownOpen: Yes
Developer-friendly
GitHub Agentic Workflows gives repository teams a way to define agent-driven Actions in Markdown. Review the generated workflow, permissions and expected model and Actions…
GitHub updated Copilot Chat so it can search and query past Copilot cloud agent sessions in chat.
Recheck dueFree: UnknownAPI: UnknownOpen: No
Launch readiness
6.5 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-12.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
GitHub updated Copilot Chat to search and query past Copilot cloud agent sessions, per the June 10, 2026 changelog (github.blog). Developers and Engineering Teams…
Replit added a Shopify workflow where users can design and launch a custom storefront by chatting with Replit Agent, including generating a front end, creating a Shopify store,…
Recheck dueFree: YesAPI: NoOpen: No
Beginner-friendlyCreator-friendly
Launch readiness
6.5 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
OpenAI introduced new GPT-Rosalind capabilities aimed at improving biological reasoning, bioinformatics, and autonomous scientific workflows.
Recheck dueFree: NoAPI: NoOpen: No
Launch readiness
5.7 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
OpenAI introduced new GPT-Rosalind capabilities aimed at biological reasoning, bioinformatics, and autonomous scientific workflows. That June 3, 2026 announcement is historical launch context. Its…
Replit introduced SEO Agent, which scans published apps, identifies discoverability issues, and can apply fixes for web search and AI search visibility.
Recheck dueFree: YesAPI: NoOpen: No
Beginner-friendlyBusiness-friendly
Launch readiness
6.4 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Replit introduced SEO Agent, which scans published apps, flags discoverability issues, and can apply fixes for web and AI search visibility (replit.com). Replit Builders…
Microsoft introduced Scout, its first Autopilot agent, designed to stay active in the background, connect across Microsoft 365 apps, and help coordinate work under enterprise controls.
Recheck dueFree: NoAPI: NoOpen: No
Launch readiness
5.9 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Microsoft introduced Scout, its first Autopilot agent — designed to stay active in the background, connect across Microsoft 365 apps, and coordinate work under…
OpenAI expanded Codex across roles, tools, and workflows, positioning it as a broader professional agent for software-adjacent and knowledge-work tasks.
Recheck dueFree: NoAPI: YesOpen: No
Creator-friendlyDeveloper-friendly
Launch readiness
6.1 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
OpenAI expanded Codex across roles, tools, and workflows, positioning it as a broader professional agent for software-adjacent knowledge work (openai.com). Developers, Product Managers, Data…
OpenAI announced that frontier models and Codex are available on AWS, expanding enterprise deployment options for OpenAI-powered agentic workflows.
Recheck dueFree: NoAPI: YesOpen: No
Launch readiness
6.2 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
OpenAI announced that its frontier models and Codex are available on AWS, confirmed by both companies' posts (openai.com). Enterprise Platform Teams standardized on AWS…
Mistral AI relaunched Le Chat as Vibe, a unified agent for long-horizon work and coding with Work Mode, Code Mode, VS Code support, CLI updates, and mobile access.
Recheck dueFree: YesAPI: YesOpen: No
Business-friendlyDeveloper-friendlyTraction signal
Launch readiness
7.1 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Anthropic released Claude Opus 4.8 with improved coding, agentic task performance, professional work quality, effort controls, and Claude Code dynamic workflows.
Recheck dueFree: NoAPI: YesOpen: No
Business-friendlyDeveloper-friendlyTraction signal
Launch readiness
7.9 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Anthropic released Claude Opus 4.8 with improved coding, agentic task performance, effort controls, and Claude Code dynamic workflows, priced at $5 per million input…
Cohere released Command A+ as an Apache 2.0 open-source MoE model optimized for reasoning, multilingual, multimodal, RAG, and agentic workflows.
Recheck dueFree: YesAPI: YesOpen: Yes
Business-friendlyDeveloper-friendlyTraction signal
Launch readiness
7.2 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Cohere released Command A+ as an Apache 2.0 open-source MoE model built for reasoning, multilingual, multimodal, RAG, and agentic enterprise workflows (cohere.com). Developers, Enterprises,…
Google introduced Gemini Spark as a 24/7 personal AI agent alongside a more agentic Gemini app, Daily Brief, and other I/O 2026 Gemini updates.
Recheck dueFree: NoAPI: NoOpen: No
Launch readiness
6.6 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Google launched Managed Agents in the Gemini API, allowing developers to run Antigravity or custom agents in secure Google-hosted Linux sandboxes using markdown-defined instructions and skills.
Recheck dueFree: YesAPI: YesOpen: No
Launch readiness
6.7 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Google launched Managed Agents in the Gemini API, letting developers run Antigravity or custom agents in secure Google-hosted Linux sandboxes using markdown-defined instructions and…
Kiro launched Kiro Web in preview, letting paid users start browser-based sessions where Kiro can write code, coordinate across repositories, and open pull requests.
Recheck dueFree: NoAPI: YesOpen: No
Launch readiness
6.6 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
AWS launched Kiro Web in preview, letting paid users start browser-based sessions where Kiro writes code, coordinates across repositories, and opens pull requests (kiro.dev).…
Cursor released Composer 2.5, describing it as a substantial improvement over Composer 2 for sustained long-running tasks, instruction following, and collaboration.
Recheck dueFree: NoAPI: NoOpen: No
Launch readiness
6.2 / 10
Demo evidence
Not scored yet
Creator-story fit
Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
Assigned by
Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
Rubric and check date
Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
Confidence and missing data
Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
Freshness
Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
Disputes
Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Anysphere released Cursor Composer 2.5, calling it a substantial improvement over Composer 2 for sustained long-running tasks, instruction following, and collaboration (cursor.com). Cursor users…
OpenAI released GPT-Realtime-2, GPT-Realtime-Translate, and GPT-Realtime-Whisper for realtime voice reasoning, translation, and streaming transcription in the API.
Recheck dueFree: NoAPI: YesOpen: No
Business-friendlyDeveloper-friendlyTraction signal
A high-signal API launch because it moves voice AI toward realtime agents that can reason, translate, transcribe, and act during a conversation.
November 6 catch-up: Google DeepMind’s October 27 Genie 4 research preview, trusted-tester access, waitlist and limits on pricing and wider availability.
No source-ready records are tagged for today yet, so this section is showing the latest public launch records available in the tracker.
AI Models
Gemini Omni 1.2 Flash
Summary: Google launched Gemini Omni 1.2 Flash on November 5, 2026, with general availability through the Gemini API and Gemini for business.
Why it matters: Gemini Omni 1.2 Flash gives video teams longer native clips and editing controls. Check the selected output settings and actual billing units before estimating…
Pricing
The announcement lists US$0.07 per second for 720p video. The API changelog separately lists US$12 per million video output tokens. These are different billing units; check the applicable settings and current terms.
Summary: OpenAI introduced GPT-6 Cyber on November 5, 2026, with initial API and Codex access for select approved Daybreak Red customers. Wider access is planned.
Why it matters: GPT-6 Cyber is relevant to security teams eligible for Daybreak Red. Confirm approval, permitted use and pricing before planning work around its restricted API…
Pricing
Standard API rates per million tokens are US$20 input, US$2 cached input and US$100 output. Cache writes are US$25 for 30 minutes or US$50 for 12 hours per million tokens. Context length and processing choices can change rates; confirm approved-access terms and the current pricing table.
Summary: OpenAI released Images 2.6 on November 4, 2026, in ChatGPT and Codex across all subscription tiers, plus Sunburst and Flare API variants.
Why it matters: Images 2.6 expands image workflows across OpenAI products. Compare Sunburst and Flare on your own edits and check API billing separately from subscription limits.
Pricing
API rates per million tokens for both variants: image input US$8, cached image input US$2 and image output US$30; text input US$5 and cached text input US$1.25. Subscription limits and API billing are separate.
Summary: Mistral made improved Large 4 weights downloadable on October 29, 2026, following its October 6 public preview. The repository documents text and image input, text output,…
Why it matters: Mistral Large 4 gives teams a documented choice between an API and downloadable weights. Evaluate the commercial-license restriction, infrastructure cost and your own task…
Pricing
Mistral's USD model documentation lists $0.70 input, $0.07 cached input and $2.10 output per million tokens. Self-hosting costs are separate.
Summary: GitHub announced Copilot Fusion general availability on October 28, 2026, on all Copilot plans in VS Code, the Copilot app, Copilot CLI and JetBrains IDEs. Users…
Why it matters: GitHub Copilot Fusion gives existing Copilot users an orchestration option in supported clients. Confirm your plan’s models and effort settings, monitor credit use and…
Pricing
Each underlying model is billed at its standard rate with no separate Fusion charge. Official docs specify a 30% paid-plan model-cost discount through November 30, 2026. Multiple-model tasks can consume more credits.
Summary: Google announced Gemini 4 Carbon on October 28, 2026. Access starts with a subset of cyber defenders and is to expand gradually to trusted Fairwind partners.…
Why it matters: Gemini 4 Carbon is currently relevant to teams admitted to Google’s controlled cyber-defense rollout. Broader developer, business and consumer access is a future step.…
Pricing
Announced introductory API rates are US$2 per million input tokens and US$10 per million output tokens, with cached input 95% below the input rate. Google lists later rates of US$4 and US$20 after the introductory period, without a confirmed expiry here. These announced rates do not establish a generally callable public API.
Future-dated migration, shutdown, and retirement records are separated from today's launches and latest-record lists. These dates are upcoming operational events, not launches that have already happened.
AI Agents
OpenAI Agent Builder shutdown deadline: November 30, 2026
Summary: OpenAI announced the Agent Builder lifecycle deadline: the visual workflow builder is deprecated and scheduled to shut down on November 30, 2026. OpenAI documents two migration…
Why it matters: Export the workflow, select the Agents SDK or a suitable Workspace Agent, and test tools, state, permissions and guardrails before the November 30 shutdown.…
Pricing
Review replacement API costs or Workspace Agent plan requirements before migrating. This record does not estimate your workflow’s implementation or operating cost.
OpenAI reusable prompt objects and v1/prompts are scheduled to shut down November 30, 2026
Summary: OpenAI announced reusable-prompt deprecation on June 3, 2026. The documented November 30 shutdown covers reusable prompt objects and v1/prompts. Move managed prompt content into application-owned code…
Why it matters: Treat saved OpenAI prompt objects as a migration dependency before November 30. Move their content and variables into application code, then validate the generated…
Three GPT Image API models are scheduled to retire December 1, 2026
Summary: OpenAI schedules gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest for API removal on December 1, 2026. Its current deprecation table recommends gpt-image-2.5-sunburst or gpt-image-2.5-flare.
Why it matters: OpenAI schedules gpt-image-1-mini, gpt-image-1.5 and chatgpt-image-latest for API removal on December 1, 2026. Its current deprecation table recommends gpt-image-2.5-sunburst or gpt-image-2.5-flare. Inventory the three…
Pricing
Review the current price of the chosen replacement and measure representative jobs. This lifecycle record does not establish workload cost or promise a cost-neutral migration.
After submitting, look out for the welcome email from The Kingy Brief. If the form asks you to confirm, open the confirmation email too. Check Spam or Promotions if you cannot find it.
Fridays at 09:00 Vancouver time: source-checked AI changes, original tests and one practical thing to try. We skip a week when there is not enough verified material. Free. Unsubscribe anytime.
Kingy AI scoring is designed for launch discovery, editorial review, creator planning, and buyer trust checks.
Kingy score
A directional editorial score for launch clarity, source quality, audience fit, pricing visibility, demo usefulness, and practical buyer or creator value.
Demo score
A signal for whether the product can be shown, tested, explained, or compared without relying on vague announcement copy.
YouTube potential
A creator-fit signal for demos, tutorials, before-and-after workflows, explainers, reviews, and audience-specific product education.
Source verification
Records distinguish verified, needs verification, and founder submitted status using official URLs, source links, last-verified dates, and correction paths.
Pricing clarity
Pricing signals favor launches with visible pricing, free-plan status, pricing pages, API access notes, or clear uncertainty when pricing is not public.
Use-case clarity
Launches are easier to evaluate when the audience, workflow, category, demo, and alternative comparison are obvious from public sources.
Founder and sponsor fit
Founder submissions and sponsor interest are routing signals only; editorial review still checks source quality, public claims, demo clarity, and usefulness.
Verification labels
Verified means enough public source evidence is present, needs verification means the record needs more checking, and founder submitted means the entry came through the submission path.
Scores are editorial signals, not scientific benchmarks, paid placements, or guarantees.
Founder submission
Submit Your AI Launch
Founders can send a launch for editorial review when the public source trail is ready to verify.
What to include
Product name
Website
Launch date
What launched
Official source links
Pricing page
Demo/video
Company info
Category
Public funding info
Screenshots/media
Privacy note
Do not submit secrets, unreleased financials, private customer data, or regulated personal data.
Submit only public product, company, source, pricing, demo, and media details that Kingy AI can review without logging into private systems.
Fridays at 09:00 Vancouver time: source-checked AI changes, original tests and one practical thing to try. We skip a week when there is not enough verified material. Free. Unsubscribe anytime.
ModelsAgents & harnessesDeveloper infrastructureProductsFunding & company movesPricing watchUnder the radar