Platforms · KoLo

One platform. Every intelligent system we build runs on it.

KoLo keeps institutional context, controls which AI may be used and how, connects intelligence to existing systems, applies governance to every action, and keeps working when a service changes or goes away.

KoLo is the runtime beneath every KODAITSU intelligent system. It is not a model and not a chatbot. It is the operating environment that makes a model useful, governed and survivable inside an institution.

Its research foundations are published by Kodasōken, our research division, under its own name.

KoLo runtime architecture layers

Five layers

What the platform does.

  • Institutional continuity

    Useful context maintained across workflows and operations.

  • Controlled AI access

    Local, specialised and external AI, per organisational requirement.

  • Workflow integration

    Intelligence connected to existing enterprise systems and processes.

  • Governance

    Permissions, approval and audit applied to intelligent operations.

  • Resilience

    Systems that stay useful when an AI service changes or is unavailable.

Reference architecture

Authority, protection, intelligence.

Guardian

Authority: identity, purpose, permissions and human approval. A gateway permission never confers institutional decision authority.

KAGE

Protection: containment, refusal at the memory and tool boundary, and recovery when something breaks.

KANATA

Intelligence: evidence, analysis and operational decisions connected in one view.

At a glance

Facts.

Deployment
On premises, institution-controlled cloud, national federation, or an authorised hybrid
Models
Local models first; specialised and external models by policy, per request, with audit
Authority
Explicit wherever consequences matter; people keep consequential decisions
Evidence
Append-only audit of actions, approvals and refusals
Research
Published by Kodasōken (株式会社KODA総研)

See it on your own material.A demonstration on approved or synthetic data.

We show a grounded answer with its source, an injected instruction refused at the boundary, and continuity when an external service is lost. Then your engineers drive.