Skip to main content
A page is a small app an agent builds for you: a dashboard, a report, an interactive tool. It’s wired to your data with live values, runs in a managed sandbox under your permissions, and can be shared with your team or published.

Getting a page

You don’t drag and drop — you ask. In a thread, describe what you want and an agent builds it:
“Turn this into a dashboard showing signups by plan over time, with a filter by region, that I can share with the team.”
The agent generates the page, wires it to the right data, and shows it back to you. Ask for changes in the same thread and it rebuilds.

Live, not a snapshot

Pages read your data at view time, so they stay current — open one tomorrow and it reflects tomorrow’s numbers. They can also hold their own state and react in realtime when more than one person is looking.

Sharing

  • Private — open to people in your workspace, under your existing permissions.
  • Public link — publish a read-only version anyone with the link can view.
Identity and access always come from the viewer’s own permissions, so a page can’t expose data the viewer isn’t allowed to see.
Building pages programmatically (deploying via the API, MCP, or SDK, and the window.erdo client) is covered in the developer guide, Build Apps.