Aikido

See every AI tool your developers use

Developers add AI assistants, models, and MCP servers faster than security can track them. Aikido shows you exactly what's running on each workstation, then lets you block, approve, or set policy per tool and team.

Trusted by 50k+ orgs
|
Loved by 100k+ devs
|
4.7/5
THE PROBLEM

AI tool adoption is growing faster than you can govern it

Your developers are already using AI tooling. But you don't  know which tools they are using or where they are using them your codebase.

NETWORK VS WORKSTATION LEVEL

Network blocks aren’t bullet proof, Aikido protects at the workstation level

What a network block sees

An IP address, nothing more
No models or MCP servers
Bypassed on a personal hotspot
No audit trail
Aikido

What Aikido’s device protection sees

The exact tool in use
The exact LLM model or MCP server
Corporate or personal account
A record for compliance
COVERAGE

Get a view of your entire (AI) stack

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
NPM
Package registries
Maven
Package registries
PyPi
Package registries
NuGet
Package registries
Go
Package registries
Ruby
Package registries
Rust
Package registries
PHP
(Soon)
Package registries
JetBrains
IDE extensions
VS 
Code
IDE extensions
OpenVSX
IDE extensions
Firefox
Browser extensions
Visual
Studio
IDE extensions
Chrome
Browser extensions
Cursor
IDE extensions
Windsurf
IDE extensions
Gemini
AI models
OpenAI
AI models
Github
Copilot
IDE extensions
xAI
AI tools
MCP
Servers
AI tools
Claude Code
AI tools
Skills.sh
AI tools
HomeBrew
Package registries
RubyGem
Package registries
Hugging Face
AI tools
DEMO VIDEO

Aikido Device Protection
explained in under 4 minutes

Known malware is blocked before it touches the filesystem.
Not flagged after. Not quarantined later. Stopped before it's downloaded.

See Aikido in action

Enter your work email to view the video

Watch Video
CAPABILITIES

Everything you need to detect shadow AI in your organisation

Full AI discovery

Every AI tool, the specific model, every MCP server, and AI-powered IDE and browser extensions.

Sees personal accounts too

Workstation-level traffic observation catches AI usage on corporate licenses and personal accounts alike.

Fully block, don't just observe

Govern AI tools with real enforcement, not a dashboard that only reports.

Group-based policies

Different rules for different teams. Strict where it needs to be, flexible where it doesn't.

Request & approval workflow

Developers request a new AI tool, you accept in one click. Without having to create and manage tickets.

Continuous monitoring

Ongoing, not a point-in-time audit. Whenever a new AI tool shows up, you will know.

Protect your developer devices from Shadow AI

BEHIND THE ENGINE

What makes Aikido’s device protection so powerful

Powered by Aikido intel, the threat intelligence engine

Aikido Intel monitors the open internet, detecting malware in open-source ecosystems within minutes.

View our Intel feed

Backed by a team of world class security researchers and experts

Aikido intel & device protection is supported by a dedicated team of security researchers and AI engineers.

The team behind the discovery of shai-hulud.
Faq

FAQs about Device Protection

How are malicious packages detected?

Every package published to npm, PyPI, and other registries is scanned automatically by Aikido Intel using a combination of static analysis, behavioral rules, and AI. Suspicious packages are flagged and reviewed by Aikido's in-house research team. Confirmed threats are pushed to every connected workstation in real time. For a live view of what we're detecting, visit the Aikido Intel feed.

How does Aikido device protection compare to using a private registry (for example, NuGet)?

Aikido device protection offers broad protection across many ecosystems, while a private registry is best when you need tight control within one specific ecosystem.

How does Aikido device protection work technically?

It intercepts HTTP traffic at the kernel level, including TLS-encrypted traffic by adding a local CA, and it is designed to work in a chain with other traffic inspection solutions.

More in depth info: https://help.aikido.dev/aikido-endpoint-protection/miscellaneous-aikido-endpoint/how-does-endpoint-protection-work

How does Aikido interact with our existing EDR?

Aikido Endpoint operates at the package, extension, and AI layer. It complements EDR rather than replacing it. EDR catches threats after they are running. Aikido stops them from running in the first place.

How is this different from blocking AI tools at the network level?

Network blocks are coarse and easy to route around. A developer on a personal hotspot can bypass them entirely. Aikido operates at the workstation level, per developer, per tool. You get granular control and a real audit trail.

What is minimum package age and why does it matter?

Minimum package age holds installs of recently published packages. The default is 48 hours. This stops a common supply chain attack. An attacker publishes malicious code to npm or PyPI and tries to get developers to install it before the community can flag it.

What ecosystems are covered?

We are constantly adding new ecosystem coverage. You can find the current coverage in-app or in the docs.

What if developers use personal accounts or consumer AI tools?

Aikido observes traffic at the workstation level regardless of which account a developer is using. If a tool is making outbound calls to an AI service, Aikido sees it. This is true whether it is a corporate license or a personal account.

Does Aikido's device protection have Windows and Linux support?

Device Protection is available on Windows. Linux support will be available by early Q3 2026.

What is the difference between Device Protection and a virus scanner like Nortons?

Traditional virus scanners such as Norton, McAfee, and Crowdstrike Falcon primarily inspect compiled binaries for known malware signatures, while Aikido Endpoint focuses on the modern, non-binary attack surface, including JavaScript packages, IDE extensions, browser plugins, and AI skills marketplaces. These plain-text, interpreted artifacts can slip past traditional scanners, yet still run with full access to the developer environment and, by extension, the software supply chain.

Protect every install. Build fearlessly.

Developer devices are prime targets, secure yours.