keenKonnect is the builder execution environment in Konnaxion: a place to run real-world projects with a tight link between coordination, artifacts, and reproducibility.
Kintsugi is the “operate” layer: it makes many independent building tools behave like one coherent product, without merging everything into a monolith.
Builders typically operate with:
Kintsugi solves this by turning scattered tools into lanes that share:
Kintsugi is not “connect everything.”
It is a disciplined approach that guarantees four things:
One-roof experience
You should not feel like you’re jumping between products.
No dual truth
Anything that matters has a canonical identity and lifecycle inside keenKonnect, even if authored elsewhere.
Releases are real
The outcome of a project can be packaged and recreated later (audit, replication, handoff, long-term maintenance).
Hybrid by default
The same experience works for hosted deployments and self-host / on-prem environments.
Kintsugi v1 focuses on a small set of lanes (kept intentionally minimal):
Collaborative build docs
Specs, build logs, checklists, test notes—kept close to the project and captured as evidence when needed.
Inventory / BOM backbone
Parts, BOMs, revisions, substitutions—linked to tasks and releases so the physical build stays reproducible.
One search bar across what matters
Find parts, docs, tasks, artifacts, and references without forcing everything into one storage format.
Forge for “how we build”
Templates, scripts, test harnesses, build recipes—versioned knowledge that can be tied to releases.
If you want the exact “reference stacks” (which tools, which options), that lives in Kompendio:
When building becomes reproducible:
keenKonnect Kintsugi is the operating layer that makes physical-world collaboration as repeatable as software release—without demanding a single proprietary platform.
