Macro/scope

A second look, through a wider lens.

Ten years ago, Kayvon Beykpour and Joe Bernstein sold Periscope to Twitter. The product taught a generation of users to point a phone at the world and broadcast. The deal was reported at roughly $86 million. The next chapter was the predictable one - run a thing inside the company that bought you, watch the platform shift around you, eventually leave. Then a pause. Then a question. What does someone who spent a decade building tools for watching do with the next decade?

The answer arrived in July 2023 as a company name that flipped the old one on its head. Where Periscope let users zoom in on a single moment, Macroscope zooms out across an entire codebase. The lens is the same; the subject changed.

The premise is straightforward, almost embarrassingly so: engineering work is mostly invisible to the people who depend on it. Managers ask for status. Reviewers skim the diff. Bugs slip through because nobody had the patience to read all 1,400 lines on a Friday. Macroscope's bet is that an AI with a graph of your repository in its head can do the patient reading, write a useful summary at the end, and make the standup unnecessary by the time it would have started.

A reunion, with one new face.

Two of the three co-founders have worked together since college. The third was acquired into Twitter exactly one year after them. None of this is a coincidence.

Three surfaces. One underlying graph.

Most AI reviewers shove a diff at a language model and ask it to find the problem. Macroscope builds a graph-based representation of the whole codebase first, then walks it. The difference shows up in the false-positive rate - the team published a case study with Parallel about exactly this.

The early believers.

Reference customers landed before the public launch, which is unusual. The list skews toward companies that ship a lot of code and have already invested in their own AI infrastructure.

FIG. 03 - Public reference customers as listed on macroscope.com.

From idea to launch.

For the curious.

Tuesday, again.

Return to the office south of Market. The clock has moved. The pull requests are still flowing. But the engineer who would have lost three hours reading them on Friday is doing something else now - building, mostly. The status meeting that was on the calendar for Monday has been quietly deleted. Nobody mourned it.

That is the small, specific thing Macroscope has changed: the half-hour you didn't realize you were spending. The question that didn't get asked because it wasn't anyone's job to ask it. The bug that would have shipped because nobody read line 1,184. Multiply that by 23 employees, 11 reference customers, eight languages, and however many pull requests are open right now, and you get the shape of a product that wants to be infrastructure.

The lens was always the same. The Periscope founders just turned it around.