Platform
The architecture of a governed coordination layer.
152 Go microservices. 144 tenant-isolated databases. One Kinara Core that governs every cross-domain join.
Architecture
how the system is structured
Records move inward under mandate. Decisions move back out under accountability.
152
deployed services
144
isolated databases, one per service
4
governed domains
72h
records held at edge, offline
Core components
what each layer does
Four layers. One rule.
Domain services
Each domain owns its own services and databases.
Health runs 40 services against its own 36 databases. Agriculture the same. No service in one domain can query a database in another. The separation is enforced at the connection layer, not the application layer.
Kinara Core
The governance layer that permits and records every cross-domain join.
When a health service needs to raise a logistics question, it sends the request to Kinara Core. Core checks the lawful basis, verifies the requestor, permits or denies, and writes the audit entry. The join happens through Core, never directly between domains.
Edge runtime
Records created where connectivity is worst.
Field workers on feature phones. Clinics without reliable data connections. The edge runtime holds records locally, queues them, and reconciles the moment connectivity returns. No record is lost. No entry requires a live connection at the moment of capture.
Kinara AI
Operational intelligence without clinical authority.
Kinara AI supports multilingual intake, translation, care navigation, documentation, and operational insight. Licensed clinicians remain responsible for diagnosis, prescribing, and treatment.
Technical choices
why we built it this way
Go. PostgreSQL. No shared databases.
Go microservices
Low memory, fast startup, suitable for constrained environments. Each service is independently deployable and independently failure-isolated.
PostgreSQL per tenant
Every tenant gets its own database. Row-level separation is not sufficient for data that different ministries must never see together.
WhatsApp and SMS inputs
The entry point is the device the worker already has. Not a custom app, not a tablet programme, not a funded device rollout.
Audit log as first-class output
The log is not a side-effect. It is a primary output of every cross-domain operation. It cannot be disabled, altered, or selectively written.
See the running system.
A 45-minute technical briefing. We will walk through the architecture live, not on slides.
Request a briefingKinara OS is built and owned by Klinova.