King Klown Logo
The kOAinitiative
Konnaxion / Kintsugi

Kintsugi: one roof, one product

Kintsugi is the integration layer that makes Konnaxion feel like a single civic utility—across modules, across deployments, and across workflows. It is not “more features”; it is coherence.

What Kintsugi unlocks for users

  • One identity and one navigation across learning, deliberation, decision, and build.
  • One object model: credentials, proposals, decisions, projects, and artifacts fit together.
  • One continuity chain: outcomes carry forward instead of being lost between tools and committees.
  • One standard of accountability: what happened, why it happened, and what can be contested.

What Kintsugi prevents

  • Dual truth: competing records, conflicting dashboards, and “which spreadsheet is correct?”
  • Tool fragmentation: separate logins, separate vocabularies, separate accountability.
  • Institutional amnesia: decisions that cannot be replayed, audited, or learned from.
  • Locked-in dependency: when a community cannot migrate, self-host, or fork without collapse.

Same experience, different deployments

Kintsugi is designed so a community can run Konnaxion hosted, self-hosted, or in hybrid form—without becoming a different product each time.

Hosted

Fast onboarding and shared upgrades. Ideal for pilots and communities that want immediate capacity.

Self-host

Strong autonomy and local control. Ideal for institutions with strict governance and sovereignty needs.

Hybrid

Combine both: public surfaces where useful, local execution where required—without breaking workflows.

Where Kintsugi shows up

Kintsugi is not a separate product. It is the coherence layer applied to each module—so outputs move cleanly from one stage to the next.

Next: Kompendio

If Kintsugi is the unified experience, Kompendio is the public reference layer: integration maps, versioned charts, and the documentation that keeps the ecosystem governable.

Go to Kompendio