Gitrailway reads the repo and draws one line through it: the files a senior dev would show you, in order, with a note at each stop and a marker that says you are here.
No accounts · No waitlist · Open source — when it ships.
The knowledge lives with a senior dev, or in a README that went stale three years ago. Gitrailway reads the repo itself and draws one line through it.
Entrypoints first, core next, corners last. The line follows how the code is actually used, not the folder tree.
Each station explains what the file does and why it matters, short enough to read before you open it.
Every step carries a marker: done, here, next. The map updates as you move. No getting lost in a 40-file repo.
Three beats per repo. Nothing to configure, nothing to install in your project.
Point Gitrailway at any repo, local or public. No config file, no setup step.
Gitrailway reads structure, history and tests, then orders the files the way a maintainer would show them.
Each stop explains one file. Mark it done and the line continues. Get lost, ask for a detour.
A route through a repo helps different people in different ways. Here is who the line was drawn for.
Instead of hunting through folders, ride one line and arrive knowing the shape of the repo — where the code starts, what it touches, and where it ends.
Memory goes stale; git history doesn't. The line is rebuilt from the current repo, so it shows where things actually live now.
Onboarding becomes: ride the line, ask questions at the stops, keep moving. A map that can't rot in a drawer.
If a feature makes a dev tool look good in a screenshot but slows down the person using it, the line goes around it.
The short version: Gitrailway reads the repo, never touches it, and ships without a signup wall.
No. Gitrailway reads the repository read-only — structure, history, tests. Nothing is added to your project: no config file, no dependencies, no CI step.
No. The line points at the code; you read it in the editor you already use. Gitrailway is the map, not the territory.
File structure, git history and tests. From those it finds the entrypoints, the order the code actually runs in, and the files that prove the behaviour works.
Yes. Local and private repos are first-class citizens. Nothing leaves your machine unless you choose to share a line.
Lines are rebuilt from git history, so they refresh as the repo moves. Stale stops get retired, new ones get drawn in — no hand-maintained tours.
The build is public on X at @gitrailway. When it opens, it opens — no waitlist, no forms, nothing to sign up for.
Follow the project on X. When Gitrailway opens, it opens. No forms, no waitlist, nothing to sign up for. You'll already be following the people who built it.
Follow @gitrailway on X ↗