For the last two decades, desktop software has shipped features as monolithic releases. You wait six weeks for the next version, you download a new installer, you restart your app, and only then do you get the new capability.
Browser extensions broke that model in 2009. WordPress plugins broke it in 2003. Visual Studio Code broke it for editors in 2017. Today, with the launch of the Konde Store, we are breaking it for agent-driven workspaces.
What KSS solves
A Konde Studio install ships with a deliberately minimal core: project management, multi-agent runtime, embedded server, file watching, license, and the basics of agent memory. Everything else — Notes, Caster, Database Manager, Konde Web, Skills — is a module that you install from the Store, on demand, without restarting the app.
When you click Install on a module:
- KS desktop fetches the signed zip from
kss.equation.id - The Ed25519 signature is verified against the public key embedded in the binary
- You see a permission prompt: "Caster needs
net.fetch,db.write— Allow?" - The zip is extracted to
~/.konde/modules/{slug}/ - Schema migrations apply (each module owns its own
mod_{slug}_*tables, scoped, no collisions) - Lifecycle hooks run (
hooks/install.ts) - UI surfaces mount live — sidebar entries, settings tabs, agent skills — all without an app restart
The whole flow takes three to five seconds. Uninstall is symmetric — the module's files and tables are removed, surfaces unmount, and KS goes back to its previous state.
Why we built it as a closed store
You will notice a deliberate constraint in v1: anonymous access to the catalog is disabled. Every request to kss.equation.id requires a valid Konde license key in the X-KS-License header.
This is intentional. The Konde Store is a closed marketplace in phase one — every module is either built by us, or built by a vendor we have approached and vetted. We do not accept third-party submissions yet.
Why? Three reasons:
- Quality control. A module that crashes the host app is not a "bug in module X" — it is a bug in Konde Studio, in the user's mind. We need every shipped module to be solid before we open the floodgates.
- Affiliate alignment. Many modules will integrate with third-party providers (Caster.io, Mailgun, Vercel). We want to negotiate revenue share with each vendor before they show up in the catalog, not after.
- Security boundary. Signed modules from a curated set of authors is a defensible trust model. "Anyone can publish" is not, until we have a real submission review pipeline.
Phase 2 will open the door to vetted third-party modules with a proper submission flow. Phase 3 might open it further. We will see.
What ships in v1
Six modules at launch, all free:
- Notes — markdown editor with full-text search and per-project filtering
- Caster — ghost-writer for social posts (X, LinkedIn, Threads, etc.)
- Database Manager (DBarn) — admin UI for inspecting your KS-managed databases
- Skills — reusable prompt templates and agent-callable functions
- Snippets — code snippet library, multi-tag, agent-accessible
- Scaffolds — project templates (Next.js, FastAPI, Astro, etc.)
Each module has its own surface — Caster mounts /caster in the sidebar, DBarn opens via a user-menu shortcut, Skills appears as a sub-tab in the Agents page. Module manifest declares where it goes; KS desktop dynamically renders.
Roadmap
After v1 stabilizes, we are working on:
- Premium modules (one-time + subscription pricing)
- Pay-per-outcome modules (e.g., Konde Web Render at $0.10 per render)
- Settings UI per module auto-generated from
settings_schema - Vendor approach workflow for closed-store admission
Module distribution lives at kss.equation.id. The catalog API, the asset download URLs, the signature verification — all documented in the upcoming Konde Docs site (which itself runs on the same kdoc engine that powers this blog).