A roadmap is a love letter to a future version of yourself. It is also a stick the internet beats you with when you miss a date. So here is ours, with the caveat that priorities can shift if our beta cohort tells us they should.
Q1 — finish the foundations
Q1 is about hardening v1.0. The eight modules that shipped on January 2 are complete enough to use, but several have rough edges that make new users think the app is buggy when in fact it is just incomplete in places we knew were incomplete. Top of the fix list:
- Sparkle integration for in-app updates. Right now you re-download the DMG and drag. By February we want an EdDSA-signed auto-update flow with a native progress UI.
- Onboarding rewrite. We watched a hundred first-time users fumble through the AKK setup. Q1 ships a proper first-launch flow.
- DBarn schema editor. Inspecting tables works. Editing the schema does not. By end of Q1 it should.
Q2 — Konde Hosting
This is the big one. Konde Hosting is a deploy target you can wire into Konde Studio that hosts your apps on infrastructure we run. The pitch is simple: the moment your project is ready to leave your laptop, you click Deploy and it is live at your-app.konde.app (or your custom domain) with a CDN, a database, a tunnel back to your local for debugging, and a proper logs view.
Why build this when Vercel, Railway, and Fly already exist? Because the hand-off between local development inside Konde and production hosting somewhere else is the second-biggest source of friction we see. By the time you have wired up Vercel envs, the GitHub action, the database URL, the secret manager, and the domain DNS, you have spent an afternoon on plumbing instead of features. Konde Hosting collapses that into one button.
Pricing will be usage-based — small projects free, real projects cheaper than Vercel — but the hosting interface itself is part of the Studio license. You do not pay extra for the panel, just for the compute.
Q3 — Konde Web v2 and Email Sender
Konde Web v2 is a structural rewrite of our landing-page renderer. v1 (which powers konde.io today) is a JSON-to-HTML pipeline. v2 adds a visual editor, component-level animations, A/B testing, and lead-capture forms that wire directly into your Konde data store. Pages still ship as static HTML at the edge — no React runtime, no client-side hydration tax — but you author them in a real editor.
Email Sender is exactly what it sounds like: a transactional and marketing email module that sits inside Konde Studio. Compose templates with the same theme tokens as the rest of your stack, send via your own provider (Resend, Postmark, SES), track opens and clicks locally. We are deliberately not running an email-sending service ourselves — that is a regulatory tar pit we are happy to outsource.
Q4 — KSS App Store and KW Render
KSS App Store. KSS is the module system. The App Store is the marketplace where third-party developers (and, eventually, you) can ship modules that extend Konde Studio. Think Raycast extensions or VS Code marketplace, but for the orchestration layer. We are seeding the store with a dozen first-party modules and opening submissions in October.
KW Render is our render module — a templating engine optimized for AI-generated content. Feed it a structured prompt, get back a static asset. We use it internally for our marketing pages, ad creative, and the cover images on this blog. Q4 makes it a public module.
Three things we are not naming yet
There are three modules in active design that we are not ready to commit to a public date on. They each tackle a class of problem we keep hitting: agent observability, content versioning across surfaces, and a kind of always-on background runner that we think changes how solo founders actually use AI day to day. When they are real, you will hear about them.
What is not on the list
- A web version of Konde Studio. We get asked this every week. The answer is no, not this year, possibly never. The whole point is local-first.
- A Windows or Linux build. We will get there. Not in 2026.
- An enterprise tier. Konde Studio is for solo founders and tiny teams. We are not interested in selling to procurement departments.
How we will keep you posted
Every Friday on this blog. Every release on the changelog. Every breaking change gets a migration note before it ships. If something on this list slides, we will say so.
The fastest way to influence this list is to join the closed beta at konde.io and tell us what is missing. We read every signup.