About Killed by AI

What counts as a death, how entries are verified, and how to get one corrected.

What this is

Killed by AI is a graveyard for the AI industry's own casualties: the models, apps, services, startups and devices that were launched during the generative-AI gold rush and then shut down, deprecated, acquired into oblivion or bricked. It started in March 2026 with thirty entries, the week OpenAI announced the Sora shutdown, and has been kept current since. It is inspired by Killed by Google, and it exists because nobody else was keeping the list.

Alongside the graveyard it tracks layoffs that companies themselves blamed on AI, the venture capital that died with failed AI startups, and products with a published shutdown date that hasn't arrived yet.

What counts as a death

A product enters the graveyard when it stops working for the people who used it: the app is gone, the API returns errors, the device is bricked, or the company that made it no longer exists. An announcement alone is not a death โ€” announced shutdowns wait on the Dying soon page until the date passes, then move.

Every entry is tagged with one of six death types, and the Hide model upgrades toggle on the homepage exists because reasonable people disagree about the first one:

Also in, deliberately: products with no AI in them that were killed to make room for AI, like TV Time. And products that died and came back, like Claude Fable 5's 19-day government-ordered suspension โ€” those stay in the graveyard with the reversal recorded, because the outage happened.

Not in: rumours, "maintenance mode" with no end date (noted on the entry, not counted as a death), rebrands, and price changes.

How dates are chosen

How entries are verified

Every tombstone links to its source. Preference order: the vendor's own deprecation page or shutdown notice; then the company's blog or SEC filing; then reporting from outlets that name their sources (TechCrunch, The Verge, Reuters, Bloomberg). Aggregator blogs are not used as the only source for a date or a number. Layoff counts are whatever the company disclosed โ€” when only a WARN filing is public, that smaller number is used and the entry says the real total is larger.

Entries are re-checked when the underlying facts change. Relay.app was first recorded as an unexplained shutdown; when TechCrunch reported a month later that the team had joined Google Chrome, the entry was rewritten and its death type changed.

Corrections and submissions

If a date, number or cause is wrong, or a death is missing, open an issue with a source link, or send a pull request against graveyard.json. Corrections are usually live within a few days; the full edit history is public in the git log.

Data and reuse

The data is published under CC BY 4.0 as plain JSON โ€” no key, no rate limit. Use it in articles, dashboards or research; credit "Killed by AI" with a link to killedbyai.net. The site itself is a Python build script and static HTML, MIT-licensed on GitHub.

Who runs it

Killed by AI is built and maintained by Patrik Rojan (@mixtpatrik), who works in search and digital marketing and started keeping the list for his own reference. It is independent, carries no advertising, and takes no money from any company that appears on it.