Radar

Radar watches your project’s data and tells you when something is wrong weeks before it surfaces in a status call.

What Radar does

Radar connects to three data sources:

• PM tools - Jira, Linear, Shortcut, GitHub Issues, YouTrack
• CI/CD - TeamCity (if you’re on Hypercade Foundation)
• Version control - GitHub, Perforce

It inspects commit history, build patterns, ticket flow, and milestone timing to produce a composite health score. Then it flags anomalies: velocity drops, scope creep, build degradation, team concentration, code quality erosion.

Why this matters

Most project problems announce themselves late. You discover scope creep in the final push. You find out about tech debt when refactors balloon into months. You realize a key person is a single point of failure after they leave.

Radar surfaces these patterns in real time. A velocity decline shows up as a risk flag days after it starts, not weeks later in a milestone review. A build time trend that’s been creeping up becomes visible before it becomes a critical path blocker.

What you get

When you add Radar to a project, you see:

• Composite risk score - overall health, 0-100 (higher is worse)
• Risk breakdown - which categories matter most right now (velocity, team, scope, build, code quality)
• Signal trends - how each individual metric has changed over the last 30 days
• Anomaly flags - specific things to pay attention to, ranked by severity
• Recommended actions - what to look at or change

Updates happen daily. Most studios check in weekly; some glance daily.

Privacy

Radar respects your team’s privacy. Here’s what surfaces and who sees it:

• Studios see everything. You see your team’s commit patterns, velocity trends, and individual signal breakdowns. You should. This is your project.
• Publishers see project health only. If you share Radar data with a publisher or fund partner, they see your composite risk score and risk categories, but not individual contributor data. No one’s name appears. They can see “velocity dropped 20% this sprint” but not “Alice and Bob slowed down.”

This separation is hard-coded. Contributor-level data is never exported or shared beyond the team.

Getting started

If you’re on Hypercade Foundation, Radar is already connected to your TeamCity instance. Add your PM tool’s credentials in the Radar settings, and Radar will start building your baseline.

If you’re not on Foundation, email hello@hypercade.io to discuss enabling Radar separately.

Next steps

Start by understanding Risk Signals - a detailed reference of what each metric means and why it matters.

Then check in on your project’s Radar dashboard weekly. Pay attention to anomaly flags. If Radar says velocity dropped 30% this week, dig into your PM tool and figure out why. Maybe your team was in crunch and you expected it. Maybe a dependency hit you by surprise. The flag is just saying “look here.”

Over time, Radar becomes your early warning system. You’ll catch problems early enough to actually do something about them.