Docs · Cloud

SolonGate Cloud setup

SolonGate Cloud is the managed edition. There is nothing to host: you create an account, pair your machine once, and a global guard then enforces your policy on every AI tool call on that machine. Policies and audit logs live in the hosted dashboard. This guide takes you from zero to enforced in a few minutes.

What you need

• A SolonGate account (free to create).
• Node.js 20 or newer on the machine you want to protect.
• An AI tool that uses tool calls, such as Claude Code.

Step 1: Create your account

Sign up at auth.solongate.com. After signing in you land on the dashboard at dashboard.solongate.com, where you will manage policies and review the audit log. There are no API keys to copy; pairing is codeless (Step 2).

Step 2: Pair the machine and turn on the guard

One command does everything. No install, no API keys. Run:

npx -y @solongate/proxy@latest login

It opens your browser to authorize the device, with no key copy-paste. Approve it from your signed-in dashboard, and SolonGate 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.

To stop enforcing and restore your previous settings, run npx @solongate/proxy logout.

Prefer a shorter command? You can install the CLI globally with npm install -g @solongate/proxy and then use solongate login / solongate logout instead.

Step 3: Write a policy

Open Policies in the dashboard 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:

• Denylist: everything is allowed except what you block. Add DENY rules (for example, deny any file named *.env, or deny commands matching *rm -rf*).
• Whitelist: nothing is allowed except what you permit. Add ALLOW rules for the exact tools, files, or commands you trust.

Click Activate to make a policy the one the guard enforces. Rules compile to an OPA-WASM bundle and take effect on the next tool call.

Step 4: Review the audit log and approve exceptions

Every decision shows up under Audit: 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. Open the blocked entry and click Whitelist this. SolonGate adds a narrow ALLOW exception for exactly that action, recompiles the policy, and the action is permitted on the next try. You can revoke any granted exception from Granted exceptions (on both the Audit and Policies pages) to put the block back.

Prefer to run everything on your own hardware with no outbound connectivity? See the Local / air-gapped guide.