Agen
Autonomous AI agents that clone repositories, write code, fix pipelines, and preview changes in the cloud.
≈ 2visits/mo
Emerging · estimate, read 2026-09-19
- For
- Development teams automating code generation and deployment from task to merge-ready pull request
- Price
- Free plan · From $59/mopricing page, read 2026-09-20
- Activity
- Maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- API
- Generate code and fix CI pipeline failures automatically
- Preview frontend backend and infrastructure changes together
- Execute recurring maintenance tasks with budget limits
- #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 - #38
Replit
Builds and deploys web apps, websites, and agents from natural language descriptions.
278knot readFrom $20/mo - #67
Factory
Deploys autonomous agents to plan, build, review and ship code changes across your codebase.
49kMaintained— - #85
Windsurf
Manages fleets of local and cloud coding agents that write code, test, and handle edge cases from a unified editor interface.
26knot readFrom $20/mo - #87
Bolt
Generates websites and applications from natural language descriptions using AI coding agents.
29.3knot readFrom $25/user/mo
What is Agen?
Autonomous AI agents that clone repositories, write code, fix pipelines, and preview changes in the cloud.
Who is Agen for?
Development teams automating code generation and deployment from task to merge-ready pull request
How much does Agen cost?
Agen has a free plan; paid plans start at $59/mo, per its pricing page on 2026-09-20.
Do people use Agen?
Emerging: ≈ 2 visits a month · estimate, 2026-09.
Is Agen still maintained?
Maintained.
What are alternatives to Agen?
In Developer tools, by use: Kiro, Devin, Replit, Factory, Windsurf, Bolt.
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.