What is seasagi?

SeasAGI describes itself as a local LLM API gateway made up of three connected parts. The client is a desktop application built with Wails, Go, and React that runs a local gateway on a user's own machine so API keys never leave that computer. A community server adds an optional cloud control plane with basic accounts, channel management, and usage tracking, and a separate enterprise server adds paid features like billing, multi tenant management, and an admin dashboard. The README says the client works fully on its own without needing the server at all. On the client side, the README lists a local API endpoint that behaves like the OpenAI API, so it can be dropped into any tool that already talks to OpenAI by changing the base URL. It also describes routing strategies that fall back between providers or spread requests round robin, a session stickiness feature that keeps a single conversation on the same model for thirty minutes, and automatic handling of rate limit errors by temporarily deprioritizing a channel that keeps failing. Other listed features include a cost tracking and optimization view, support for eight different provider integrations such as OpenAI, Azure, Anthropic, Gemini, and Ollama, request logging and error charts, automatic health checks on API keys, and a built in chat window for testing setups directly. The community server, described as self hostable, covers basic login, channel setup, combo management, and usage statistics, while the enterprise edition is closed source and adds billing through Stripe along with team and governance features. Licensing is split by component. The client is GPL 3.0, the community server is AGPL 3.0, and the enterprise server is closed source, so anyone reusing or modifying the client or community server pieces must keep those parts open under their respective licenses, while the enterprise code is not open at all. The interface supports Chinese, English, Japanese, and Korean, and the README notes that API keys are stored in the operating system's keychain rather than in plain configuration files.