Skip to main content

Connect Neon to GitHub Copilot

Give GitHub Copilot governed access to Neon’s 29 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Neon to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve Neon in Runlayer

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

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Neon’s 29 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Neon

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

  4. 4

    Use Neon from GitHub Copilot

    Neon’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

29 Neon tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • List projects

    Lists the first 10 Neon projects in your account.

  • List organizations

    Lists all organizations that the current user has access to.

  • List shared projects

    Lists projects that have been shared with the current user.

  • Create project

    Create a new Neon project.

  • Delete project

    Delete a Neon project

  • Describe project

    Describes a Neon project

  • Run SQL

    Execute a single SQL statement against a Neon database.

  • Run SQL transaction

    Execute a SQL transaction against a Neon database, should be used for multiple SQL statements.

See all 29 Neon tools

Control

What Runlayer can see and stop in GitHub Copilot

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every Neon call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination