Inspect your repository technology evidence

Inspect declared technologies, versions and component evidence from bounded static scans; unsupported formats and missing sources remain explicit.

Static adapters cover the documented ecosystem families without executing repository scripts or package managers. Literal extraction is partial for dynamic build/configuration languages. Exact Git subject binding requires a stable trusted host capture; informational GitHub language bytes do not establish an exact commit.

How it works

  1. Open project Workflows

    Open Workflows from Projects or Sessions with Shift+W, or use the browser action.

  2. Configure and start work

    Choose accounts, hosts and limits, then start a task, request review or connect a tracker. CLI and scoped MCP tools expose the same operations.

  3. Keep live actions explicit

    Live actions require configured permissions, accounts and budgets; the demo only reads sample records.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.