LetKiteIndustrial intelligence
Hand repetitive, error-prone operations to AI without handing over control. LetKite puts one governed gateway between the AI your teams already use and the servers and equipment they run, so every action is scoped, approved where it matters, and recorded.
Run the fleet in plain language
Operators ask for what they need — “check disk on every production node”, “rotate logs where usage is over 85%”, “why did the nightly job fail on staging?” — and the AI carries it out across the fleet through LetKite.
- Group by tag. Nodes carry tags such as
prod,hkorstaging, and one request can act on a whole group. - Long jobs keep running. Backups, builds and migrations run detached on the node and survive dropped connections and gateway restarts.
- Changes wait for sign-off. Reboots, service stops, firewall changes and other risky commands need an explicit confirmation before they run.
- Every step on record. Each call is written to the audit log: who asked, which node, what command, what it returned.
Every line connected, no inbound ports
Edge devices on each production line dial out to the LetKite gateway, so the plant network never has to accept connections from outside. AI inspects and maintains equipment by line, site or role.
- Scoped by line and site. Line A, the warehouse and the QC lab can be separate groups with their own permissions.
- Contractors see only their assignment. A vendor's AI session reaches the machines it was granted and nothing else.
- Roll out in batches. Deploy and update edge devices across a site or a line at once.
An AI bastion host
Security teams already route human access through a bastion host. LetKite does the same for AI: a single, audited entry point with its own credentials.
One entry point
AI clients never hold server credentials. They sign in to the gateway with OAuth, and the gateway holds the keys to the nodes.
Least privilege
Nodes are reached through an unprivileged account. What the AI may do is the overlap of the client's scopes, the node's scopes and that account's rights.
Evidence for audit
One log line per call — who, when, which node, what command, exit code — gives compliance reviews a complete trail.
Learn more: Security
How a rollout works
Start with LetKite Lite
Install the open-source gateway on one server and enroll a handful of Linux nodes with a single command each.
Connect your AI
Add the gateway URL as a connector in Claude, Kimi or GLM. Begin with read and exec scopes; add write access where it earns trust.
Grow with LetKite
Bring in Windows machines, factory equipment and sites behind NAT, with folder-level rules, phone approvals and team roles.