Skip to main content
Control and security · Code gateway

Apply company policy to
developers' AI coding tools too

The code gateway routes requests from developers' AI coding tools to the company gateway. It identifies each developer by an issued key and checks requests for repositories, files and commands on the block list. Requests are handled only by models the administrator has chosen and are recorded in the coding session log.

The Code gateway tab in security settings
The Code gateway tab in security settingsReal product screen
LLM gateway · Code gateway

Apply the same policies
to every model call

Connect models from 23 providers, across vendor APIs, cloud, gateways and self-hosting, to one gateway. Requests from coding tools get the same policies and logging.

Code gateway pipeline
1
AuthenticationDeveloper verified by issued key
2
Policy checkBlocked repositories, files and commands
3
GuardrailsSensitive data inspection
4
Allowed modelHandled by an administrator-approved model
5
Coding session logCall record and cost tracking
Claude CodeCodex CLIOpenCode+8

Policy violations are logged as warnings by default, and administrators can switch them to blocking. Set which users and groups can use each model, along with daily token limits and pricing, to manage cost.

23Model providers4Connection typesAccess, limits and pricing per model
Real product screen
Code gateway policies and allowed models
What changes

Before and after adoption

Before

When developers use coding tools with personal accounts, there is no way to know where the source code goes.

After

Requests from coding tools are sent through the company gateway, and only to allowed models.

Before

Files that hold sensitive data, such as .env, can be sent to the model.

After

Syncgate checks for repositories, files and commands on the block list, and warns or blocks.

Before

There is no record of who sent which code to AI.

After

Call records and costs are kept in the coding session log.

How it works

Four steps

01Identify the developer

The key issued to each developer identifies who sent the request.

Keys issued to each developer in the code gateway
Key features

Code gateway features in detail

11 coding tools

Connect 11 coding tools, including Claude Code, Codex, GitHub Copilot CLI and OpenCode.

Repository, file and command blocking

Policy violations are logged as warnings by default, and administrators can switch them to blocking.

Allowed models

Set which models coding tools can use.

Key issuance

Issue and manage a key for each developer.

Enforced settings on developer PCs

Distribute settings so that coding tools on developer PCs send their requests through the gateway.

Coding session logs

See call records and costs for each coding tool in one place.

Admin settings

Settings each company configures

  • Set the block list and the warn and block policies.
  • Set the models coding tools use.
  • Issue keys to developers.
11Coding tools
Warn and block policies
Coding session logs

Figures reflect the product as of October 2026.

FAQ

Frequently asked questions about the code gateway

Which coding tools are supported?

It supports 11 coding tools: OpenCode, Kilo Code, Hermes Agent, Qwen Code, GitHub Copilot CLI, Goose, Grok Build, GitHub Copilot in VS Code, Antigravity CLI, Claude Code and Codex.

What if a developer bypasses the gateway?

Coding tool settings can be enforced on developer PCs so that the tools send their requests through the gateway.

Do we have to block from the start?

No. By default only warnings are logged, and administrators can switch each item to blocking.

See it with
your own documents

In a consultation, we connect a few of your documents so you can check the answer quality for yourself. Send us your questions and our team will get back to you.

Product videosReal product screens · Example company ACME Logistics · 16 videos