What is kiro-stack?

Kiro-stack, this fork, is a self-hosted proxy manager designed for people who run multiple AI service accounts and need each one to connect through its own separate proxy. It sits between your API clients and an AI service, routing each account's traffic through its own designated network exit point so the accounts appear to originate from different locations. The system is built around Clash subscription support, Clash being a network routing tool that loads a list of proxy nodes from a subscription URL. Each account in the admin panel can be bound to a specific node from a loaded subscription, to a per-account HTTP or SOCKS5 proxy from commercial services such as Bright Data, Rola, or Oxylabs, or to a global tunnel proxy. If the primary route fails with a connection error, the system automatically falls back through a configured fallback chain rather than going direct. Several reliability features are included. A component called DNSGuard checks whether DNS resolution results look tampered with, treating results that resolve to loopback or private addresses as a sign of pollution, and retries through alternative DNS-over-HTTPS providers. Tunnel proxies that include a session placeholder in their URL automatically rotate to a fresh session after repeated failures. A circuit breaker panel lets you configure failure thresholds per account to stop a broken proxy from continuing to send requests, with manual controls to open or close the breaker for a single account. The admin panel also exposes an API compatible with Claude and OpenAI client libraries, so existing tools can point at the local server without code changes. Everything runs as a single Docker container by default in the current version, with an older two-container layout still available for standalone debugging. The project is written in Python and is a fork of an existing kiro-stack project, with a changelog tracking each version's additions. The full README is longer than what was shown.