KLOUDY / open-source
Build on the public protocol
Protocol and connector docs live in kloudy-open. Core vault and routing stay owned. Build on the public surface; do not expect the vault source.
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.
Build on the three public doors
The public CLI, MCP and SDK help builders connect through Kloudy. They are interfaces to one product, not copies of the private engine or vault. The SDK may power your own front door while the user retains control of scoped access.