Eighteen months ago I quit my job, moved back to Surabaya, and started building the tool I wished existed. Today, January 2, 2026, Konde Studio v1.0.0 is publicly available.
If you have been following along on X or in the small private beta, you already know roughly what this is. For everyone else, here is the short version: Konde Studio is a single macOS app that bundles project orchestration, multi-agent runtime, embedded server tooling, and a publishing layer into one local-first workspace. One license, one machine, no SaaS lock-in.
What ships in v1.0
Eight modules are live on day one:
- Projects — every codebase, server, and deploy target on one canvas. Tags, statuses, ownership, and a graph view that shows which agent is touching what.
- Agents — first-class support for Claude Code, Codex CLI, Cursor agents, and local Ollama models. Each agent gets a homebase directory, a memory file, and a working directory you can swap without restarting.
- Caster — turn one paragraph into ready-to-post drafts for X, LinkedIn, Threads, Bluesky, Pinterest, Facebook, and Instagram. Drafts land in a review queue. You hit "Post Now" when you are happy.
- DBarn — admin dashboard for the local Konde data store. Inspect tables, run SQL, edit rows, export CSV.
- Tunnels — embedded Cloudflare Tunnel. One click to share
localhost:3000with a real HTTPS URL. - KW Render — landing-page renderer that takes a JSON config and ships a styled page. Powers konde.io itself.
- Konde Docs — the platform you are reading this post on. Markdown in, fast HTML out, deployed at the edge.
- KSS — the module system that lets us (and eventually you) extend Konde Studio without us shipping every feature ourselves.
Themes
We shipped fifty-six themes, sourced from a render pipeline we built specifically for this. Two are the brand defaults — creamy for light mode and midnight for dark — and they ship enabled. The other fifty-four are one click away. Every Konde-rendered surface (Studio itself, Caster, KW Render, Konde Docs) reads from the same theme tokens, so picking seafoam in Studio paints your blog the same shade.
A real API
Every module ships with a real REST API behind an AKK (Agent Konde Key). Caster, DBarn, the project graph, the agent runtime — all of it is scriptable from any agent or external tool. Internal teams have been using these endpoints for months, but starting today they are documented and stable.
Read the API spec at /api/docs on any Konde service. The Scalar UI is interactive, the OpenAPI 3.1 spec is downloadable, and an llms.txt index lives at the root of every domain so your favourite agent can ingest the surface area without scraping.
Pricing that does not scale with usage
Konde Studio is one-time purchase. Pay once, use forever, on one machine. No seats, no per-agent metering, no AWS bill that grows with traffic. We genuinely believe the SaaS model is a poor fit for tools that solo founders and tiny teams use every day, so we walked away from it.
You can grandfather your license to one new machine per year (laptop death, upgrade, etc.) by emailing support. After the first year, optional update access is a small annual fee — but the v1 you bought keeps running indefinitely either way.
Who this is for
Konde Studio is built for solo founders and tiny teams of two or three. If you are running ten AI agents in parallel across three side projects, sleeping at 2am with the laptop open, shipping faster than seed-stage teams did five years ago — this is the operating system you have been duct-taping together for the last eighteen months. We made a real one.
What is next
Tomorrow we publish our 2026 roadmap. Konde Hosting, Konde Web v2, Email Sender, and a proper Render module are all on the docket. We will be shipping continuously from here — typically a release a week.
Thank you to the hundred private-beta builders who lived through the rough edges with us. v1 ships because of your bug reports.
Get Konde Studio at konde.io. Hit me up on X if you build something interesting.