Skip to content

Hosted Gate, step by step

The example: Brightline Studio, a 12-person agency. Everyone has a Google Workspace account at brightline.example, uses Claude Desktop, and works in a CRM that offers an MCP server. Jordan, the office manager, sets it up. No servers.

What you end with: everyone signs in with Google, their AI reaches the CRM with their own CRM access, your guardrails decide how far it may go, and every action is in one audit trail.

Time: about 15 minutes, plus a week of learning mode before you set guardrails.

What hosted Gate cannot do

Hosted Gate runs at app.acutisgo.com, so it cannot reach things inside your office: Active Directory, Windows sign-in, or \\server\share file shares. For those, use Windows Server or the Linux appliance.

Step 1. Create your account

  1. Open app.acutisgo.com/signup?product=gate.
  2. Fill in your name, work email, a password, and your company name. Press Create Account.
  3. Open the email from Acutis and press Verify email address.
  4. Sign in at app.acutisgo.com/gate. Gate asks you to secure your account: scan the QR code with your authenticator app, type the 6-digit code, and press Confirm & continue.

You are now the Gate admin.

Step 2. Start the trial

  1. In the left menu, open License.
  2. Under This Gate (hosted), enter how many people will use it (12) and press Subscribe.
  3. Finish the Stripe checkout. The first 14 days are the trial; you can cancel any time before it ends under Manage billing.

Until there is a subscription, AI tool calls are paused. Sign-in and the console work regardless.

Step 3. Let everyone sign in with Google

  1. Open Identity → Google Workspace.
  2. Workspace domain: brightline.example.
  3. Tick Enable for my organization.
  4. Leave Also allow local sign-in ticked for now, so your own password still works. Press Save.

Now anyone with an @brightline.example Google account can open app.acutisgo.com/gate, press Sign in with Google, and is in. Their account is created at first sign-in. Google enforces their two-step verification.

More detail: Google Workspace sign-in.

A second admin

Make sure you are not the only admin. Under Identity → People, add a colleague with the role Gate admin and a temporary password. See People you add in Gate.

Step 4. Add the CRM

Gate connects to any app that speaks MCP over HTTP.

  1. Open My apps → Add an app for everyone.
  2. Short name: crm (this is how guardrails will name it: crm://tools/...). Name: CRM.
  3. MCP URL: the address your CRM gives for its MCP server.
  4. Sign-in: choose Each person's own key (or own sign-in). Then every request carries that person's identity, and the AI can do only what they can do in the CRM.
  5. Header and Prefix: what the CRM expects, usually Authorization and Bearer. Press + Add app.

Each person then opens My apps, finds CRM, and connects their own key once. It is stored encrypted and only ever sent to the CRM.

Avoid the shared account option

One shared account is there for apps that cannot do per-person access. Every call is labelled "shared" in the audit trail, and the app cannot tell people apart. Use it only when there is no other way.

Step 5. Connect everyone's Claude Desktop

Each person does this once, on their own computer:

  1. Sign in at app.acutisgo.com/gate → Connect an AI.
  2. Under Personal tokens, type Claude Desktop as the label and press + Create token. Copy it now: it is shown once.
  3. The Claude Desktop box below now shows a ready-made config with the token filled in. Press Copy.
  4. In Claude Desktop: Settings → Developer → Edit Config. Paste it into claude_desktop_config.json (merge with anything already under mcpServers), save, and restart Claude Desktop.
  5. In a new chat, the tools icon lists the Acutis Gate tools.

Claude Desktop needs Node.js installed for this (it runs npx mcp-remote). Cursor, VS Code and Open WebUI work too: see Connect an AI.

Step 6. Learning week, then guardrails

A fresh Gate is in learning mode: every AI call is allowed and recorded. After a normal week:

  1. Open Guardrails → Build rules from the trail. Gate drafts rules from what people actually did.
  2. Read each one as a sentence, change what you disagree with, and tick Dry run for a few days if you want to see what would be blocked first.
  3. Press Save as new version. From now on, nothing is allowed unless a guardrail says so.

A full worked example: Guardrails, a worked example.

Step 7. Check it

  • Connect an AI → What this AI can do as you → Run the check shows which apps and actions your AI gets.
  • Health check → Run all checks walks the chain and marks anything to fix.
  • Audit trail shows every call, by person.

Common questions

Someone left the company. Suspend them in Google Workspace; Gate refuses their next sign-in. If you added them under People, press Remove there.

Seats. A seat is an active person. Change the count any time under License → Change seats; Stripe prorates it.

Where is my data? Gate stores audit rows and settings in Acutis' cloud. App keys are stored encrypted and only sent to that app. Stream the trail to your own SIEM from Streaming if you want your own copy.