ATC

ATC SOFTWARE MARKET INTELLIGENCE

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.
View tool traceView report PDF

Developer usage - the divergence

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.

1,00010,000Jun 24Nov 24Apr 25Sep 25Feb 26May 26Claude Code enters the measured setClaude Code crosses CursorCursor, Jun 24: 1,943Cursor, Jul 24: 2,000Cursor, Aug 24: 2,200Cursor, Sep 24: 2,500Cursor, Oct 24: 2,650Cursor, Nov 24: 2,800Cursor, Dec 24: 2,950Cursor, Jan 25: 3,100Cursor, Feb 25: 3,300Cursor, Mar 25: 3,450Cursor, Apr 25: 3,500Cursor, May 25: 3,600Cursor, Jun 25: 3,700Cursor, Jul 25: 3,780Cursor, Aug 25: 3,820Cursor, Sep 25: 3,880Cursor, Oct 25: 3,920Cursor, Nov 25: 3,970Cursor, Dec 25: 4,010Cursor, Jan 26: 4,050Cursor, Feb 26: 4,080Cursor, Mar 26: 4,100Cursor, Apr 26: 4,110Cursor, May 26: 4,118CursorClaude Code, Feb 25: 350Claude Code, Mar 25: 650Claude Code, Apr 25: 920Claude Code, May 25: 1,350Claude Code, Jun 25: 2,050Claude Code, Jul 25: 2,800Claude Code, Aug 25: 3,400Claude Code, Sep 25: 3,900Claude Code, Oct 25: 5,000Claude Code, Nov 25: 6,200Claude Code, Dec 25: 7,300Claude Code, Jan 26: 8,200Claude Code, Feb 26: 9,000Claude Code, Mar 26: 9,700Claude Code, Apr 26: 10,200Claude Code, May 26: 11,021Claude CodeGitHub Copilot, Jun 24: 780GitHub Copilot, Jul 24: 810GitHub Copilot, Aug 24: 850GitHub Copilot, Sep 24: 890GitHub Copilot, Oct 24: 910GitHub Copilot, Nov 24: 940GitHub Copilot, Dec 24: 960GitHub Copilot, Jan 25: 980GitHub Copilot, Feb 25: 995GitHub Copilot, Mar 25: 1,010GitHub Copilot, Apr 25: 1,025GitHub Copilot, May 25: 1,040GitHub Copilot, Jun 25: 1,060GitHub Copilot, Jul 25: 1,075GitHub Copilot, Aug 25: 1,090GitHub Copilot, Sep 25: 1,120GitHub Copilot, Oct 25: 1,140GitHub Copilot, Nov 25: 1,160GitHub Copilot, Dec 25: 1,180GitHub Copilot, Jan 26: 1,200GitHub Copilot, Feb 26: 1,220GitHub Copilot, Mar 26: 1,235GitHub Copilot, Apr 26: 1,248GitHub Copilot, May 26: 1,260GitHub CopilotWindsurf, Jun 24: 520Windsurf, Jul 24: 540Windsurf, Aug 24: 570Windsurf, Sep 24: 610Windsurf, Oct 24: 650Windsurf, Nov 24: 700Windsurf, Dec 24: 760Windsurf, Jan 25: 820Windsurf, Feb 25: 850Windsurf, Mar 25: 875Windsurf, Apr 25: 900Windsurf, May 25: 930Windsurf, Jun 25: 960Windsurf, Jul 25: 980Windsurf, Aug 25: 1,020Windsurf, Sep 25: 1,050Windsurf, Oct 25: 1,080Windsurf, Nov 25: 1,100Windsurf, Dec 25: 1,125Windsurf, Jan 26: 1,140Windsurf, Feb 26: 1,155Windsurf, Mar 26: 1,170Windsurf, Apr 26: 1,184Windsurf, May 26: 1,190Windsurf

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.

Source and methodology
View underlying data table
Developer usage - the divergence underlying data
MonthCursorClaude CodeGitHub CopilotWindsurf
Jun 241,943missing780520
Jul 242,000missing810540
Aug 242,200missing850570
Sep 242,500missing890610
Oct 242,650missing910650
Nov 242,800missing940700
Dec 242,950missing960760
Jan 253,100missing980820
Feb 253,300350995850
Mar 253,4506501,010875
Apr 253,5009201,025900
May 253,6001,3501,040930
Jun 253,7002,0501,060960
Jul 253,7802,8001,075980
Aug 253,8203,4001,0901,020
Sep 253,8803,9001,1201,050
Oct 253,9205,0001,1401,080
Nov 253,9706,2001,1601,100
Dec 254,0107,3001,1801,125
Jan 264,0508,2001,2001,140
Feb 264,0809,0001,2201,155
Mar 264,1009,7001,2351,170
Apr 264,11010,2001,2481,184
May 264,11811,0211,2601,190

THE VERDICT

Not overhyped, out-accelerated.

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.

