The merge gate

Coding is solved.
Software isn't.

AI writes code faster than humans can review it. Memor sits on every PR and posts one deterministic comment. Same diff in, same verdict out. No LLM at runtime.

M
Memor @memor · just nowReporter
High risk: merging this can destroy the payments-db RDS instance
blocker

infra/rds.tf: resource renamed without a moved block; Terraform destroys and recreates payments-db on apply

blocker

src/routes/billing.ts: POST /billing removed; 3 repos call this endpoint

warning

src/middleware/auth.ts: jwt_secret hardcoded as literal string; was read from env

3 findings · 8 files analyzed · full coverage
Edited just now by Memor

Detects

💥Blast radius
🔗Downstream breakage
🤖Hallucinated APIs
⚠️Risky patterns
Deterministic

Same diff in, same verdict out. Every claim is derivable. Grep the source, verify the output. No probabilistic components at runtime.

Quiet by design

Three lines max per PR. Clean PR gets one line: all clear. Memor is tuned to earn silence, not fill it.

Private by architecture

Stateless. Self-hostable. No third-party calls. Source code exists only for analysis and is deleted immediately.

Security posture

  • No source stored. Code is fetched, analyzed in memory, and deleted.
  • No third-party calls. Analysis runs entirely on your infrastructure.
  • No LLM at runtime. Every verdict is deterministic and reproducible.
  • Minimum-scope tokens. Read repository + write PR comments only.
  • Self-hosted available. Single Docker container inside your network.

Early access

Piloting with a small number of GitLab and GitHub teams. One repo, fifteen minutes.

hey@memor.dev

Install is one webhook. Two weeks, nothing useful caught, remove it and tell us why.