KLOUDY / surfaces
One Kloudy. Many surfaces.
One browser experience across desktop, tablet, phone, glasses-sized and watch-sized displays, with shared navigation commands: previous, next, select and back. Native apps adapt those commands to supported device inputs and connect Siri or Gemini Nano. Browser layout checks do not imply hardware certification. The web app and compact web widget are available here; native releases are handled separately. Google Home is currently parked.
Product overview. Public-page reading and KLDY preparation are available here. The connector, account actions and native apps described below are not connected to this site.
Less setup. More useful work.
For IDEs and bots: one CLI, one MCP, tools appear when needed.
Find with SEO/GEO, read FHIR for medical data or KLDY for other information, then select one scoped Toolbox tool when action is needed.
Passive local reads use no model calls. Narrowing 100 candidate definitions to 10 would mean 90% fewer definition fetches in that example; this is an illustration, not measured token savings.
OS voice is an optional input
A supported native host handles speech and passes final text into Kloudy. The engine handles resource narrowing and tool execution, and returns a concise result for the native host to present. Spoken yes does not approve a consequential action; confirmation is a separate step. IDE clients use the CLI or MCP without a speech detour.