Last updated June 1, 2025

Product Overview

Macroscope provides automated status and productivity reporting for software teams. It helps leaders stay informed about product changes by using codebase activity as the source of truth and tracks how the team’s engineering efforts are allocated across projects. Macroscope also helps engineers broadcast what they’re doing automatically, so they can spend more time building and less time reporting status.

Macroscope has a few core capabilities:

• Automated status updates of how product and engineering initiatives are evolving
• Automated identification and summarization of all active projects at the company, with analytics showing % of engineering allocation to each project.
• Automated summarization of Commits and Pull Requests to save engineers time from describing their changes.
• Automated code review (focused on correctness issues) in Pull Requests
• Engineering productivity benchmarks that show how your team’s engineering output compares to other companies
• Native Slack integration so that various summaries (commits, pull requests, project updates) can be broadcasted in any configured #channel

Macroscope is currently in private beta.

Hosting & Architecture

Macroscope’s infrastructure is hosted on Google Cloud Platform.

Authentication & Customer Access Control

GitHub Setup

Customer setup involves OAUTH login with GitHub and installing Macroscope’s GitHub app in your GitHub Organization (this can only be done by an admin of the GitHub org). Macroscope fully inherits your GitHub organization’s access control permissions. This means that once you’ve installed our GitHub app, your GitHub users can simply login to Macroscope’s website using GitHub OAUTH, and they’ll have access to any GitHub repositories that they already have access to via your GitHub organization. Your organization’s users will not see any GitHub repositories or commit summaries from repos that they do not have access to. Any edits made to your GitHub privileges (e.g. off-boarding an employee) will automatically take effect within Macroscope’s systems. This reduces any overhead of needing to create, manage or edit user permissions within Macroscope.