Understand which software products are actually gaining ground
ATC combines developer activity, enterprise-adoption signals, product discussion, adoption-observed company breadth, and change over time, then gives Claude or ChatGPT the structured evidence needed to produce a market analysis.
Inspect a real recorded analysis of Cursor and its peers below. New questions require the authenticated MCP connector.
Recorded analysis - no signup to inspect - static data - new queries require MCP
RECORDED MARKET ANALYSIS
Is Cursor overhyped?
This is a recorded run generated from the prompt below using ATC MCP. The public web presentation is adapted for responsive inspection; raw responses and internal evidence identifiers are withheld.
Data throughMay 31, 2026
Capture dateJune 24, 2026
ClientClaude
ModelNot supplied
StatusStatic recorded artifact
View exact prompt
Is Cursor overhyped? Compare Cursor, Claude Code, GitHub Copilot, and Windsurf across developer activity, enterprise-adoption signals, product discussion, adoption-observed company breadth, and time-series momentum. Return a verdict, supporting and conflicting evidence, chart-ready trajectories, developer discussion themes, company evidence, and methodology limits.
Monthly developer-activity signal across the AI coding tools in the recorded analysis.
monthly developer-activity recordsJun 2024 - May 2026
Cursor rises steadily over two years, but Claude Code accelerates after February 2025 and finishes about 2.7 times higher than Cursor by May 2026. GitHub Copilot and Windsurf are flatter by comparison.
Cursor climbed steadily, then decelerated through 2025. Claude Code launched into the measured set in February 2025 and crossed Cursor's raw developer-activity signal around September 2025.
Recent months can lag while public signals are collected and resolved. Missing values are shown as gaps, not interpolated.
Log scale omits zero and missing points from the plotted line.
The signals point in the opposite direction: Cursor remains a real, still-growing category leader with strong reach and entrenchment. The pressure is that momentum has rotated toward Claude Code, which sits one layer below Cursor in the stack.
MOMENTUM
Where Cursor sits today
ATC's composite momentum blends growth pace, activity volume, acceleration, and adoption-observed company breadth on a 0-100 scale.
Claude CodeMay 31, 2026
82.1
Breakout
Developer activity and discussion accelerated fastest after launch.
Companies with enterprise-adoption signals
2,379
GitHub CopilotMay 31, 2026
80.0
Strong
Broad enterprise-adoption signal footprint remains the largest in the set.
Companies with enterprise-adoption signals
2,820
CursorMay 31, 2026
77.3
Strong
Balanced profile across reach, discussion, and developer activity.
Companies with enterprise-adoption signals
2,025
WindsurfMay 31, 2026
71.6
Strong
Visible discussion and developer activity, but much narrower enterprise breadth.
Companies with enterprise-adoption signals
92
TRAJECTORY
Two years of signal, month by month
The monthly series shows when Cursor's growth normalized, when Claude Code broke out, and when enterprise-adoption activity inflected.
Enterprise-adoption activity
Monthly companies with newly observed public enterprise-adoption signals.
companies with new enterprise-adoption signals per monthJun 2024 - May 2026
GitHub Copilot starts from the broadest enterprise-adoption signal base. Cursor and Claude Code inflect upward during 2026, while Windsurf remains much smaller.
A sharp early-2026 inflection for both Cursor and Claude Code suggests adoption moving from individual developers to broader enterprise rollout signals.
Company breadth is outside-in adoption-associated evidence. It is not a contract registry or seat count.
Log scale omits zero and missing points from the plotted line.
Cursor's strength is footprint. Momentum and footprint are related but distinct signals.
Momentum
Current velocity and acceleration.
Footprint
Accumulated observed activity or company breadth.
Enterprise-adoption footprint
cumulative companies with enterprise-adoption signals
GitHub Copilot
2,820
Claude Code
2,379
Cursor
2,025
Windsurf
92
Enterprise-adoption footprint data
Product
cumulative companies with enterprise-adoption signals
GitHub Copilot
2,820
Claude Code
2,379
Cursor
2,025
Windsurf
92
Developer usage footprint
cumulative developer-activity signal
Claude Code
11,021
Cursor
4,118
Windsurf
1,250
GitHub Copilot
1,207
Developer usage footprint data
Product
cumulative developer-activity signal
Claude Code
11,021
Cursor
4,118
Windsurf
1,250
GitHub Copilot
1,207
Cumulative footprint does not imply active monthly users, contracts, seat counts, or internal deployment records.
THESIS
Where Cursor wins, where it is exposed
WHERE CURSOR WINS
Enterprise reach
Cursor shows 2,025 companies with enterprise-adoption signals and 2,468 companies carrying a broader Cursor-associated signal, including Halliburton, Under Armour, MITRE, and Andreessen Horowitz.
Balanced profile
Discussion, usage, and adoption-associated signals move together rather than depending on one isolated channel.
Still growing
Developer activity rose 112 percent over 24 months and remains visible. Enterprise-adoption activity inflected upward in early 2026.
WHERE CURSOR IS EXPOSED
Growth laggard
Cursor's developer-activity growth is real, but it is slower than the fastest-moving peer in this recorded set.
Disintermediation risk
The product gaining share fastest sits one layer below Cursor. Category consolidation toward model labs is the structural threat.
Moat narrative
The developer corpus surfaces pricing backlash and questions about differentiation when the underlying models are similar.
VOICE OF DEVELOPER
What developers are saying
646 analyzed public comments over the trailing year. Approximately 80 percent Hacker News and 20 percent Reddit over the trailing year.
Observed comments were grouped into themes by ATC and summarized by the model. Direct quotations are not included in this public version.
Substitution
Developers describe moving from Cursor to Claude Code or Codex after a step-change in output quality.
Commoditization
The moat question appears repeatedly: what does Cursor offer over a code editor when the underlying models are the same?
Pricing friction
Billing and packaging complaints appear as a recurring friction point that could increase churn.
Real entrenchment
Counterweight themes describe Cursor embedded in production workflows and in compliance-sensitive engineering contexts.
EVIDENCE
Companies with recent Cursor-associated signals
A sample of companies where ATC observed recent public signals associated with Cursor. These are outside-in adoption indicators, not confirmed contracts, seat counts, or internal deployment records.
HalliburtonEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public role or work-description evidence
Public summary
Public technical-work evidence associated Cursor with engineering workflows at the company.
Under ArmourEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public role or work-description evidence
Public summary
ATC resolved a recent public signal associating Cursor with software-development work.
MITREEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public technical evidence
Public summary
Public evidence linked Cursor to developer tooling or engineering practice discussion.
Andreessen HorowitzEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public technical evidence
Public summary
ATC observed a public Cursor-associated signal in the organization's software ecosystem.
Extreme NetworksEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public role or work-description evidence
Public summary
Public work-description evidence associated Cursor with engineering activity.
FluenceEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public technical evidence
Public summary
ATC resolved a recent public signal connecting Cursor to developer workflows.
SugarCRMEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public role or work-description evidence
Public summary
Public technical evidence associated Cursor with software-development activity.
SpliceEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public technical evidence
Public summary
ATC observed a recent public Cursor-associated engineering signal.
Ria FinancialEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public role or work-description evidence
Public summary
Public evidence associated Cursor with developer tooling in a software-work context.
1-800 ContactsEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public technical evidence
Public summary
ATC resolved a recent public signal tied to Cursor and engineering activity.
DHI GroupEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public role or work-description evidence
Public summary
Public work-description evidence associated Cursor with technical workflows.
BetclicEnterprise-adoption signal
Observed date
June 14, 2026
Source category
Public technical evidence
Public summary
ATC observed a recent public Cursor-associated software-development signal.
TOOL TRACE
From one question to a structured market analysis
ATC supplies structured research data and derived metrics. The AI model produces the narrative and presentation.
01
The user asked the exact prompt shown on this page.
02
ATC MCP returned structured product momentum, chart data, company evidence, developer voice themes, and product relationships.
03
The model synthesized a market-analysis narrative from those structured responses.
04
A human review removed internal evidence identifiers and withheld raw responses that were not marked public.
05
The public page adapts the report into responsive HTML, static SVG charts, accessible summaries, and data tables.
Exact user prompt
Is Cursor overhyped? Compare Cursor, Claude Code, GitHub Copilot, and Windsurf across developer activity, enterprise-adoption signals, product discussion, adoption-observed company breadth, and time-series momentum. Return a verdict, supporting and conflicting evidence, chart-ready trajectories, developer discussion themes, company evidence, and methodology limits.
Internal evidence identifiers omitted from company evidence.
Raw structured responses withheld because they are not marked public.
Direct developer quotations withheld; the public version shows approved theme summaries only.
DISCUSSION IN CONTEXT
Attention is one signal, not the whole picture
Discussion activity shows what people are talking about. ATC also examines developer activity, enterprise-adoption signals, adoption-observed company breadth, product relationships, time-series trajectory, and supporting or conflicting evidence.
Mention-frequency and search-frequency views can be useful. ATC is complementary: it is built to connect attention to broader software-market evidence.
METHODOLOGY
What these signals mean
Developer activity
Public developer, open-source, repository, community, or related activity as defined in the approved methodology. It is not equivalent to active seats.
Enterprise-adoption signals
Public role, work-description, initiative, or related evidence associated with a product and company. It is not a contract registry.
Adoption-observed company count
Unique companies with qualifying adoption-associated evidence under the approved methodology.
Product discussion
Public discussion activity associated with the product, after approved deduplication and resolution.
Composite momentum
A derived measure combining approved growth, volume, acceleration, and company breadth components.
Model-generated
The final explanatory prose, thesis, and report structure produced by the AI model from structured responses.
ATC is an outside-in research system. It should not be treated as a contract registry, CMDB, procurement database, product telemetry system, or implementation audit.
A market conclusion is a research thesis, not ground truth.
OTHER QUESTIONS
Other questions ATC can investigate
These prompt cards are static examples. They do not execute on this page.
Compare Snowflake, Databricks, ClickHouse, DuckDB, and Dremio.
Which observability platforms are accelerating?
Compare Vercel, Cloudflare, Netlify, and Fly.io.
Which data-infrastructure products show developer-led versus enterprise-led momentum?
What are developers saying about a product's moat, pricing, and workflow entrenchment?
Which companies show recent adoption-associated signals for a product?
RUN YOUR OWN ANALYSIS
Ask your own software-market questions
Connect ATC to Claude or ChatGPT to run new comparisons, investigate products, inspect company evidence, and explore software ecosystems.
https://mcp.atc-analytics.com/mcp
Claude
Open Claude and go to Customize, then Connectors.
Add a custom connector.
Paste the ATC MCP URL.
Authenticate with ATC.
Enable ATC in a conversation and paste a software-market prompt.
No writes to CRM, email, warehouse, or internal systems
ATC is not a proxy for the ordinary prompt stream
PRICING
Enough free usage to evaluate it
50 free credits each month
No credit card required
Most research calls cost 1 credit
Some longer workflows cost more
LIMITATIONS
Current limitations
The analysis is static and does not reflect changes after the data-through date.
Public-source coverage and recency vary by product, company, and source class.
Company breadth counts represent qualifying outside-in signals, not confirmed contracts, seat counts, or deployment records.
Discussion activity measures public attention and argument structure; it is not a usage metric.
Composite momentum is a derived measure and can change when methodology, coverage, or time windows change.
WHY WE BUILT THIS
Why we built this
Our team came from technology-ecosystem research for institutional investors. The work involved combining weak or conflicting signals into a defensible view of how software categories and companies were changing.
Language models are good at writing an analysis once they have the right context. The difficult part is supplying structured, current evidence about products, companies, developer activity, adoption, and change over time.
We built ATC to expose that research layer as tools a model can call.
FEEDBACK
What we would like feedback on
We would particularly value feedback on whether the signals and methodology are sufficient to audit the conclusion, which software-market questions are most useful, and whether the MCP tool boundaries expose the right level of detail.
Is the evidence sufficient to audit the Cursor thesis?Are the signal definitions clear?Is absolute or indexed trajectory more useful?Which software category should ATC analyze next?Should raw sanitized tool responses be publishable by default?