the company ai supply line
Your team's AI works on day one.
Standard issue.

Your people get the tools they need, and nothing they shouldn't. No access tickets, no approval queues, no logins left open after someone leaves. One install connects every AI client to your company's tools, under rules you set.

your client
> claude
● connected · wardyn
> find my customers in crm
↳ tools.crm_list_customers
wardyn gateway
middleware
pipeline · 9 stages
usage logger
auth
budget
prompt sanitizer
arg sanitizer
pii filter
poisoning protection
schema pinning
crash guard
live controls · 5
skill screening
downstream proxy
live alerts
cost metering
sessions
company backend
crm api · 200 ok
{ "customers": 3,
"region": "emea" }
mcp server
downstream · n8n · ok
{ "server": "n8n", "tools": 33 }
slack
alert · delivered
{ "channel": "#sales", "status": "sent" }
clients claude code claude desktop opencode cursor kimi copilot custom agents • • • many more
every request

Nothing to configure. Nothing to remember.

You write no policy files and approve nothing by hand. Every call passes the same nine checks before a tool runs. Hover a stage to see what it stops.

01

Usage log

02

Live auth

03

Budget

04

Prompt safety

05

Arg hygiene

06

PII filter

07

Poisoning guard

08

Schema pin

09

Crash guard

what you get

Your team gets to work. You keep the controls.

Nobody files a ticket for a tool. Nobody keeps access they no longer need. You grant, change, and remove all of it from a browser.

Your team installs one thing

Every approved tool, skill, and prompt arrives through it. Nobody hunts for a key or configures a second client.

Remove access the moment someone leaves

The next request stops. No nightly sync, no keys left on a laptop.

New hires start with the right tools

Assign a role. The tools that fit it appear.

A bad skill never reaches your team

Every skill is screened before release. Every version is kept, so one step undoes a mistake.

See what your AI is doing

Invite, assign, revoke, and review from the browser. No config files, no redeploy.

Add a tool without opening it to everyone

Connect any MCP server once. Each role sees only the tools it should.

one-line setup

Paste one line. Every client configures itself.

No per-machine setup and no config files to share. Pick the path that fits your team. Wardyn configures the rest.

Choose an install path

Claude Code, Claude Desktop, opencode, Cursor, Kimi, Copilot, Codex, and other MCP clients use the same governed endpoint.

Agent-first endpoints: llms.txt · connect · doctor · skills

GATEWAY_PUBLIC_URL=https://wardyn-ai.com \ npx bayzat-gateway onboard YOUR_TOKEN
curl -sSL 'https://wardyn-ai.com/install?token=YOUR_TOKEN' | bash
{ "mcpServers": { "wardyn": { "command": "npx", "args": ["--yes", "mcp-remote@0.1.38", "https://wardyn-ai.com/mcp"] } } }
export WARDYN_INSTALL_TOKEN=YOUR_TOKEN codex mcp add wardyn --url https://wardyn-ai.com/mcp --bearer-token-env-var WARDYN_INSTALL_TOKEN

Codex does not run embedded commands. Paste each line manually.

pricing

One number.

You only pay for what's issued.

$2/mo

per issued MCP

Setup is free. Revoke a leaver and the meter stops.

works with Claude, ChatGPT, and any MCP client

issue a seat
+1
revoke a seat
-1
unissued seat
0
supply: live wardyn v1.0 issued across your team
how it works

Metered by seat, not by team.

The meter runs only when a seat is active.

Issue a kit to a seat and the meter counts it. Revoke it and the meter stops. Setup is free. Unissued seats cost nothing.

issued +1
issued -1
issued 0
FAQ
What is Wardyn?

Wardyn is the company AI supply line: it packs your company's AI skills, context, and connections into kits and issues them to each team — installed once, always current, revoked the instant someone leaves.

How do I share AI skills, prompts, and tools my company built with my team?

Assemble them into a kit in Wardyn and issue it to the teams that need it. Each person installs one connection in the AI they already use, and from then on everything you publish reaches them automatically.

How do I update AI capabilities shared with my team?

Publish the new version in Wardyn. Every issued seat is current instantly — employees don't download, re-install, or do anything at all.

What is an MCP?

An MCP (Model Context Protocol) server is the standard way to give AI tools like Claude and ChatGPT access to skills, files, and systems. Wardyn packages everything your company built into one managed MCP per person, so each employee connects once instead of juggling many.

What happens when someone leaves the company?

You revoke their kit with one click and access ends immediately. There's nothing to collect and nothing left behind on personal accounts.

How much does Wardyn cost?

$2 per issued MCP per month. Setup is free — you only pay for what's issued.

Which AI tools does Wardyn work with?

Claude, ChatGPT, Claude Code, and any client that supports MCP with OAuth. Employees keep using the AI they already have.

Can I issue an MCP to an AI agent?

Yes. An agent takes a seat like any person: you issue it a kit, it connects through the same managed MCP, it's billed at the same price, and you revoke it the same way — one click, access ends immediately.

Do employees have to install anything?

One connection, once. After that, updates arrive on their own — there's nothing to maintain and nothing to remember.