kuku's strongest trust argument is architectural. Plain Markdown remains local, the code is public, and the project allows a path from fully local use to managed sync or self-hosted infrastructure.24 The current repository describes encrypted sync using workspaces, device/key envelopes, signed commits and encrypted objects so the managed server does not need plaintext note content.2
The privacy policy is more generic than the engineering documentation and should be read separately. It says local device data remains under the user's control unless the user chooses to sync or upload it, while optional cloud/sign-in features process the data needed to provide those services.6 It also says kuku may collect technical data such as device type, app version and crash logs and usage data needed to run or improve the product, and may use infrastructure or analytics providers.6 This is less absolute than older “no telemetry without explicit opt-in” roadmap language.4
AI processing also depends on configuration. The Free plan explicitly supports bring-your-own Gemini key, while planned paid tiers add remote AI requests and broader model-provider access.5 “Local-first” should not be interpreted as “all AI inference is local.”
Independent evidence is still thin. Product Hunt currently reports 4.5/5 from two reviews and around 950 followers.7 One visible reviewer praises open-source/local-first ownership and asks for a stronger plugin/extension ecosystem; the maker agrees that extensibility is still being stabilized.8 Two reviews are useful qualitative evidence but nowhere near enough to support a statistically meaningful satisfaction score.
OpenApps' repository analysis characterizes the project as actively maintained, open-source and young, with strong recent development activity but low maturity relative to established tools.9 Repository statistics and automated “health” scores are not product-quality benchmarks, so they are useful mainly as maturity context.
There is no robust current evidence for long-term sync reliability, recovery from difficult merge conflicts, AI edit quality across large heterogeneous vaults, battery/memory behavior on large datasets, enterprise administration, or support responsiveness.