Connections for Cloudflare OS

Easy sign-in and connectors. The same Gatekeeper security.

Today every sign-in method and every service in Cloudflare OS needs its own OAuth app. With WorkOS AuthKit, people sign in with SSO and connect GitHub, Google, Slack and more in one click. Every action still goes through the Gatekeeper.

Try the walkthrough
EasySign in with SSO. Connect a service in one click. No OAuth apps to make.
Same securityThe Gatekeeper still decides what the agent can do, asks before it acts, and logs every step.

Today

Before you can click Connect, you set up OAuth yourself

Every service in Cloudflare OS goes through a Gatekeeper, the part that controls what the agent can do with it. Each Gatekeeper needs its own OAuth app. You make it by hand.

  1. Create an OAuth app on GitHubFind the right page in GitHub's developer settings. Paste the callback URL.

  2. Copy two secrets into CloudflareFrom GitHub into the GitHub Gatekeeper, from the command line.

  3. RedeploySign-in is a separate setup again: Access, a password, or more OAuth apps.

  4. Do it again for every serviceOne app, two secrets and one more thing to rotate, each time.

The security in Cloudflare OS is good. The setup is the hard part, and it stops most people from trying it.

With AuthKit

Sign in. Ask. Click Connect. Approve.

Click through it. The bar at the top shows whose page you are on. The panel below it shows what the GitHub Gatekeeper has set up so far.

Sign in to Acme OS

or
Make an issue dashboard for acme/web.
Connect GitHub
I need the repo acme/web to read and create issues.

Connect a GitHub repository

Choose what the agent can use.

Repository

acme/webchosen by the agent's request

The agent will be able to:

  • Read issues on acme/web
  • Create issues on acme/web, after you approve

It cannot see your other repos.

Authorize access

Signed in to GitHub as you

This app will be able to:

  • Read and write repositories
  • Read your profile and email
Connected: acme/web
I have a plan. I want to create 3 issues.

Approve this action?

  1. Bug: login fails on Safari
  2. Docs: update the README
  3. Chore: upgrade dependencies
Done. I created 3 issues on acme/web and built the dashboard.

Log

  • Connected acme/web
  • Approved: create 3 issues
  • Created 3 issues

GitHub Gatekeeper

  • Accessacme/web only
  • Tokenkept by the Gatekeeper, never the agent
  • Changeswait for your approval
  • Logevery step recorded

    How it works

    WorkOS handles the logins. The Gatekeeper still runs the show.

    You add one small Worker, the keyring, to your Cloudflare OS. It gets logins from WorkOS and hands them to your Gatekeepers. Nothing else in Cloudflare OS changes.

    Your agentAsks to use a repo. Never sees a password or token.
    GitHub GatekeeperDecides what the agent can do. Asks you before it acts. Logs every step. Same as today.
    GitHubOnly the Gatekeeper talks to it.
    ⟰ GitHub login token
    KeyringNew. One Worker in your account. To the Gatekeeper, it looks like GitHub's login page.
    ⟰ token
    WorkOSAuthKit signs you in. Pipes runs the GitHub login and keeps the token fresh.
    • No OAuth apps to makeTo try it, WorkOS lends you its own GitHub, Google, Slack and Notion apps. In production you add your own, once, in WorkOS.
    • No secrets on your GatekeepersThe keyring holds one WorkOS key. The GitHub Gatekeeper holds none.
    • Signing in is not connectingSign in with GitHub only proves who you are. The agent gets a repo only when you click Connect, through the Gatekeeper.
    • Your tokens, laterOne setting moves the tokens out of WorkOS and into your own Cloudflare account. Same screens for your users.

    Setup, for the person who runs Cloudflare OS

    Run init, paste your WorkOS key, and pick your sign-in methods and services. Init turns them on in WorkOS and adds AuthKit to Cloudflare Access. The GitHub Gatekeeper gets one setting that points it at the keyring.

    $ npx cf-os init acme-os
    ? Add the keyring        yes
    ? WorkOS API key         sk_test_••••
    ? Sign-in methods        Google, Microsoft, GitHub, email
    ? Services               github, google, slack, notion
    ✓ Ready. Open https://acme-os.example.com
    
    $ wrangler secret list --name gatekeeper-github
    []   # no GitHub secrets anywhere