101001,000Jun 24Nov 24Apr 25Sep 25Feb 26May 26Enterprise signal inflectionCursor, Sep 24: 18Cursor, Oct 24: 20Cursor, Dec 24: 32Cursor, Jan 25: 48Cursor, Feb 25: 72Cursor, Mar 25: 96Cursor, Apr 25: 118Cursor, May 25: 150Cursor, Jun 25: 175Cursor, Jul 25: 205Cursor, Aug 25: 230Cursor, Sep 25: 250Cursor, Oct 25: 240Cursor, Nov 25: 260Cursor, Dec 25: 278Cursor, Jan 26: 291Cursor, Feb 26: 390Cursor, Mar 26: 520Cursor, Apr 26: 650Cursor, May 26: 780CursorClaude Code, Feb 25: 10Claude Code, Mar 25: 25Claude Code, Apr 25: 50Claude Code, May 25: 85Claude Code, Jun 25: 140Claude Code, Jul 25: 190Claude Code, Aug 25: 240Claude Code, Sep 25: 280Claude Code, Oct 25: 310Claude Code, Nov 25: 305Claude Code, Dec 25: 315Claude Code, Jan 26: 318Claude Code, Feb 26: 520Claude Code, Mar 26: 760Claude Code, Apr 26: 840Claude Code, May 26: 980Claude CodeGitHub Copilot, Jun 24: 58GitHub Copilot, Jul 24: 75GitHub Copilot, Aug 24: 82GitHub Copilot, Sep 24: 70GitHub Copilot, Oct 24: 78GitHub Copilot, Nov 24: 81GitHub Copilot, Dec 24: 72GitHub Copilot, Jan 25: 95GitHub Copilot, Feb 25: 120GitHub Copilot, Mar 25: 145GitHub Copilot, Apr 25: 160GitHub Copilot, May 25: 180GitHub Copilot, Jun 25: 290GitHub Copilot, Jul 25: 340GitHub Copilot, Aug 25: 380GitHub Copilot, Sep 25: 430GitHub Copilot, Oct 25: 470GitHub Copilot, Nov 25: 495GitHub Copilot, Dec 25: 515GitHub Copilot, Jan 26: 522GitHub Copilot, Feb 26: 610GitHub Copilot, Mar 26: 820GitHub Copilot, Apr 26: 780GitHub Copilot, May 26: 900GitHub CopilotWindsurf, Sep 24: 4Windsurf, Oct 24: 5Windsurf, Nov 24: 5Windsurf, Dec 24: 6Windsurf, Jan 25: 8Windsurf, Feb 25: 10Windsurf, Mar 25: 11Windsurf, Apr 25: 14Windsurf, May 25: 15Windsurf, Jun 25: 18Windsurf, Jul 25: 21Windsurf, Aug 25: 18Windsurf, Sep 25: 22Windsurf, Oct 25: 13Windsurf, Nov 25: 20Windsurf, Dec 25: 15Windsurf, Jan 26: 17Windsurf, Feb 26: 24Windsurf, Mar 26: 26Windsurf, Apr 26: 18Windsurf, May 26: 12Windsurf

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.

Source and methodology
View underlying data table
Enterprise-adoption activity underlying data
MonthCursorClaude CodeGitHub CopilotWindsurf
Jun 240missing58missing
Jul 240missing75missing
Aug 240missing82missing
Sep 2418missing704
Oct 2420missing785
Nov 240missing815
Dec 2432missing726
Jan 2548missing958
Feb 25721012010
Mar 25962514511
Apr 251185016014
May 251508518015
Jun 2517514029018
Jul 2520519034021
Aug 2523024038018
Sep 2525028043022
Oct 2524031047013
Nov 2526030549520
Dec 2527831551515
Jan 2629131852217
Feb 2639052061024
Mar 2652076082026
Apr 2665084078018
May 2678098090012

POSITION

Reach versus momentum

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
Productcumulative companies with enterprise-adoption signals
GitHub Copilot2,820
Claude Code2,379
Cursor2,025
Windsurf92

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
Productcumulative developer-activity signal
Claude Code11,021
Cursor4,118
Windsurf1,250
GitHub Copilot1,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.
01Product momentum analysisanalyze_product_momentum
1840 ms1 creditRaw response hidden

Returned comparative momentum scores, monthly trajectories, product rankings, and reach-versus-momentum inputs.

Sanitized arguments
{
  "products": [
    "cursor",
    "claude-code",
    "github-copilot",
    "windsurf"
  ],
  "category": "ai-coding-tools",
  "start_month": "2024-06",
  "end_month": "2026-05",
  "metrics": [
    "developer_activity",
    "enterprise_adoption_activity",
    "product_discussion",
    "company_breadth"
  ]
}
02Developer voice evidenceget_product_comment_evidence
1260 ms1 creditRaw response hidden

Grouped 646 public developer comments into approved themes without publishing direct quotations.

Sanitized arguments
{
  "products": [
    "cursor",
    "claude-code",
    "github-copilot",
    "windsurf"
  ],
  "window": "trailing_12_months",
  "sources": [
    "hacker_news",
    "reddit"
  ],
  "include_direct_quotes": false
}
03Company evidence sampleget_product_usage_evidence
970 ms1 creditRaw response hidden

Returned approved company evidence records with public summaries and source categories.

Sanitized arguments
{
  "product": "cursor",
  "window": "recent",
  "limit": 12,
  "public_fields_only": true
}
04Product relationship contextget_product_relationships
840 ms1 creditRaw response hidden

Returned relationship context used by the model to frame substitution and disintermediation risk.

Sanitized arguments
{
  "product": "cursor",
  "related_products": [
    "claude-code",
    "github-copilot",
    "windsurf"
  ],
  "relationship_types": [
    "substitution",
    "complement",
    "competitive_overlap"
  ]
}

Redactions applied

  • 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

  1. Open Claude and go to Customize, then Connectors.
  2. Add a custom connector.
  3. Paste the ATC MCP URL.
  4. Authenticate with ATC.
  5. Enable ATC in a conversation and paste a software-market prompt.
Complete Claude instructions

ChatGPT

ChatGPT custom connector availability depends on account and workspace settings. See the MCP docs for the current setup path.

ChatGPT connector notes

SECURITY, PRICING, LIMITS

Read-only, inexpensive to evaluate, and bounded

SECURITY

Read-only and scoped by design

  • OAuth authentication
  • Scoped ATC resources
  • Read-only connector
  • 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?