Kelivo: A Flutter LLM Client That Pushes Cross-Platform Limits
A Flutter LLM Chat Client. Support Mobile & Desktop.
At a glance
- What is it?
- Kelivo is an open-source Flutter chat client for LLMs that targets mobile, desktop, and even HarmonyOS. Its broad platform list and feature set are ambitious, but the AGPL license and reliance on third-party API relays deserve scrutiny.
- Who is it for?
- Adopt Kelivo if you need a single Flutter codebase for LLM chat across Android, iOS, desktop, and HarmonyOS, and you are comfortable with the AGPL-3.0 license and a project that is still evolving. Do not adopt it if you require a stable enterprise-grade solution or cannot accept the viral licensing terms for your distribution model.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Dart, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Kelivo Actually Solves
Kelivo addresses a practical pain: users who want a unified chat interface for multiple LLM providers without juggling several native apps. It is a Flutter application, so it targets Android, iOS, Windows, macOS, Linux, and HarmonyOS (the latter via a separate repository, kelivo-ohos). The README lists support for OpenAI, Google Gemini, Anthropic, and others, though the exact list is not detailed. This makes it a candidate for power users who switch between models and want a local client rather than a web interface. It also includes features that go beyond basic chat, such as MCP (Model Context Protocol) tool integration and built-in web search across many engines. The intended audience is clear: developers and tech-savvy users who want control over their LLM interactions and are willing to configure providers manually.
Architecture and Core Mechanisms
The repository is a standard Flutter app, with Dart as the primary language. The README does not describe the internal architecture, but the feature list implies a modular design: providers are abstracted, assistants are customizable, and tools are integrated via MCP. The mention of a built-in MCP Fetch tool suggests that Kelivo can act as an MCP host, allowing the LLM to call external tools during a conversation. Web search is integrated with many engines, from Bing to SearXNG, which likely means the client sends queries to these services and feeds results back to the model. The UI is inspired by RikkaHub, as acknowledged in the README, which suggests a modern, chat-centric layout. Without source code inspection, the exact data flow is unclear, but the design appears to be a client-side aggregator: it handles API calls, renders markdown, manages conversation history, and exposes configuration options for providers and tools.
Getting Started: Installation and Configuration
To run Kelivo, you download the latest release from the GitHub releases page or, for iOS, from the App Store (the README links to an App Store page). There is also a TestFlight link for beta testing. The README does not provide build instructions from source, but since it is a Flutter project, you would typically clone the repository and run `flutter run` after setting up the Flutter SDK. Configuration is not documented in the README snippet, but the feature list mentions QR code sharing for provider configurations, which implies a settings screen where you enter API keys and endpoints. Custom HTTP headers and bodies are supported, which is useful for providers that require extra authentication. For HarmonyOS, you must use the separate kelivo-ohos repository, not this one. The absence of a quick-start guide in the README is a gap; new users must rely on the app's UI or community support via Discord or QQ.
Limitations and Failure Modes
Kelivo has several genuine limitations. First, the README does not specify which providers are supported beyond the names OpenAI, Google Gemini, and Anthropic, so compatibility with niche or self-hosted models is uncertain. Second, the project is licensed under AGPL-3.0, which is a strong copyleft license; if you integrate or modify the code and distribute it, you must release your changes under the same license. This is a deal-breaker for proprietary or closed-source projects. Third, the HarmonyOS support is not in this repository but in a separate project (kelivo-ohos), which may lag behind the main repo. Fourth, the README mentions that Android background generation is an optional setting, implying that by default, generation may stop when the app is backgrounded, which could be a problem for long responses. Finally, the project is relatively young, with the latest release at v1.2.6 as of September 2026, so it may still have rough edges and breaking changes.
Alternatives and How They Differ
The most direct alternative is a provider-specific app, such as the official ChatGPT app or the Claude app, but those lock you into one vendor. Another alternative is a self-hosted web client like Open WebUI, which runs on a server and requires a browser, but offers a different deployment model: you host it centrally, and it can be accessed from any device without installing anything. In contrast, Kelivo is a native client that runs on your device, which gives offline access to your settings and chat history, but it requires maintenance on each device. Another category is desktop-only clients like GPT4All, which focuses on local models, whereas Kelivo is cloud-oriented. The key difference is that Kelivo aims for a single codebase across many platforms, including HarmonyOS, which few alternatives offer. If you need only one platform, a simpler client might suffice, but for multi-device users, Kelivo's breadth is its main draw.
Maintenance and Upgrade Cost
The project shows active development: releases v1.2.4, v1.2.5, and v1.2.6 were published in late August and early September 2026, with the last push on September 9, 2026. This indicates a regular release cadence, but it also means users must keep up with updates to get fixes and new features. The README does not mention a migration guide or upgrade path, so breaking changes are possible between minor versions. The reliance on third-party sponsors for free models (e.g., siliconflow.cn) suggests that some features depend on external services, which could change or disappear. The AGPL license means that if you redistribute modified versions, you must provide source code, which adds compliance overhead. For personal use, the upgrade cost is low: download the latest release and reinstall. For developers who fork the project, the cost is higher because they must track upstream changes and ensure their modifications remain compliant with the license.
Editorial conclusion
Adopt Kelivo if you need a single Flutter codebase for LLM chat across Android, iOS, desktop, and HarmonyOS, and you are comfortable with the AGPL-3.0 license and a project that is still evolving. Do not adopt it if you require a stable enterprise-grade solution or cannot accept the viral licensing terms for your distribution model. Before committing, verify the current state of the HarmonyOS port (since it lives in a separate repository), test your preferred providers and MCP servers against the latest release, and check the project's issue tracker for unresolved platform-specific bugs. Kelivo is a promising but young project; its value depends on your willingness to engage with its community and adapt to rapid changes.
Community notes