Atlantic
Atlantic reads your backlog, support desk and repository, picks one problem, writes the fix, tests it in a browser, has a second model review the diff and opens the pull request.
- From tickets to pull requests
- Evidence on the pull request
Atlantic vs Factory (factory.com)
Where the work starts and how it is proven.
Factory (factory.com) sells Droid agents you work with, delegate to, or start from automations. Atlantic picks a problem from your tickets and support desk, tests the change in a browser and opens a pull request.
- Browser test on video
- Second-model review
- Auto-merge is off by default
Same repository. A different finish line.
Both start from your repository and end in a pull request. The differences are what starts the work, where the change is tested, and how you pay.
Factory (factory.com)
Factory (factory.com) sells Droid agents for coding, code review, QA and security review. Work starts when someone delegates an issue or message, or when an automation fires on a schedule, a Slack message or a GitHub event.
- Delegate or automate
- Review on the pull request
| Feature | Atlantic | Factory (factory.com) |
|---|---|---|
| How work starts | Three finders read your backlog, support desk and repository, each working blind. A judge picks one problem. | A person delegates an issue or message, or an automation fires on a schedule, a Slack message or a GitHub event. Ticket to PR picks up ready Linear or Jira tickets. |
| Browser testing | Before the pull request opens, a browser agent drives the change for up to 40 steps on a fresh preview machine, recorded on video. | Automated QA drives a real browser on pull requests and posts a report with screenshots. The Droid Control plugin can record demo videos on request. |
| Review of the change | A second model reviews the diff. Blockers go back for up to 2 fix cycles before the pull request opens. | Automated Code Review posts inline comments on GitHub pull requests and GitLab merge requests. The /review command checks local changes before you push. |
| Record of tool and external calls | Every external call a run makes is logged with source, status and time. Each provider is marked live or mocked. | Tool call counts and durations are exported as OpenTelemetry data to your own collector. |
| How you pay | A credit is used only when Atlantic opens a pull request. Failed and cancelled runs are free. | Monthly plans for individuals and teams, with per-seat pricing on Teams. You can buy extra usage past your limit. Business and Enterprise plans are custom. |
| Source control and hosting | Writes only to GitHub today. Atlantic's workers and evidence storage run on AWS in us-east-1. | Code review works with GitHub and GitLab repositories. Deployment can be managed by the vendor, in your VPC, on premises or air-gapped. |
How work starts
- Atlantic
- Three finders read your backlog, support desk and repository, each working blind. A judge picks one problem.
- Factory (factory.com)
- A person delegates an issue or message, or an automation fires on a schedule, a Slack message or a GitHub event. Ticket to PR picks up ready Linear or Jira tickets.
Browser testing
- Atlantic
- Before the pull request opens, a browser agent drives the change for up to 40 steps on a fresh preview machine, recorded on video.
- Factory (factory.com)
- Automated QA drives a real browser on pull requests and posts a report with screenshots. The Droid Control plugin can record demo videos on request.
Review of the change
- Atlantic
- A second model reviews the diff. Blockers go back for up to 2 fix cycles before the pull request opens.
- Factory (factory.com)
- Automated Code Review posts inline comments on GitHub pull requests and GitLab merge requests. The /review command checks local changes before you push.
Record of tool and external calls
- Atlantic
- Every external call a run makes is logged with source, status and time. Each provider is marked live or mocked.
- Factory (factory.com)
- Tool call counts and durations are exported as OpenTelemetry data to your own collector.
How you pay
- Atlantic
- A credit is used only when Atlantic opens a pull request. Failed and cancelled runs are free.
- Factory (factory.com)
- Monthly plans for individuals and teams, with per-seat pricing on Teams. You can buy extra usage past your limit. Business and Enterprise plans are custom.
Source control and hosting
- Atlantic
- Writes only to GitHub today. Atlantic's workers and evidence storage run on AWS in us-east-1.
- Factory (factory.com)
- Code review works with GitHub and GitLab repositories. Deployment can be managed by the vendor, in your VPC, on premises or air-gapped.
What this page says about Factory (factory.com) summarizes the vendor's own public pages, and the table links the page behind every row. If something is out of date, email hello@getatlantic.ai.
When to choose Factory (factory.com) vs Atlantic
Choose Atlantic
- You want Atlantic to pick the problem from your tickets, support desk and repository.
- You want the change tested in a browser, on video, before the pull request opens.
- You want a second model to review the diff before the pull request opens.
Choose Factory (factory.com)
- You want agents in your terminal, desktop app or IDE, and a way to delegate from Slack, Jira or Linear.
- You need to run on premises or air-gapped, or you use GitLab.
- You want to pick your own models or bring your own keys.
Try it on your repo
- Writes only to GitHub
- Auto-merge is off by default
Browser test
The change is tested before you review it.
Atlantic boots the branch on a fresh, isolated preview machine and checks its health. A browser agent drives the change for up to 40 steps, recorded on video.
- Up to 40 browser steps
- Video attached
Where work comes from
Your existing tools become the work queue.
Atlantic watches the backlog (Linear, Jira, GitHub Issues), the support desk (HubSpot today) and the repository. Slack, Sentry and PostHog add evidence.
See integrations
Review
Atlantic opens the pull request. Your team reviews it.
A second model reviews the diff. Blockers go back through up to 2 fix cycles. Atlantic never pushes to your default branch. Auto-merge stays off unless you turn it on for repositories you name.
- Up to 2 fix cycles
- Auto-merge is off by default
Questions teams ask before choosing Atlantic
No. Atlantic and Factory (factory.com) are separate products. Factory (factory.com) sells Droid agents you work with, delegate to, or start from automations. Atlantic picks a problem from your tickets and support desk, tests the change in a browser and opens a pull request for your team to review.
Three finders read the backlog, the support desk and the repository in parallel, each working blind. A judge links what they found, picks one problem and writes a thesis.
The pull request opens last, with the thesis, evidence, QA verdict and video, and reviewers are requested. Atlantic never pushes to your default branch. Auto-merge stays off unless you turn it on for repositories you name.
No. Atlantic can change only repositories in both your GitHub App install and your own selection. A run can include up to 5 repositories.
Atlantic is priced in pull request credits. Solo is $29 a month for one user and includes 2 credits. Team is $1,499 a month per workspace and includes 60 credits. Scale is $3,499 a month per workspace and includes 200 credits. Enterprise is from $60k a year. A credit is used only when Atlantic opens a pull request. Failed and cancelled runs are free. Extra credits cost $19 each.
Review a pull request instead of chasing a bug.
Atlantic picks the problem from your backlog, support desk and repository, tests the fix in a real browser and opens a pull request for your team to review.