Works with

Use the AI assistant you already pay for.

LayerOps does not ship its own chatbot. It connects the assistant your team already uses to your MSP tools, with the same permissions and approvals whichever one you pick.

At a glance

How each one connects.

Account sign-in means each person signs in with their LayerOps account, so there is no key to hand out. A key is one you create in LayerOps and can revoke at any time.

AssistantSign-inWhere it runs
ClaudeAccount sign-inWeb, desktop and mobile apps
Claude CodeAccount sign-in or keyTerminal
ChatGPTAccount sign-inChatGPT on the web
CodexKey, or account sign-inTerminal and code editor
Microsoft CopilotAccount sign-inMicrosoft 365 Copilot and Teams, through Copilot Studio
GitHub CopilotAccount sign-in or keyVS Code

Claude, ChatGPT, Codex, Microsoft Copilot, GitHub Copilot and Cursor are trademarks of their respective owners. LayerOps is not affiliated with or endorsed by them.

Same on every assistant

Switch assistants, keep the rules.

The assistant only asks. LayerOps decides what each person may see and change, so the rules stay the same whichever assistant your team picks.

Read the security model
  • Roles

    Each person's role decides which tools they can read and where they can propose changes, checked when they ask and again when anything runs.

  • Approvals

    A change waits in the LayerOps approvals inbox for someone with the right to approve it, unless an owner or admin has written an allow rule for exactly that change.

  • Audit log

    Every call is logged with the person behind it, allowed or blocked, whichever assistant they used.

Keep your assistant. Add the rules.

Fourteen days free and no card needed. Connect a couple of tools, set who can do what, and see what your team asks first.