Features
Where your delivery slows, in plain view.
Orbit reads the metadata your tools already produce and turns it into cycle time, review wait and deploy frequency for each repository, team and week.
01 / The numbers
Four numbers that
explain a week.
The same four measures for every team, every week. Trends matter more than a single snapshot.
- Deploy frequency
- 12.8per day ↑ 24% this period
- Cycle time
- 4.2hrs ↓ 1.6 hours faster
- Review wait
- 2.4hrs 57% of cycle time
- Change failure
- 1.1% Steady over 90 days
Find the wait.
Free the flow.
Spot where reviews stall and builds drag. Go from a weekly average to the actual pull request in two clicks.
- Cycle time split into code, review and deploy
- Drill from a team average to one pull request
- Filter by repository, team or release train
All repos.
One rhythm.
Commits, reviews, builds and releases from every service land in one timeline per team.
- Read-only access, repository by repository
- Pipeline events from any CI through a webhook
- Team, service and owner tags you control
Services connected: 6 · Events today: 214
A week's worth of insight. One useful conversation.
Every Monday the team gets a short brief: what moved, what stalled, and one question for the retro.
- Sent to the workspace or a shared team inbox
- Three signals, never a dashboard dump
- Links to the pull requests behind each signal
Review time fell 18%.
The release queue cleared.
Your on-call team had a quiet weekend.
04 / Privacy by design
Measure systems.
Trust people.
Orbit answers how work flows, not who is busy. Here is the line we keep.
What Orbit reads
- Commit timestamps and author IDs
- Pull request, review and merge events
- Build and deployment status
- Repository and team names you choose
What Orbit never reads
- File contents and diffs
- Individual scores or rankings
- Lines-of-code counts per person
- Anything outside the repositories you connect