New: architecture gate for pull requests

ArcobayClient-ready architecture
from your codebase.

Arcobay turns your codebase into client-ready architecture documentation.

Living diagrams, decision records, walkthrough video, and a shareable handoff portal that stays up to date when you push code.

Sign in with Google, GitHub, or GitLab to create your Arcobay account and connect a repository.

Connect repositoryTry with a prompt
Samplerepo
Ship handoff
Samplerepo architectureNext.js on Vercel with Supabase data/auth, Inngest workers for repo scans and exports, Claude for AI, and Paddle billing.CLIENTFRONTENDOBSERVABILITYBACKENDINTEGRATIONSAUTHASYNC & WORKERSDATACODE HOSTSEnd UserUses the web appl…Next.js AppWeb appVercelApplication hosti…SentryError monitoring and a…PostHogProduct analytics and …UptimeRobotUptime monitoringNext.js API RoutesWeb appWebhooksPush and merge events …Anthropic Claude APILLM for diagrams, Q&A,…PaddleSubscription billing a…ResendTransactional email de…Supabase AuthEmail, OAuth, and se…InngestBackground jobs, ret…Background WorkersRepo scans, diagram …Diagram RendererDeterministic JSON-t…PlaywrightHeadless capture for…FFmpegVideo encoding for d…Supabase PostgreSQLPrimary relational da…Upstash RedisRate limiting, cachin…Supabase StorageExported diagrams, vi…pgvectorSemantic search exten…Supabase RealtimeLive notifications an…GitHubRepository contents a…usesAPI callsAuthenticatesReads / writesEnqueues jobsStores exportsLLM analysisCreates checkoutPush eventsReports errorsmanages users

Features

Architecture documentation that stays accurate — and client-ready.

Living diagrams, architecture decision records, walkthrough video, and a shareable handoff portal — generated from your codebase and updated on every push.

Client handoff portal

Share one branded link with your architecture diagram, decision records, changelog, and walkthrough video — a client-ready package that stays current when you ship.

Self-updating architecture diagrams

Connect GitHub, GitLab, or Bitbucket and regenerate living architecture diagrams on every push — so docs never drift from the codebase.

Architecture decision records

Capture the why behind each choice and attach it to the component on the diagram — searchable ADRs grounded in your real system.

Presentation video exports

Export animated architecture walkthroughs for stakeholders, investors, and clients — without recording a screen share.

Prompt-based diagram generation

Describe your system in plain language and get an architecture diagram instantly — no repository access required to start.

Plain-language architecture Q&A

Ask why a service talks to Redis and get answers grounded in your actual codebase — not generic documentation.

Team plan

PR architecture gate for pull requests.

Catch dependency, integration, and env-var changes before they merge — with living diagram diffs and architecture decision coverage that only clears in Arcobay.

Comment on the PR — merge stays open

Team plan · webhook only. Arcobay posts structural changes and missing decision notes. No GitHub Action required.

Pull request · comment
feat: add Redis rate limiting#482
Arcobay Architecture GateWarning

This PR introduces a structural change that should have an architecture decision note in Arcobay.

Missing decision coverage

dependency in package.json — Redis added for rate limiting

Add decision on Redis →

Before · base

API→Postgres

After · this PR

API→Redis→Postgres
+ Redis
Get started freeView Action on GitHub

Why Arcobay exists

Architecture docs that rot vs living institutional memory.

Most teams still draw diagrams by hand, park decisions elsewhere, and hope the handoff stays accurate. Arcobay keeps architecture, decisions, and client-ready delivery in one place — synced to your codebase.

The status quo breaks down

Architecture documentation that can't keep up with the code.

What goes wrong

  • Architecture diagrams that go stale the week after you draw them
  • No way to sketch the system before the code exists
  • The why lives in Notion or Slack — never on the diagram
  • Drift and undocumented changes slip into production unnoticed
  • New hires and clients get a README, not institutional memory

Arcobay keeps it accurate

Living diagrams, decisions, and handoffs from your codebase.

What Arcobay delivers

  • Living architecture diagrams regenerated from your repo on every push
  • Prompt-first diagrams before code exists — then merge with the codebase
  • Architecture decision records attached directly to diagram components
  • Drift alerts and a PR architecture gate for missing decision coverage
  • Client handoff portal, grounded Q&A, and onboarding tour in one place
See full competitor comparison

Named rival breakdowns live on the compare page

How it works

Two ways to get started.

Connect when you're ready for living docs, or prompt when you want value in seconds.

Connect a repository

Link GitHub, GitLab, or Bitbucket. Arcobay scans your codebase and builds a living architecture diagram that updates as you ship.

  1. 1Grant read access
  2. 2Select repositories
  3. 3Get your first diagram
Connect your repo

Start with a prompt

Describe your system in plain language first. Arcobay builds a living architecture diagram you can refine with follow-up prompts.

  1. 1Describe your system
  2. 2Generate a diagram
  3. 3Refine and export
Try a prompt

Who it's for

Built for people who must explain systems to humans.

Arcobay is for the moment a README is not enough — freelancers, agencies, and small teams who need living architecture documentation others can actually understand.

Freelance developers

Client-ready architecture handoffs without the slide deck

When a README is not enough, share one branded link so the client can see the diagram, decisions, and walkthrough — without a day of slides and screen recording.

  • One handoff link instead of a slide deck
  • Diagram + decisions + video together
  • Looks finished the day you ship
Freelance developer reviewing a living architecture diagram with a client during project handoff

Dev agencies

Branded architecture portals your clients can keep

Ship a white-label client handoff portal alongside the code — living architecture documentation, decision records, and walkthrough video under your brand.

  • Branded portal next to the deliverable
  • Agency-ready packaging for every client
  • Docs that stay current after launch
Agency deliverable set with architecture diagram, decision blueprint, and walkthrough video for a branded client portal

Founders and small teams

Living architecture for investors and new hires

Give stakeholders an architecture view that updates when you push — instead of a diagram that rots after a sprint. Onboarding and investor clarity from the same living docs.

  • Investor-ready system view on demand
  • New-hire onboarding from real architecture
  • Stays accurate as the product ships
Founders and teammates reviewing a living architecture map together for investors and new hires

FAQ

Architecture documentation questions, answered.

How Arcobay works for living diagrams, client handoffs, PR architecture gate, and security — before you connect a repo or start a prompt.

Arcobay is an architecture documentation tool that turns your codebase into living diagrams, architecture decision records, walkthrough video, and a shareable client handoff portal that updates when you push code.

Still comparing tools? See the full competitor comparison · View pricing

Get started

Ready for living architecture docs you can actually ship?

Connect a repository or start with a prompt. Arcobay builds a useful architecture diagram in your first session — then packages decisions, walkthrough video, and a client handoff portal that updates when you push code.

Get started freeTry with a prompt

Free to start · No credit card · First diagram in one session