NewAtlantic raises from Galata Business Angels at a $5M valuation
SECURITY

Factory works inside a boundary you set.

GitHub decides which repositories Factory may touch. It opens pull requests and leaves merging to you. Secrets stay encrypted per organization, injected at preview boot, and previews tear down when the pull request closes.

Sign up freeStart with $50 free for 7 days

You choose the repos, Factory never crosses that line.

The repository set Factory may touch is the intersection of your GitHub App install and your own selection. Secrets stay in a per-organization encrypted store, injected at preview boot, never in the repo. SOC 2 Type II compliant, GDPR compliant.

Repository scope

Factory may change only repos in the intersection of your GitHub App install and your own selection.

You choose the set

Pull requests only

Factory opens pull requests. It never merges and never pushes to a default branch.

Human merges every time

Encrypted secrets

Secrets live in a per-organization encrypted store, injected into the preview at boot, never in the repo.

Never in your repo

Preview teardown

Previews idle-stop after 6 hours, carry a 7-day TTL, and are destroyed when the pull request closes.

7-day TTL max
ComplianceSOC 2 Type IIGDPR
app.factory.getatlantic.ai / runs, every run scoped to the repositories you chose PREVIEW
Atlantic Factory run detail for a succeeded run, showing the problem, fix and result summary, the working repository scope, and a pull request panel with QA verdict
Realness gate

Every run records each provider as real or fixture. A run flagged real refuses fixture providers.

Call ledger

Every external call a run made is listed with its source, status, and time.

Guardrail on every diff

Each diff is checked before push: a 2,500 changed-line budget, binary rejection, repo-mismatch check.

Audited, not self-certified

Atlantic AI Inc. holds a SOC 2 Type II attestation and GDPR compliance, checked at the company level.

Data handling

Where your code goes.

Five questions security teams ask first, answered plainly.

Where is my code processed?

On AWS, on a worker that belongs to your organization alone.

  • Your organization gets its own preview worker. It is never shared with another organization, and each run gets an isolated segment on it under rootless Docker.
  • Tests and checks run in containers with networking turned off. Dependency install and build steps can reach package registries.
  • Factory's workers and evidence storage are configured in AWS us-east-1. Model calls go through Amazon Bedrock, which can use AWS cross-region inference, so a request may be served in another AWS region. We do not claim EU-only or US-only processing.

Which models see it?

Anthropic Claude and OpenAI GPT models, served through Amazon Bedrock.

  • Claude handles most stages. Some stages of the Low, High, and Max tiers use OpenAI GPT models, also served by Bedrock. You choose a tier, never a model.
  • A run sends a model the ticket and the repository content it reads to investigate, fix, and review the change.
  • On a bring-your-own-key plan, model calls go directly to Anthropic or OpenAI under your own account and its terms, not through Atlantic's Bedrock.

Is it used for training?

No. Amazon Bedrock does not train on prompts or completions.

  • AWS documents that Bedrock does not use your prompts and completions to train models and does not distribute them to third parties, including the model providers.
  • Atlantic calls hosted models. It does not train or fine-tune any.

Is it stored, and for how long?

Briefly on the worker, longer as run history you can audit.

  • The checkout is deleted when the preview is torn down: when its pull request closes or the run ends. Idle previews stop after 6 hours, and none lives past 7 days.
  • Run history (the ticket, the files Factory changed, command output, and the call ledger) stays in Atlantic's database so you can audit every run.
  • QA screenshots and browser recordings sit in Amazon S3 behind unlisted links, and are deleted after 180 days. Anyone holding a link can open it until then.
  • Environment secrets are encrypted at rest with AES-256-GCM and are write-only in the app.

Who can access it?

Only repositories you install and select, and only people in your organization.

  • Factory reaches code through the GitHub App you install, limited to repositories you both install it on and select.
  • Factory opens pull requests. It merges only for an organization that turns on auto-merge for repositories it names.
  • Runs are visible to members of your organization in the Factory app.

Read AWS's Amazon Bedrock data protection policy, our sub-processors, and our DPA.

04 / Posture

What we're explicit about.

Affirmative guarantees only. No vendor weasel words.

Locked to repos you choose

Only repos in both your GitHub App install and your own selection are ever in scope.

Intersection, not union

Secret-shaped values get blocked

The deploy contract validator blocks secret-shaped literals from a preview's declared environment values.

Validated before boot

Realness checked, not assumed

Each surface in a run is checked against its provider. A run flagged real never falls back to a fixture.

No silent fallback

Merging stays yours

Factory opens pull requests. Auto-merge is off unless you turn it on for repositories you name. Merge and approve stay GitHub-native: comment, approve, request changes, then merge commit, squash, or rebase.

Auto-merge off by default

SOC 2 Type II compliant

Atlantic AI Inc. is SOC 2 Type II and GDPR compliant at the company level.

Audited 2026

Previews don't linger

Idle previews stop after 6 hours. Every preview carries a 7-day TTL and dies when its pull request closes.

7-day TTL max