Acyclic
Splits a coding task across parallel coding agents, each in its own sandbox, then merges their work into one patch or pull request.
41 linking domains
Emerging
- Price
- Price not read
- Activity
- Activity not read yet
- Company
- Domain since 2025domain registered
- Runs as
- CLI
- Used for
- split a coding task across parallel agents in sandboxes
- merge parallel agent results into one patch
- open a pull request from merged swarm results
- Domain since2025domain registered
- MCP docsacyclic.dev/guides/mcpthe vendor's page ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1
Cursor
AI coding agent that writes code, runs tasks, and reviews pull requests autonomously or with human direction.
314kActiveFrom $20/user/mo2023 - #2
Replit
Builds and deploys web apps, websites, and agents from natural language descriptions.
278kActiveFrom $20/mo - #3
OneUptime
Monitors infrastructure and applications, detects incidents in seconds, pages on-call engineers, and opens fix pull requests.
221kActiveFrom $22/mo2020 - #4
Warp
Runs fleets of coding agents across software development workflows defined in code.
162kActiveFrom $20/mo - #5
Augment Code
Orchestrates software development agents across the full lifecycle from tickets to deployment and monitoring.
144kActiveFrom $20/mo - #6
AirtableMCP · sign-in
Builds custom business applications and deploys AI agents across workflows without coding.
142kActiveFrom $20/user/mo2012
What is Acyclic?
Splits a coding task across parallel coding agents, each in its own sandbox, then merges their work into one patch or pull request. It is listed in the Atlas under Developer tools.
Do people use Acyclic?
Emerging.
What are alternatives to Acyclic?
In Developer tools, by use: Cursor, Replit, OneUptime, Warp, Augment Code, Airtable.
Not quite it? Describe the job
betaFive tools from the Atlas that fit it, each judged against what you wrote.
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 tool 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.