Back to browse
GitHub Repository
45 starsGo

Aitori, see and govern the AI traffic leaving your machine

by deeptishukla22·Jul 27, 2026·2 points·2 comments

AI Analysis

●●●BangerBig BrainSolve My Problem

Intercepts browser-based AI traffic like claude.ai where standard proxies fail.

Strengths
  • Per-device CA allows inspection of encrypted traffic from desktop apps and browsers.
  • Fallback mode ensures requests still reach upstream if the gateway is down.
  • Open source with documented forwarding contract for vendor-agnostic integration.
Weaknesses
  • Requires installing a CA on every employee machine, which can be an IT hurdle.
  • Does not yet support mobile devices where much AI consumption happens.
Category
Target Audience

DevOps engineers and security teams managing AI usage

Similar To

mitmproxy · Zscaler · Netskope

Post Description

Hi HN, I work at TrueFoundry.

We built Aitori because AI traffic is getting harder for companies to control.

When developers call an LLM API directly, the request can be routed through a gateway. But tools like Claude Desktop, ChatGPT app, claude.ai call the model from the vendor’s backend. There is no endpoint setting you can point to your proxy.

Aitori is an open-source local proxy that runs on the employee’s machine and intercepts traffic to selected AI applications.

It uses a per-device CA, similar to mitmproxy, to inspect model and MCP requests and forward them to a gateway. Traffic to other applications is left untouched.

Once you can see the traffic, it stops being a black box. You can log it, apply policy, route it, or do whatever else you would with AI traffic you control.

It's Apache-2.0, and the forwarding contract is documented so it works with any gateway, not just ours: https://github.com/truefoundry/aitori/

Try it: curl -fsSL https://raw.githubusercontent.com/truefoundry/aitori/main/in... | sh then sudo aitori up --ui

Around all day to answer any questions.

Similar Projects