Connect DeepWiki to ECA
Give ECA governed access to DeepWiki’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add DeepWiki to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve DeepWiki in Runlayer
Add DeepWiki from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches DeepWiki’s 4 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to DeepWiki
Sign in the way DeepWiki requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use DeepWiki from ECA
DeepWiki’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
4 DeepWiki tools in ECA
Runlayer policy decides which of these ECA users can call.
Ask question
Ask any question about a GitHub repository and get an AI-powered, context-grounded response.
Ask wiki question
Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.
Read wiki contents
View documentation about a GitHub repository.
Read wiki structure
Get a list of documentation topics for a GitHub repository.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every DeepWiki call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more