Connect Socket to Oh My Pi
Give Oh My Pi governed access to Socket’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Socket to Oh My Pi in four steps
Admins approve the server once. Everyone in Oh My Pi then gets it through the same governed connection.
- 1
Approve Socket in Runlayer
Add Socket from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Oh My Pi to Runlayer
Install the Runlayer CLI so Oh My Pi can reach Socket, which runs on the user’s machine.
Oh My Pi setup guide - 3
Sign in to Socket
An admin adds Socket credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Socket from Oh My Pi
Socket’s approved tools appear in Oh My Pi. Every call is checked against policy and recorded.
Tools
1 Socket tools in Oh My Pi
Runlayer policy decides which of these Oh My Pi users can call. 1 read data only.
Depscore
Query dependency security scores across npm, PyPI, cargo, and other package ecosystems.
Control
What Runlayer can see and stop in Oh My Pi
Some controls apply to every client at the gateway. Others depend on what Oh My Pi exposes to Runlayer.
Gateway policy (available)
Every Socket call from Oh My Pi passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Oh My Pi as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Oh My Pi yet, so control happens at the gateway.
Frequently asked questions
Connect more