Skip to content

AI that fixes bugs and opens tested PRs.

For engineering teams. New issues start Atlantic automatically.

Unlock $50 in free credit

Live demo: no account or credit card required.

7 days of free credit. Your selected plan starts when the period ends or the credit runs out.

Example runReview requested
Fix confirmation email for EU checkout with VAT

QA verdict The change works.

An example run in the Atlantic app window: a ticket becomes a proven pull request, and review is requested.

Example run, ticket LIN-482. The film starts on its outcome, an open pull request with review requested, in the Atlantic app window on the ocean. The window shrinks into the Atlantic app icon, a pointer double clicks the icon and the window opens on the run list, where a new run arrives at the top. The pointer opens that run, and the film plays the run that led to the pull request. On a wide screen a camera moves in close on the ticket, the thesis, the code change, the checkout form and the review; on a phone the window fills the frame and the camera moves in once, at the end. Step one shows the ticket and a support thread about the same problem. In step two three finders read the ticket, the thread and the code without seeing each other's work, and the judge types out one thesis with its reason. Step three confirms the problem by reading the code again at its current head. Step four writes the fix on its own branch in the web-app repository and shows the change line by line. In step five a preview boots, a browser agent enters a VAT ID at checkout and places an order, a confirmation email is sent and the change works. In step six a second model reviews the change and finds one blocker, which is fixed in the first review cycle, and the review ends with no blockers. In step seven the pull request opens with the thesis, the evidence and the QA verdict, the camera moves in on it and pulls back, and the film ends where it began.

Example run, 27 seconds

Trusted by

  • Teamfluencer
  • Lovie
  • a1mobile
  • DSALTA
  • Hardal
  • egaranti
  • Car Studio AI
  • Infrenzy
  • Mithrandir
  • CDR

Connect your repo. Follow the change.

  1. Choose where it works.

    Connect your repositories and issue tracker. New issues start Atlantic's investigation automatically.

    Repository cards on the repositories page of the Atlantic app in an example workspace, among them api and web-app.
    Example workspace
  2. It writes and tests the patch.

    Atlantic writes the change on a branch, tests it in a preview and records the browser run.

    A frame from the QA recording of an example run: a browser agent has typed a test name and an example.com address into a profile form.
    Example workspace
  3. Review the pull request and evidence.

    Read the diff, test verdict and review findings in one place. Unresolved blockers stay visible.

    A pull request on the review page of the Atlantic app: its title, state and branches, and the problem description.
    Example workspace

Connect your tools.

Atlantic reads your tools. Changes go to GitHub.
  • Tickets
  • Support
  • Errors and product data
  • Team chat
  • Writes to GitHub

You control access and merging.

SOC 2 Type II and GDPR at the company level.

  • Repository access

    Atlantic can change only repositories in both your GitHub App install and your own selection.

  • Merge policy

    Atlantic never pushes to your default branch. Auto-merge stays off unless you turn it on for repositories you name.

  • Encrypted secrets

    Secrets are encrypted per organization with AES-256-GCM, injected when a preview boots, and never written to your repository.

Your team controls what ships.

Atlantic investigates issues, writes and tests changes, then opens pull requests. Your team controls merging.

“Atlantic gets the hard part exactly right: AI investigates the issue, writes and tests the fix, then gives engineers the evidence to decide what ships.”

Tugrul YilmazerCTO @ Midas

“As a CTO, I care about AI that can take real engineering work from an issue to a change the team can confidently review. Atlantic’s approach of investigating the problem, validating the fix in a running preview, and bringing the evidence into the pull request is compelling. It keeps engineers in control while giving AI a meaningful role across the software delivery process.”

Dogan AkbulutCo-Founder & CTO, DSALTA

We run Atlantic on our own repositories through the same GitHub App our customers install.

Pay for pull requests, not tokens.

Every plan includes model and compute costs. A credit is used only when Atlantic opens a pull request. Failed and cancelled runs are free.

Annual: 12 months for the price of 10

Plans at a glance
PlanPricePR credits and runs
Soloone user$29per month2 credits/monthUp to 10 runs/month
Starterper workspace$599per month20 credits/month3 concurrent runs
Teamper workspace$1,499per month60 credits/month5 concurrent runs
Scaleper workspace$3,499per month200 credits/month15 concurrent runs
Enterpriseannual contractFrom $60kper yearCustom credit volume

Choose your plan after signup.

Included with Solo through Scalethese plans

  • Browser QA and agent review

Enterprise

Your models, your infrastructure, your contract.

From $60k

per year, annual contract

Contact us
  • Your own model account: Bedrock, Azure, or Vertex
  • On-prem or VPC deployment
  • SSO, SLA, and audit log
  • Custom credit volume

Questions before you start.

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.

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.

Does it work with GitLab or Bitbucket?

Atlantic writes only to GitHub today.

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.

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 models see our code, and do they train on it?

Anthropic Claude and OpenAI GPT models, through Amazon Bedrock. Bedrock does not use prompts or completions to train models, and Atlantic does not train or fine-tune models.

Where is our code processed, and how long is it kept?

Workers and evidence storage run on AWS in us-east-1, on a worker that belongs to your organization alone. Model calls go through Amazon Bedrock, which can use AWS cross-region inference, so a request may be served in another AWS region. Atlantic does not claim EU-only or US-only processing. QA recordings are deleted after 180 days.

What does a failed run cost?

Nothing. Failed and cancelled runs never use a credit.

How do we start?

Book a live run, or install the GitHub App on one repository and unlock up to $50 in free credit for 7 days.

Is Atlantic SOC 2 compliant?

Atlantic holds a SOC 2 Type II attestation and is GDPR compliant at the company level. Visit the trust center.

Bring one ticket.

Start with one repository.