Start here
If you are evaluating Kronroe, begin with the docs landing page and the quick start for your stack.
The practical details, without the marketing fog.
These are the questions people usually ask before adopting Kronroe: what it runs on, how private it really is, what it costs, and how it fits into existing workflows.
Most asked
Install, privacy, supported platforms, and licensing are the four questions that usually matter first.
Need the shortest path?
Open the playground if you want to see the memory model working before you read the full docs.
How do I install Kronroe?
Use the language-specific package for Python or Rust, or follow the docs for the MCP server and WASM builds. Each path is documented so you can choose the surface that matches how you ship.
Does data leave the device?
No. The core positioning is on-device and local-first, with no cloud dependency for the memory engine itself. If a workflow needs sync or hosting later, that is a separate design choice rather than a requirement of the core engine.
What platforms are supported?
Rust, Python, iOS, Android, and WASM are the current surface area the homepage calls out. That keeps the product close to the languages and runtimes people are actually building in.
Is Kronroe open source?
Yes, with a commercial licence available as well. That will stay visible in the site footer and docs so the project is easy to evaluate from both a technical and licensing perspective.
How does bi-temporal memory help?
It keeps valid time and recorded time separate, which makes corrections, history, and point-in-time queries much clearer. That matters when you want to know what was true then, what was recorded then, and how a fact changed over time.
Where should I start if I am evaluating the product?
Start with the docs landing page, then read What is Kronroe? and one quick start guide. That gives you the product thesis, the setup flow, and the API surface without making you read the entire site first.
Can I use it in a commercial product?
That is exactly the case the site is designed to support. The docs and licensing language should make it clear how to adopt Kronroe in a real product, not just a demo.
Need a faster answer?
Jump straight to the docs or try the playground if you want to see the memory model in action.