Sourcegraph Amp

Name: Sourcegraph Amp
Brand: Sourcegraph Amp
Rating: 4.5 (101 reviews)

Sourcegraph Amp is an agentic coding tool that plans and executes multi-step development tasks across a local codebase via a CLI-first interface with a web companion, including editing files, running builds/tests, and iterating on changes.

Est 2013|Valuation $2.6B|Raised $223.1M|50 Ref Customers

LinkedIn 30K|Website|Web traffic 131K|FTEs 147|HQ San Francisco, California, US

MarketsAI Coding Assistants

01Competitive Landscape

| Aspect | Sourcegraph Amp | GitHub Copilot | Cursor | |--------|------------------|----------------|--------| | Starting Price | Free subscription option; pay-as-you-go with a published minimum credit purchase; enterprise tier available with published usage uplift | Published per-seat pricing available from the vendor for business and enterprise tiers (seat-based) | Free tier available; paid plans exist (official docs emphasize per-active-user billing and model pass-through if choosing direct models) | | Best For | Terminal-first agent workflows; teams wanting explicit governance and pay-per-use economics | Broad IDE integration; predictable per-seat budgeting; strong default enterprise procurement fit | Editor-first, agentic multi-file edits; devs who want integrated VS Code-fork workflow | | Key Strength | Transparent usage billing; strong emphasis on long-running agent tasks; enterprise controls listed (SSO, allowlists, visibility) | Ubiquity; tight IDE integration; clearer procurement pattern | Strong UX for multi-file edits + chat; popular among individual devs/teams | | Key Weakness | Cost can spike at API rates; some quality/formatting complaints; workflow constraints (rules/scoping) | Ongoing industry complaints about shifts toward usage-based/credits and related sticker shock | Pricing/limits can be confusing; still not the same as self-hosted enterprise governance in many orgs | - Direct competitors and their key differentiators - **Copilot:** widely deployed; strong Microsoft/GitHub ecosystem integration; vendor documentation lists per-seat pricing and procurement patterns. - **Cursor:** editor-centric experience and agent workflows; tends to optimize for developer UX. - **Windsurf / Claude Code / Codex:** commonly compete on workflow style (IDE vs terminal), model access, and cost structure. - Pricing comparison: value proposition vs alternatives - Amp’s **pass-through API pricing** can be cheaper for light, sporadic usage, but potentially **more expensive** than “all-you-can-eat-ish” or subsidized subscriptions for heavy daily agent use. - Competitors increasingly also move toward **credits/usage-based** components (e.g., Copilot’s billing changes widely discussed in industry conversations), reducing the predictability advantage of seat-based pricing alone. - Customer testimonials comparing this product to competitors - A community user comparing Amp vs Cursor praised Amp’s ability to make sweeping changes and run compile/test loops, but also criticized product direction changes and indicated they stopped using it. - Market share and adoption trends (cite sources) - No reliable, quantified market share for Amp was found in the sources used. - When customers choose competitors instead (and why) - Choose Copilot/Cursor when: - You want predictable per-seat cost ceilings (or at least simpler budgeting). - You prefer a polished IDE-first experience with strong inline completions. - Choose Amp when: - You want explicit pass-through economics and are willing to manage spend. - You prefer terminal-first, long-running agent workflows with governance knobs.

01Competitive Landscape

Aspect	Sourcegraph Amp	GitHub Copilot	Cursor
Starting Price	Free subscription option; pay-as-you-go with a published minimum credit purchase; enterprise tier available with published usage uplift	Published per-seat pricing available from the vendor for business and enterprise tiers (seat-based)	Free tier available; paid plans exist (official docs emphasize per-active-user billing and model pass-through if choosing direct models)
Best For	Terminal-first agent workflows; teams wanting explicit governance and pay-per-use economics	Broad IDE integration; predictable per-seat budgeting; strong default enterprise procurement fit	Editor-first, agentic multi-file edits; devs who want integrated VS Code-fork workflow
Key Strength	Transparent usage billing; strong emphasis on long-running agent tasks; enterprise controls listed (SSO, allowlists, visibility)	Ubiquity; tight IDE integration; clearer procurement pattern	Strong UX for multi-file edits + chat; popular among individual devs/teams
Key Weakness	Cost can spike at API rates; some quality/formatting complaints; workflow constraints (rules/scoping)	Ongoing industry complaints about shifts toward usage-based/credits and related sticker shock	Pricing/limits can be confusing; still not the same as self-hosted enterprise governance in many orgs

Direct competitors and their key differentiators
- Copilot: widely deployed; strong Microsoft/GitHub ecosystem integration; vendor documentation lists per-seat pricing and procurement patterns.
- Cursor: editor-centric experience and agent workflows; tends to optimize for developer UX.
- Windsurf / Claude Code / Codex: commonly compete on workflow style (IDE vs terminal), model access, and cost structure.
Pricing comparison: value proposition vs alternatives
- Amp’s pass-through API pricing can be cheaper for light, sporadic usage, but potentially more expensive than “all-you-can-eat-ish” or subsidized subscriptions for heavy daily agent use.
- Competitors increasingly also move toward credits/usage-based components (e.g., Copilot’s billing changes widely discussed in industry conversations), reducing the predictability advantage of seat-based pricing alone.
Customer testimonials comparing this product to competitors
- A community user comparing Amp vs Cursor praised Amp’s ability to make sweeping changes and run compile/test loops, but also criticized product direction changes and indicated they stopped using it.
Market share and adoption trends (cite sources)
- No reliable, quantified market share for Amp was found in the sources used.
When customers choose competitors instead (and why)
- Choose Copilot/Cursor when:
  - You want predictable per-seat cost ceilings (or at least simpler budgeting).
  - You prefer a polished IDE-first experience with strong inline completions.
- Choose Amp when:
  - You want explicit pass-through economics and are willing to manage spend.
  - You prefer terminal-first, long-running agent workflows with governance knobs.

Aspect

Sourcegraph Amp

GitHub Copilot

Cursor

Starting Price

Free subscription option; pay-as-you-go with a published minimum credit purchase; enterprise tier available with published usage uplift

Published per-seat pricing available from the vendor for business and enterprise tiers (seat-based)

Free tier available; paid plans exist (official docs emphasize per-active-user billing and model pass-through if choosing direct models)

Best For

Terminal-first agent workflows; teams wanting explicit governance and pay-per-use economics

Broad IDE integration; predictable per-seat budgeting; strong default enterprise procurement fit

Editor-first, agentic multi-file edits; devs who want integrated VS Code-fork workflow

Key Strength

Transparent usage billing; strong emphasis on long-running agent tasks; enterprise controls listed (SSO, allowlists, visibility)

Ubiquity; tight IDE integration; clearer procurement pattern

Strong UX for multi-file edits + chat; popular among individual devs/teams

Key Weakness

Cost can spike at API rates; some quality/formatting complaints; workflow constraints (rules/scoping)

Ongoing industry complaints about shifts toward usage-based/credits and related sticker shock

Pricing/limits can be confusing; still not the same as self-hosted enterprise governance in many orgs