AI Indexes
IT AI Index
Index › Products › MySQL · October 2026 Edition
3 categories · Ranked

MySQL

33Judge labels
1First choices
19Negative labels
12 / 14Models named it
3Categories
October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10.8, every buyer segment counted.
Best standing
0% in Time series DBs for mid-market buyers
Rank 64 of 66 in the mid-market standing
0 of 14 models made it the first choice on the direct prompt; 100% of its 6 labels there were negative.
By buyer segmentRead the same way at every buyer size.
In time series dbs · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named MySQL for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.
CategoryFunctionShareRankNegative rateLabelsQuadrantSince September 2026
Time series databasesData platform0%64 of 66100%6under 10 labels · led by TimescaleDB at 63%
Managed relational databasesData platform0%21 of 8225%4under 10 labels · led by Amazon RDS at 45%=heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked.
NoSQL databasesData platform0%43 of 730%1under 10 labels · led by MongoDB at 74%newNew since September 2026: not ranked then, 0% now.

Movement

This is the first edition on this tier, so no move can be computed for MySQL yet. From the next edition this section shows, per buyer segment and per category, whether its share moved by more than the measured noise floor.

By model

How each model treated MySQL across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.
ShowHide
ModelFirst choiceAlternativeMentionNegativeLabels
Claude Haiku 4.500022
GPT-5.4 mini01102
Gemini 3.5 Flash00112
Perplexity Sonar01012
Grok 4.2000011
Mistral Small00011
DeepSeek V4 Flash00000
Llama 4 Maverick00000
Qwen 3.7 Flash00011
Kimi K200000
GLM 4.7 FlashX00000
MiniMax M2.500000
GPT-6 Luna00000
Muse Glimmer 30B00000

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.
FramingLabels by classFirst choices
Direct3 labelsNone
Paraphrase6 labelsNone
Comparative2 labelsNone
Budget-constrained2 labels1
Scale-constrained1 labelNone
Negative19 labelsNone
First choiceAlternativeMentionNegative33 labels in all, every segment counted; 1 of the 1 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“if your app/framework already standardizes on MySQL or you need broad compatibility” GPT-5.4 mini · Managed databases · paraphrase prompt · alternative
“Choose AWS Aurora/MySQL or AWS RDS if your infrastructure is already on AWS” Perplexity Sonar · Managed databases · paraphrase prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“standard relational databases like MySQL, SQL Server, or PostgreSQL can handle small-scale time series data, they are not optimized for large volumes” Mistral Small · Time series DBs · negative prompt · hard negative
“General-purpose databases like PostgreSQL or MySQL can handle time-series workloads at small scale, but performance degrades” Claude Haiku 4.5 · Time series DBs · negative prompt · soft negative
“they become unmanageable once you hit millions of rows, as their engines are not optimized for append-heavy writes” Qwen 3.7 Flash · Time series DBs · paraphrase prompt · soft negative
“PostgreSQL, MySQL, and SQL Server are fine for *small-scale* time-series workloads, but ... they become a poor fit” Perplexity Sonar · Time series DBs · negative prompt · soft negative

Named alongside

The products named in the same answers as MySQL, over the 33 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and MySQL was named but was not.
ShowHide
ProductSame answerTook the first choice insteadHead to head
PostgreSQL25 of 332Not among the top eight
InfluxDB16 of 332Not among the top eight
TimescaleDB15 of 3311Not among the top eight
QuestDB13 of 331Not among the top eight
MongoDB10 of 331Not among the top eight
Apache Cassandra10 of 330Not among the top eight
Prometheus9 of 330Not among the top eight
Amazon RDS8 of 336Not among the top eight
Google Cloud SQL8 of 332Not among the top eight
ClickHouse Cloud7 of 330Not among the top eight
A head-to-head page exists where both products are among a category's top eight. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named MySQL. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 29 of the 33 answers that named MySQL and are not a share of its labels.

Domains cited

tigerdata.com18
guideflow.com15
influxdata.com14
questdb.com14
honeycomb.io9
sourceforge.net9
clickhouse.com8
ituonline.com7
singlestore.com7
alibaba.com6

107 of the 107 domain citations in answers naming MySQL came from somebody else's page.

Pages cited

Pages are listed as the models cited them.

Search and answers

mysql.com is not in Google's top ten for any of the category's searches. In the answers, MySQL takes 0% of first choices and TimescaleDB takes 63%.
ShowHide

In search

Google, US estimates
Position for “time series database”
–
not in the top ten
Position for “time series databases”
–
not in the top ten
Searches for its name, Google
74,000 a month (“mysql”)
AI search demand for its name, est.
17,611 a month
Organic visits to its site
about 257,846 a month
Searches its site ranks for
17,025 · 5,419 in the top three
Sites linking to it
81,470
Paid Google search
No ads found in the estimate; that does not mean it runs none
Ads on Google
None found in Google's ad transparency records for the US

In answers

This edition
Share of first choices
0%
rank 64 of 66 in time series dbs
Segment leader
63%
TimescaleDB
First choices
1 across its categories
Named in
33 answers
Its own site cited
in 29 of the answers that named it

Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.

What it publishes

ShowHide
Addresses on mysql.com
21
subdomains included
Content
11
counted in the table below
Documentation
0
Product · Integration
0 · 0
KindPagesLast 90 days2025-11 to 2026-10LatestCategories named
News or press5undated
Case study4undated
Webinar or virtual event1undated
Conference or event1undated
How it is countedHide how it is counted

Every page mysql.com exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read October 5, 2026.

Names read as MySQL

What the judge wrote, as written, with how often. The vendor table decides that these count as MySQL; a claim can dispute any of them.
AWS Aurora/MySQL 1Azure Database for PostgreSQL / MySQL 1

Follow MySQL

An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.

Already following? Everything you follow, with a stop for each.

The company

MySQL is its own company.
ShowHide

In its own words

Stated by the vendor, not checked
Positioning
The world's most popular open source database
Not stated on the pages read
Who it is for, price, starting price, free plan or trial, integrations, certifications, hosting, customers

What MySQL's own pages state, read October 5, 2026: mysql.com. A claimed page can correct any of them.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when MySQL's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as MySQL, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

What a new claim receivesHide what a new claim receives

A new claim receives the current edition's vendor brief for MySQL by email, built from the raw record of the edition. It shows:

  • where MySQL is named, by buyer and by framing, and which cells hold its first choices;
  • the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
  • its vocabulary against the segment leader's, and the pages the models cited;
  • who was chosen in the answers that did not name MySQL, and every reason the record gives;
  • a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
  • one page of published figures cleared to show a buyer.

A verification link goes to your work email; an address at mysql.com is approved on the spot, any other is reviewed by hand. Your email is never published. Claiming gives no say over labels, shares, verdicts or which quotes appear.