Skip to content

Panolayer Studio · Architecture

See what calls what.

Panolayer maps your repository’s services, modules, functions, callers and dependencies. The map is parsed from the source, so the same code always gives the same map, and your agents and the Verification Engine work from it too.

macOS 15 on Apple silicon · Free to start · No credit card required

Architecture · from system to source

Panolayer architecture map with application groups, functions and their connected dependencies.

Full capture · scroll to inspect the details

You’re three levels into a service, trying to work out what calls it.

A file tree shows where code lives, not what depends on it. With agent-written code, it’s harder still: nobody on the team wrote it, and the diff was 2,000 lines. Panolayer lets you move through code by what calls what, not by folder.

What you can do

From the whole system to a single line

01

Start with the whole system

Open a repository and see its services, what’s inside each one, and how they connect.

Start at the repository

Start at the repository

The architecture diagram connects the repository to API Routes, Application Pages, Other, Shared Libraries and UI Components.

Full capture · scroll to inspect the details

02

Drill down to what you need

Move from services to modules to functions. Diagram, column and path views show the same structure three ways.

Open a function. Go straight to its source.

Open a function. Go straight to its source.

The recorded walkthrough opens the pick function from UserSwitcher in the architecture map, revealing its source, summary and verification results.

Full capture · scroll to inspect the details

03

Read any function in context

Open getPrice() and see what it does, its inputs and outputs, who calls it, what it depends on, the rules that apply and its verification status.

Architecture · source and rules together

Architecture · source and rules together

Panolayer Studio source view showing a PATCH handler, its function summary, and a failed rule at line 65.

Full capture · scroll to inspect the details

04

See what a change will reach

Change getPrice() from cents to dollars, and the map shows it reaches the product page, the cart and checkout before anything ships.

Follow a component into its functions

Follow a component into its functions

The architecture map connects the UserSwitcher component to its pick function, alongside UserSwitcherProps and neighboring components.

Full capture · scroll to inspect the details

05

Your agents see the same map

Agents can query the map through an MCP tool for structure, callers and dependencies, and verification checks their changes against it.

Panolayer Agent · answers grounded in your source

Panolayer Agent · answers grounded in your source

Panolayer Agent explains the posting workflow with references to the repository's routes, validation and data types.

Full capture · scroll to inspect the details

Living Documents

Documentation that keeps up

Ask about any part of your codebase and get a document written from the architecture, with its claims linked to the source. Regenerate it when the code changes.

How Living Documents work

Living documents · source-linked context

A living document explaining a feature with links to source files and line numbers.

Full capture · scroll to inspect the details

Questions

Something else? Contact us and we’ll answer.

Is the map generated by an LLM?

No. The structure is parsed from source. A model can add plain-language descriptions when you ask, but it never decides the structure.

Can I use the map without running agents?

Yes. It works on its own for finding your way around unfamiliar code.

Which languages are supported?

TypeScript, JavaScript, Python, Go, Rust, Java and more. Dynamic calls and generated code are harder to trace and may need a manual look. See the full list in the docs.

Does it work on a monorepo?

Yes.

Try Panolayer on your codebase.

Free to start · No credit card required

How Panolayer handles your code

Next: Living Documents