A story in six orbits
Everything flows into Komok.
Komok is the end-game: a personal information system where plans, knowledge and memories share one connected model. Messages, mail, contacts, photos, video, podcasts, music, films, notes and tasks — everything a life accumulates — kept in one place, available offline, and organised with the help of language models that live inside it.
Small apps run inside it. It reaches out to the physical world through devices and services. An agent–organiser works on your behalf, with access to all of it.
None of that is built in one go. Each project below is a step on the way — and each one is useful on its own. This page tells that story. See what Komok looks like →
Orbit one · Everyday apps
Things I already use every day.
The closest orbit holds the applications that will dissolve into Komok over time. A book library, a video-to-notes converter, a system monitor: each solves one problem today and teaches what a shared model should look like tomorrow.
Orbit two · Kotlin foundation
What everything is made of.
Komok and its apps are Kotlin Multiplatform, so the building blocks have to exist in common Kotlin first: dependency wiring, YAML, UI trees, time, arbitrary-precision math, Markdown, document formats, Unicode, WebAssembly, JWT, Telegram. Where the ecosystem had a gap, a library appeared.
Orbit three · Build & deliver
How it gets compiled, checked and shipped.
A foundation this wide needs its own road to production. Plugins and GitHub Actions wrap the JetBrains Kotlin Toolchain; Skarb turns CI uploads into signed releases; kvik is the long bet — a build tool that compiles itself and its plugins into a single Kotlin/Native binary and speaks JSON to agents.
Orbit four · Agent harness
The hands that build all of this.
Most of the code in these orbits is written together with coding agents. kotgent keeps their sessions, tasks, plans and reviews next to the code — a harness around the harness. kortex gives them Kotlin skills, keemun gives them architectural memory, kotlm gives them a model, and MCP servers give them systems to act on.
Orbit five · Community
Where the knowledge goes.
Awesome Kotlin has catalogued the Kotlin ecosystem since 2015. It will gain an MCP server so agents can browse it too, and kotomka will turn talks into notes for it. kotbot serves the Kotlin community chats.
Orbit six · Operations
Keeping it running.
Komok and Skarb are self-hosted. kodkod watches their containers and restarts or recreates them when needed.
How it connects
One ecosystem, not a list.
- Libraries feed Komok. kotomi wires it, kotaml configures it, kinetica draws it, kotmark renders its notes, pombo brings its messages.
- Apps flow into Komok. kotomka, kotbusta and harmon start as standalone tools and become views over the same data.
- kvik builds; ktc-* and Skarb deliver. The toolchain compiles, checks, signs and publishes every library above.
- kotgent builds everything. The harness is where the other orbits are written, reviewed and shipped.
- Knowledge loops back. Awesome Kotlin catalogues the ecosystem Komok is built from — and will be queryable from inside it.
Hover any project on the map or in the lists to trace its connections. Repositories on this page: —.
What's next
Soon in Heapy.
Hollow points on the map are projects that exist locally but are not public yet. They will appear on github.com/Heapy as they stabilise.
Beyond repositories: an MCP server for Awesome Kotlin, kvik as the build tool for every project on this page, and the organiser agent inside Komok.