Questions teams ask before they switch.
How is this different from a coding agent like Cursor or Claude Code?
Atlantic starts from the tickets and support threads your team has already filed, and chooses the work itself. It proves the fix before the pull request opens: it boots the branch on a fresh machine, drives a browser through the change, and has a second model review the diff. The pull request opens last, with the thesis, evidence, QA verdict and video, and reviewers are requested.
Can Atlantic merge on its own?
Only if you turn on auto-merge for repositories you name. It is off by default, and Atlantic never pushes to your default branch.
Which repositories can it touch?
Atlantic can change only repositories in both your GitHub App install and your own selection. A run can include up to 5 repositories.
How does Atlantic decide what to work on?
Three finders read your backlog, support desk and repository in parallel. A judge links their findings into one problem and writes a thesis, about a minute after a ticket is filed.
How do I know the change actually works?
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. A second model reviews the diff. Blockers go back through up to 2 fix cycles.
Will it flood us with pull requests?
It opens one pull request per validated problem, only after browser QA and an agent review, and every diff is checked against a 2,500 changed-line budget by default. Concurrent runs are capped by plan.
How is it billed?
You pay per pull request, not per token: model tokens and preview compute are included. Solo is $29 a month with 2 PR credits, Team $1,499 with 60, Scale $3,499 with 200. Annual billing is paid upfront at 12 months for the price of 10. A credit is used only when Atlantic opens a pull request. Extra credits cost $19 each. Failed and cancelled runs are free. Enterprise starts at $60k a year.
What does Atlantic need to run our app?
It boots your branch on a fresh machine from a factory.deploy.yml file that describes how to build and start your stack.
What happens to secrets and previews?
Secrets are encrypted per organization with AES-256-GCM, injected when a preview boots, and never written to your repository. Previews stop after 6 hours idle. Previews expire within 7 days. Previews are destroyed when the pull request closes.