A program dashboard,
named after a snack.
Open a clementine and the structure is instantly obvious: a handful of clean segments, each complete on its own, together making one thing. No knife, no peeler, no manual.
That's the product philosophy in a fruit. Your program is a few strategic pillars — segments of a whole. Every one should be visible at a glance, separable when you need to look closely, and part of one obvious shape when you zoom out. Most tools bury that structure under tabs, sub-tools, and configuration; klementyne keeps it in your hand.
And a clementine is gone in ten seconds — which is exactly how long your next status update should take.
What klementyne believes
Your work data is yours — architecturally, not contractually. Promises live in privacy policies; architecture lives in the product. Klementyne keeps your portfolio in your browser and runs its AI on your device, so the question "who can see my data?" has a structural answer: nobody, because there's nothing to see it with.
The report is a by-product, not a job. If a tool already holds your pillars, tasks, updates, blockers, and capacity, then a status report is just a rendering of what it knows. You shouldn't write it; you should read it, fix a sentence, and send it.
AI should work where the data lives. The most useful assistant is the one you can hand everything to — and the only assistant you can safely hand everything to is one that never phones home. On-device AI isn't a compromise here; it's the unlock.
A suggestion should show its work. "Quiet for 9 days" is a diagnosis, not help. Klementyne reads a task's own updates, blockers, and history before it proposes anything, and it decides on its own whether a task needs your attention at all today — then shows the exact lines the suggestion came from, so you're never asked to trust a black box.
Leaving must be easy. Everything exports — Excel, CSV, Markdown, diagrams, straight pushes to Confluence and Jira. A tool that holds your data hostage doesn't deserve it. Confidence in the product should be the only switching cost.
Who it's for
Coordinating a roadmap and shipping product used to be two different jobs. The bet ledger makes them one: an idea only counts once it's written as a falsifiable bet — a success threshold and a kill threshold, locked in before the work starts — and it isn't finished until it has a permanent scale, kill, or pivot decision behind it.
That's the shift from TPM to builder PM: from "I coordinated the launch" to "I called the outcome, in writing, before I saw it." klementyne keeps the record so that track record is provable, not remembered.
Why it's free
Honestly: because the architecture makes it nearly free to give away. Local-first means your browser does the storage and your device does the AI — there's no per-user server bill to recover. And since your data never reaches us, we couldn't monetize it if we wanted to. No ads, ever.
If paid plans arrive one day, they'll be for things that genuinely cost money to run — think encrypted team sync and organization-wide roll-ups — priced for organizations. The single-player app stays free, and because everything exports, nothing you build in it is ever leverage against you.
Ten seconds from now, you could be looking at your next status update.
Open klementyne