Vexp
Indexes code dependencies locally and provides precise context to AI coding agents, reducing token usage.
≈ 89visits/mo
Established · estimate, read 2026-09-19
- For
- Developers using AI coding agents who want to reduce token usage and costs.
- Price
- Free plan · From $19/mopricing page, read 2026-09-19
- Activity
- Actively maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- CLI
- reduce tokens sent to AI models by mapping code dependencies
- verify agent work is correct before it submits changes
- run coding agents on local machine without uploading code
- #18
Kiro
Converts prompts into executable specifications and implements code with parallel agents that validate correctness.
32.7kActiveFrom $20/user/mo - #25
Devin
Executes software engineering tasks including code migrations, bug fixes, testing, and documentation generation across multiple repositories.
30.6kActiveFrom $20/mo - #26
Remy prompt
Builds websites, designs slides, and generates images through conversational AI.
30.9knot read— - #33
Nous Research
Trains and releases open source language models with infrastructure for distributed training.
33.7knot read— - #38
Replit
Builds and deploys web apps, websites, and agents from natural language descriptions.
278knot readFrom $20/mo - #40
Lovable
Builds production-grade web and mobile applications from natural language descriptions.
198knot readFree plan2023
What is Vexp?
Indexes code dependencies locally and provides precise context to AI coding agents, reducing token usage.
Who is Vexp for?
Developers using AI coding agents who want to reduce token usage and costs.
How much does Vexp cost?
Vexp has a free plan; paid plans start at $19/mo, per its pricing page on 2026-09-19.
Do people use Vexp?
Established: ≈ 89 visits a month · estimate, 2026-09 · 2.9k npm installs a month.
Is Vexp still maintained?
Actively maintained.
What are alternatives to Vexp?
In Developer tools, by use: Kiro, Devin, Remy prompt, Nous Research, Replit, Lovable.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.