Loading...
SolonGate Cloud is the managed edition. There is nothing to host: you create an account, get an API key, and a global guard then enforces your policy on every AI tool call on that machine. Policies and audit logs live in the CLI itself, with no separate website to open. This guide takes you from zero to enforced in a few minutes.
Sign up at auth.solongate.com.
SolonGate Cloud does not currently have a self-serve way to issue or view your API key from the account you just created. If you want to run the Cloud edition, contact us and we will get you a key directly.
First, install SolonGate. On macOS the global npm folder is root-owned, so the install has to run with sudo:
$ sudo npm i -g @solongate/proxy@latest$ npm i -g @solongate/proxy@latestSet your key, then run it to turn on the guard:
$ export SOLONGATE_API_KEY=sg_live_...$ $env:SOLONGATE_API_KEY = "sg_live_..."$ solongateSolonGate turns on the global guard automatically: a hook that intercepts every tool call from every AI session on the machine and evaluates it against your active policy. From now on, each tool call is allowed, blocked, or logged according to policy.
Open the Policies panel and create a policy. A policy is a set of rules; each rule targets a tool plus a constraint and is either ALLOW or DENY. Two modes:
*.env, or deny commands matching *rm -rf*).Press s to save a policy as the one the guard enforces. Rules compile to an OPA-WASM bundle and take effect on the next tool call.
Every decision shows up in the Audit panel: what was allowed, what was blocked, and which rule matched. When a legitimate action is blocked, you do not have to rewrite the whole policy. Select the blocked entry and press w to whitelist it. SolonGate adds a narrow ALLOW exception for exactly that action, and the action is permitted on the next try. You can remove that rule again from the Policies panel to put the block back.