Search Results

Getting started Sentilai is the control plane for the AI coding assistants your team already uses. Every request from Claude Code, Cursor, GitHub Copilot, Gemini CLI or Codex CLI routes through the Sentilai Gateway, where your policy is enforced in real time a...

Connect your tools The Sentilai Endpoint app configures your AI tools to route through the Gateway. On a governed machine, open the app and use Govern all detected tools — everything below happens automatically. This page documents what each adapter actually d...

Sentilai Endpoint (desktop app) The Sentilai Endpoint is the small desktop app that makes governance zero-touch: it discovers the AI tools on the machine, routes them through the Gateway, wraps local MCP servers, and reports device compliance. Install & sign i...

MCP governance MCP servers give AI agents tools — file access, browsers, deploy keys. Sentilai governs them in real time on every request. MCP Inventory Every MCP server seen anywhere — discovered on developer machines by the Sentilai Endpoint, or observed in ...

Policy & risk detection Every outbound AI request is scanned before it leaves, by layered detectors. Findings are recorded on the request's Activity row; depending on your settings they warn, report silently, or block. Format detectors High-precision pattern d...

Real-time alerts Don't watch dashboards — get paged. Sentilai posts to your channels the moment a qualifying governance event fires. Channels Slack — an incoming-webhook URL; alerts arrive as formatted messages. Microsoft Teams — an incoming-webhook URL; alert...

Activity & conversations Activity is the audit trail: one row per AI request, recorded by the Gateway after the response streams back. What's recorded Model, tool (Claude Code / Cursor / …), developer identity, device, connection mode (subscription pass-throug...

Provider keys (Provider Vault) Some tools can only carry an API key (Cursor, Copilot, Gemini CLI, Codex CLI). For these, the Gateway injects your organization's provider key server-side — developers never see or hold it. Supported providers OpenAI and Anthropi...

Team management & SSO Roles Admins use the Admin Console: policy, inventory, activity, billing. Developers use the Sentilai Endpoint on their machines; they don't need console access. Both take a seat. Your plan's seat limit and current usage are on the Billin...

Devices & logs Device registry Every machine running the Sentilai Endpoint registers with its own credential (public-key identity). The Devices screen lists them with first/last seen, reported hostname, and compliance state. A device credential can be revoked ...

Support & tickets Sentilai has a built-in, closed-loop support system — no third-party helpdesk holds your data. Opening a ticket In the Admin Console's Support area: subject, description, attachments. You'll see the full ticket history and status there. Email...

Compliance & SIEM Evidence pack The Compliance screen assembles an auditor-ready evidence pack for any period: the policies in force (MCP default + rules, detector actions), risk sensitivity, capture settings, top models/tools/MCP servers, and activity summari...

Billing Plans Free trial — 30 days, up to 2 seats, no card required. Every governance feature included. Team — up to 25 seats, self-service subscription. Enterprise — custom seats, SSO-enforced enrollment, contract terms; contact sales. Seats A seat is an admi...

API Everything the Admin Console does is an API — the console is just a client. Authentication Create an API credential in the console (Users & Teams → API credentials): you get a client ID/secret for the OAuth 2.0 client_credentials grant. Each credential car...

Admins manage the organization: policy, providers, people, billing. They do not need the Endpoint Suite — that's for developers. How Go to Users & Teams → Admins. Click Invite Admin, enter their name and work email. They receive an email with a passkey setup l...

Developers are the people whose AI tools you're governing. A developer invite grants no console access — it exists so their machine can enrol and their name can appear against their AI activity. How Go to Users & Teams → Developers. Click Invite Developer, ent...

Use this when someone can't sign in because their passkey is gone — a lost or wiped laptop, a replaced phone, or a passkey that was never finished. How Users & Teams → find the person in the Admins or Developers table → Resend passkey. They get a fresh setup l...

One action for "this person has left". Classic offboarding checklists cover email and VPN but never reach AI tooling — API keys sitting in tool configs, live logged-in assistants, MCP credentials, gateway tokens. How Users & Teams → Developers → Offboard on th...