Introducing KOllama: A Kotlin-First Ollama Client with Full Type Safety

If you're working with Ollama in a Kotlin project, you've probably wished for a client that feels truly native – one that embraces coroutines, sealed classes, and the type safety we all love. That's exactly why I built KOllama – a Kotlin client for Ollama, powered by Ktor Client and designed to make local LLM interactions delightful. In this post, I'll walk you through what makes KOllama different, show you how to get started, and share some of the design decisions behind it. Why KOllama? Ollama's REST API is simple, but using it from Kotlin can be messy: You have to manually map fields (like prompt_eval_count to something readable). Streaming responses require manual SSE handling. There's no built‑in type safety – you're dealing with raw JSON or Map s. KOllama changes that by providing: ✅ Full type safety – every request and response is a Kotlin data class. ✅ Kotlin‑first API – suspend functions, Flow for streaming, DSL builders, and sensible defaults. ✅ Semantic naming – fields like