Skip to main content

Connect Cloudflare Radar to Oh My Pi

Give Oh My Pi governed access to Cloudflare Radar through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Cloudflare Radar 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. 1

    Approve Cloudflare Radar in Runlayer

    Add Cloudflare Radar from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Oh My Pi to Runlayer

    Users add the Runlayer Plugin to Oh My Pi by following Runlayer’s setup guide. Oh My Pi reaches Cloudflare Radar’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Oh My Pi setup guide
  3. 3

    Sign in to Cloudflare Radar

    Sign in the way Cloudflare Radar requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Cloudflare Radar from Oh My Pi

    Cloudflare Radar’s approved tools appear in Oh My Pi. Every call is checked against policy and recorded.

Tools

Cloudflare Radar tools in Oh My Pi

Cloudflare Radar reports its tools when your organization connects it, so the list depends on your deployment.

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 Cloudflare Radar 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

Find another combination