DISCOVER
Start with the source.
Scan a repository on your device. Review the provider references it finds, with the file and line that led you there.
How discovery worksTHE APPLICATION FIELD GUIDEKnow what runs
Know what runs
your application.
Your code, hosting, data and the people behind them. A working record of everything an application depends on, with the evidence close at hand.
In development. Available for local review.A WORKING LOOK INSIDE
Follow an application’s footprint.
Switch environments. Open a resource.
See the context that stays with it.
Sample inventory · no live provider data
| Provider | Resource | Environment |
|---|---|---|
| Vercel | production | |
| Neon | production | |
| Better Stack | production | |
| GitHub | shared |
4 resources for Learning Studio. Shared resources appear in every environment. Select a resource to read its details.
FROM REPOSITORY TO RUNBOOK
Build a record you can return to.
A little structure for the work
between the dashboards.
DOCUMENT
Leave a useful trail.
Give each resource an owner, an environment and a runbook. Keep the context your future self, or the next person on call, will need.
Inside the workspaceOBSERVE
Know where a signal came from.
Inspect the source and freshness of an observation. Read Vercel deployment state or check a public HTTPS endpoint from the local workspace.
Data & access boundariesTHE CURRENT EDITION
Review proposed pricingUseful today. Still taking shape.
Repository discovery, manual inventory, Vercel deployment reads and endpoint checks are available locally. Hosted connections, durable history and collaboration are planned.