Question 1

What is Stepflo?

Accepted Answer

Stepflo is a free developer tool that connects to your GitHub repo and automatically detects all user-facing flows from your code structure — routes, pages, layouts, and directory conventions. It then maps friction signals from GitHub issues to specific steps in those flows, giving you a visual map of every journey in your product and where users are getting stuck.

Question 2

How does Stepflo detect user flows from code?

Accepted Answer

Stepflo uses framework-aware analysis to read your repository's file structure. For Next.js apps, it reads the App Router directory. For Vite and React Router apps, it reads route configuration files. It identifies pages, layouts, API routes, and directory patterns, then uses AI to determine which combinations represent distinct user-facing flows — like signup, onboarding, checkout, or settings. It finds every flow, not just the ones you've documented.

Question 3

Does the flow map update when my code changes?

Accepted Answer

Yes. Stepflo doesn't take a one-time snapshot. You can re-analyze your repo anytime — after shipping new routes, restructuring pages, or adding features. The flow map reflects your product as it currently is, not as it was during the last planning session.

Question 4

How does Stepflo find where users get stuck?

Accepted Answer

Stepflo syncs your GitHub issues and uses AI to screen for friction language — reports about confusing UX, broken flows, slow processes, failed integrations. Issues that indicate user friction get matched to the specific flow step where the problem lives and scored by severity. This turns a flat list of issues into a visual map showing which steps are failing and how badly.

Question 5

Is Stepflo free?

Accepted Answer

Yes, and not in a "free trial" way. Stepflo is free for one repo with no time limit, no hidden paywall, no trial period, and no feature gating. The free experience is the full product, not a preview.

Question 6

What permissions does the GitHub App request?

Accepted Answer

Stepflo requests read-only access to repository contents (file structure only — not source code) and read access to issues. It does not request write access to any repository data. The app can be revoked instantly from GitHub Settings → Applications → Stepflo.

Question 7

Does Stepflo store my source code?

Accepted Answer

No. Stepflo reads your file tree (names and paths) and issue titles. It does not read, store, or transmit source code. AI analysis uses Anthropic's Claude with zero data retention — your data is processed and discarded, never used for training.

Question 8

How is Stepflo different from Pendo or Amplitude?

Accepted Answer

Pendo and Amplitude track user behavior — clicks, pageviews, funnel completion. Stepflo works from the code side: it reads your repo structure to detect all user flows and matches GitHub issues to specific journey steps. Pendo answers "what are users doing?" Stepflo answers "what does the complete journey look like, and which step is broken?" They're complementary — Stepflo doesn't require any client-side instrumentation or behavior tracking.

Question 9

How is Stepflo different from journey mapping in Miro or FigJam?

Accepted Answer

Journey maps built in workshops are accurate for about a week. Then the product changes and the map doesn't. Stepflo's flow map is generated from your actual code structure and can be refreshed anytime your code changes. It's not a workshop artifact — it's a continuous, code-aware diagnostic tool that finds flows you may not have mapped manually.

Question 10

What is code-based user journey mapping?

Accepted Answer

Code-based user journey mapping is the practice of inferring a product's user journeys directly from the codebase — using file structure, route patterns, and directory conventions as the source of truth for how users move through a product. Unlike behavior-based journey mapping (which requires analytics instrumentation) or manual journey mapping (which requires workshops and goes stale), code-based mapping works from the structure that already exists in any repository and stays current as the code evolves. Stepflo is the first tool to do this continuously and connect the result to friction signals from issue trackers.

Question 11

What frameworks does Stepflo support?

Accepted Answer

Stepflo currently supports Next.js (App Router and Pages Router), Vite with React Router, and standard React Router configurations. Framework detection is automatic — Stepflo reads your package.json and config files to determine the right extraction strategy. Support for additional frameworks is coming based on user demand.

Privacy Policy