See your codebase in the dark.
OwlMap reads your repository and writes the architecture overview, flow diagrams, module notes and onboarding guide your team never had time to write.
Free during the beta. Public GitHub repositories first.
routes → SessionsController#create → User.authenticate → AuthService → SessionStore
Four documents, written from your code
Each one answers a question a new teammate would otherwise ask in chat. This sample is from a small Rails app.
Architecture overview
The big picture: main components, how data moves between them, and the outside services they depend on.
A monolithic Rails app with three areas: accounts, billing and notifications.
- Requests enter through
config/routes.rband are handled by controllers underapp/controllers. - Business rules live in
app/services, not in models. - Background work runs on Sidekiq:
MailerJob,InvoiceJob. - External services: Stripe (payments), SendGrid (email), S3 (uploads).
Key flows
Step-by-step traces of the paths that matter most, with a diagram you can paste into any Markdown viewer.
Signing in
Failed attempts are counted in Redis; after five, the account is locked for 15 minutes.
lib/billing
One note per module: its job, what it depends on, and what to be careful with.
Creates invoices at the end of each billing period and retries failed charges.
Depends on Stripe, Invoice, InvoiceJob.
Careful: tax rates are hard-coded in two places. Change both together.
Onboarding guide
A first-day reading order and the questions newcomers usually ask.
- Read
app/services/auth_service.rbfirst. Most features pass through it. - Run locally:
bin/setup, thenbin/dev. - Where are emails defined? In app/mailers, sent from MailerJob.
How it works
Paste a repository link
Any public GitHub repository up to about 500 source files during the beta.
OwlMap reads the code
Claude summarises each module, then pieces together the architecture and main flows. Usually a few minutes.
Read or download the docs
Browse them in OwlMap, or download Markdown files to commit next to your code.
Made for teams that inherit code
- Tech leads onboarding new developersGive newcomers a map on day one instead of a week of questions.
- Agencies taking over a projectUnderstand a handed-over codebase before quoting the work.
- Offshore teamsShare one picture of the system across languages and time zones.
Your code stays yours
- Public repositories only in the betaPrivate repository support will come with explicit, per-repository permission.
- Deleted after processingThe cloned code is removed once your documents are written.
- Not used for trainingOwlMap uses the Claude API under Anthropic's commercial terms.
Map your first repository
We're inviting a small group of developers to try OwlMap and tell us what's missing. Leave your email and we'll send an invite.