The assistants your people chose, seen and steered

Workplace assistants, desktop apps and local models arrive through licenses, personal accounts and one-click installs, often connected to company data through MCP servers and plugins. Geordie finds them on the endpoint and in the browser, separates the sanctioned from the rest, and guides people toward the tools you want them using without simply blocking the work.

Book a demo See how Geordie works

Assistants and desktop agents in this category

Microsoft Copilot
ChatGPT
Claude Desktop
Gemini
LM Studio
Mistral
Meta Llama
And more

The line between approved and unapproved is moving every week

People adopt assistants for productivity, preference or convenience, and the gap between the tools the organization provides and the tools people use keeps widening. Both sides need understanding, for different reasons.

The assistants you licensed

Connected to mail, documents and chat through connectors you configured, and sometimes to more through connectors people added themselves.
Used by people whose roles carry very different access, under one license and one set of settings.
Producing work and spend that nobody can yet tie back to a team or an outcome.

The assistants people chose

Personal accounts on consumer assistants, used for company work outside your data agreements.
Desktop apps wired to company systems through MCP servers people run on their own machines.
Local models downloaded and run with no review of what they are or what they reach.

Where everyday assistants turn into exposure

Customer incident

An agent coordinating with an outside agent

At a financial services and investment firm, Geordie surfaced an agent mining bitcoin while coordinating with an agent belonging to an external adviser.

From our research

Home-made connectors to company systems

One manufacturer told us it did not want ten people writing MCP connectors for the same service and hosting them on their own machines, which is exactly what tends to happen without a catalog.

Seen across customers

Local models nobody reviewed

Local model apps install in minutes and run entirely on the device, so they never appear in a SaaS inventory or cross a network control.

Seen where people actually use them

Assistants live on the desktop and in the browser, so that is where Geordie reads them, alongside the SaaS platforms behind the licensed ones.

Endpoint

The sensor finds desktop assistants, their MCP servers and plugins, and local model apps, and reads their configuration and sessions.

Cloud and SaaS

APIs cover the licensed assistants and the connectors configured for them.

Code

Direct connection to repositories, scanning agent configuration, skills and dependencies where they live.

Browser

The extension sees assistants and agents working inside web apps, including the ones signed in with personal accounts.

Understand the usage, then shape it

Usage

Know which assistants, which models and how many people

Geordie shows every assistant in use, the models behind it and the people using it, alongside the connectors each one reaches. That turns a conversation about shadow AI from guesswork into a list you can act on.

"We knew developers were using AI agents for coding, but we didn't know the full picture. Geordie showed us exactly which models were being invoked and by how many people." Senior Security Engineer, global private equity firm

Remediation, powered by Beam

Guide people to the tools you want them using

Beam works through the assistant's own configuration and context, so an assistant reaching for a connector outside the approved catalog can be pointed to the approved one, and an action that needs a person's decision can wait for it. The work continues, which is what keeps people from routing around the policy.

“Geordie's endpoint-based approach stood out because it gave us visibility close to where agent activity happens, without forcing us into a more complex gateway-based model.”

Sushil Dora Associate Director, OakNorth

One record across every kind of agent

Most estates run all five. Geordie covers them in a single inventory.

Questions about assistants and desktop agents

Geordie reads assistants on the endpoint and in the browser, so you can see usage whether someone is on a licensed seat or signed in with a personal account.

The endpoint sensor finds local model apps and the agents people build on them, which never appear in a SaaS inventory because they never pass through one.

Beam doesn't block by default, and it can guide an assistant toward the connectors and tools you've approved while keeping confirmation and enforcement for the actions that warrant them.

Geordie deploys through the MDM you already run, such as Jamf, Intune or Kandji, at user-level permissions, and the browser extension rolls out the same way.

Geordie holds SOC 2 Type 2 and ISO/IEC 27001 certification and is GDPR compliant, and no third-party LLM sub-processors handle customer data.

See the assistants your people are really using

We will show you every assistant and local model across your devices and browsers, what each one connects to, and who uses it.

Book a demo Explore the platform