Introducing the Konde Store — install agent capabilities like browser extensions
KSS lets you ship features post-install via signed module packages. No more waiting for app updates to add capability. Today we are opening the doors.
Why we built our own changelog platform
Mintlify, ReadMe, and GitBook are all good products. None of them fit a multi-tenant publisher who ships docs, changelogs, and a blog from the same primitive. So we built kdoc — a single Cloudflare Worker that serves all three and ships in 200KB.
How we cut Claude Code token usage by 60% with RTK
We were burning $40/day on Claude Code at internal scale. RTK — a small Rust proxy that intercepts the most expensive tool calls and rewrites them — cut that to $14/day with no behavioural change. Here is how it works and why it is open source now.
Designing for solopreneurs not enterprise
Most dev tools target Series B engineering teams — and the design choices that work for that audience actively get in the way of the solo founder shipping at 2am. Here are the seven trade-offs we made deliberately, and why they cut against the consensus.
Agents 101 — building your first multi-agent workflow
A practical guide to chaining agents in Konde Studio. The four anti-patterns that make multi-agent workflows fall over, the three patterns that make them work, and the worked example we use internally for shipping product changes.
Launching Caster — your social media ghost writer
Caster takes one paragraph of intent and turns it into ready-to-post drafts for X, LinkedIn, Threads, Bluesky, Pinterest, Facebook, and Instagram. Now in private beta — here is the pitch and how to get in.
Why we built kdoc on Cloudflare Workers
kdoc serves docs and blog content for the entire Konde footprint at sub-50ms globally for less than five dollars a month. Here is the architecture, the trade-offs, and the three things that surprised us about Workers in production.
Konde Web — render landing pages from JSON
Konde Web takes a JSON config and emits a fully styled, fast, edge-deployed landing page in under thirty seconds. It powers konde.io itself, and starting today it ships as a public Konde Studio module.
How Konde Studio licensing works
One license, one machine, perpetual ownership, optional update access. Why we deliberately walked away from SaaS pricing for Konde Studio — and the answers to the four questions every new buyer asks us.
KDF — the design framework powering Konde
KDF is the token-based design framework we built to keep fifty-six themes in lockstep across Studio, Caster, KW Render, and Konde Docs. Tokens in JSON, classes in TSX, dynamic-resolved at render — here is the architecture and why it works.