The setup, timestamped
You’ve heard "five-minute setup" before.
So we timestamped ours. Every screen, every click, every permission - from "Sign in with GitHub" to your first cycle time breakdown. Bring a stopwatch.
Free for teams of up to 10 developers. No credit card required.
Or watch the whole thing first
Why this one is actually five minutes
Setup is slow when there is something to install. There is nothing to install.
No agent. No plugin. No pipeline.
CodePulse reads PR and commit metadata GitHub already has. Nothing runs on your laptops, your CI, or your servers.
Read-only, metadata only.
We analyze metadata only - PR titles, timestamps, and review activity. We never access source code, secrets, or credentials.
No sales call.
No demo gate, no procurement dance. Connect your work GitHub account and look at your own data instead of a slide deck.
The whole setup, screen by screen
This is the real flow, with the real screens. Timestamps are from a normal-sized organization on an ordinary Tuesday.
- 0:00Objection killed: Another account to manage
Sign in with GitHub
You use the GitHub account you already have - your work account, the one with your org in it. No new credentials, no SSO project, no invite emails.
codepulsehq.com/loginSign in to CodePulse
Engineering intelligence for your team
Sign in with GitHub- We never see or store your source code
- Read-only access to PR and commit metadata
- You choose which repositories to connect
- 0:30Objection killed: What exactly are you getting access to?
GitHub asks, not us
This screen is GitHub's, not ours. Read it - it grants read-only access to your profile and organization membership. Repository access comes later, per repository, through the GitHub App. If any vendor's permission screen asks for more than the job needs, close the tab.
github.comAuthorize CodePulse
- Read your profile information
- Read your organization membership
AuthorizeCancel - 1:15Objection killed: I'll need to open an IT ticket
Point it at your organization
Pick the organization to track and install the CodePulse GitHub App on it. Not an org owner? You get a "Request Installation" button instead - GitHub notifies your admin with a one-click approve. That is the only step that can take longer than five minutes, and it is GitHub's guardrail, not ours.
codepulsehq.com/onboarding/selectSelect Your Organization
Choose a GitHub organization to start tracking.
acme-engineeringacme-platform - 2:00Objection killed: I'll be configuring this all afternoon
Pick repositories - they're pre-selected
We pre-select your most active repositories. Start with a few key ones - you can add more from your dashboard any time. There is nothing else to configure: no webhooks to create, no YAML, no per-repo tokens.
codepulsehq.com/onboarding/select-reposSelect Repositories
We've pre-selected your most active repositories.
acme-apiacme-webacme-infraContinue with 3 repos - 2:30Objection killed: And now I wait
Your import already started
The moment you picked repositories, the import kicked off in the background. While the last 7 days of PRs and reviews stream in, we ask four quick questions - your role, team size, and what you want to see first - so your dashboard leads with what you actually care about. Nobody watches a progress bar.
codepulsehq.com/onboarding/personalizeWhat best describes your role?
VP / Director of EngineeringEngineering ManagerStaff / Principal EngineerContinue - 4:30Objection killed: It'll be empty for a week
Your first insights are ready
Cycle time breakdown, review bottlenecks, and team activity from your last 7 days - real numbers from your real PRs. The rest of your history, up to 6 months, keeps importing in the background. We email you when it is complete.
codepulsehq.com/onboarding/insightsYour First Insights Are Ready!
47
PRs analyzed
129
Reviews
11
Contributors
7d
Last 7 days
See Your Velocity Score
The average of those timestamps is not a promise. It is just what happens when there is nothing to install.
What we never ask for
- No credit card
- No agent on your machines
- No IDE plugin
- No write permissions
- Revoke access any time from GitHub
What five minutes gets you - and what it doesn’t
At the five-minute mark you have your last 7 days: cycle time, review flow, and where PRs are getting stuck. That is enough to spot this week’s bottleneck. It is not enough to judge a quarter. The full picture - up to 6 months of history, trends, and benchmarks - lands in the background over the next hours, and we email you when it is complete. Very large organizations can take longer because GitHub rate limits apply to everyone; the 7-day snapshot still arrives while you are on the page.
The questions your security review will ask
No. If you are not an owner, the install button becomes "Request Installation" - GitHub notifies your admin, who approves with one click. Everything else in the flow is identical.
Your PR data is already sitting in GitHub. Go look at it.
Five minutes from now you either know where your PRs get stuck, or you have lost five minutes. That is the whole bet.
Free for teams of up to 10 developers. No credit card. Revoke any time.