Koine · decision intelligence

Defensible decisions from the data you already have.

Most organisations don't lack data — they lack decisions they can defend. Koine reads across the systems you already run, returns cited answers, and gates every write to source through a dry-run, approval, and audit pipeline.

postgres · mysql · sqlite · sql server · sheets · arcgis · rest · csv · cspro

Your data lives in twelve systems. The last quarterly report took three weeks. The audit trail behind it is a Slack thread.

systems
12+
Average source systems an analyst joins by hand for a single board report.
cycle time
3 wks
Median time to produce a cross-system report on quarterly cadence.
defensibility
0
Auditable trace from board slide back to source row, in most institutions.
How it works

Connect once. Ask in plain English. Defend the answer.

Koine is one platform with three roles: read across your systems, compose answers with citations, and govern any change before it touches source.

Step 01

Bind your sources.

Read-only by default. Postgres, MySQL, SQLite, SQL Server, Google Sheets, ArcGIS, REST, and bespoke connectors via the Bridge agent for systems behind your firewall.

  • Schema introspected on bind — Koine knows your tables, you don't repeat yourself.
  • Secrets encrypted per tenant. Nothing leaves your VPC unless you say so.
  • Existing systems keep working. Koine never replaces, only orchestrates.
connectorcivil-registration · postgres
moderead · write-via-tools
tables142 introspected
last synclive · 2s ago

postgres read tier-2 writes pii-aware
Step 02

Ask a question.

An analyst, a director, or your own product. Koine picks the right tools, runs them against your bound sources, and returns an answer that cites the rows it read and the SQL it ran.

  • Four-tier prompt stack: sealed system rules, your house voice, per-role personas, session overrides.
  • Multilingual — English, French, Portuguese. Add a locale, the AI follows.
  • Every reply lists tools called, citations, and the user-context that shaped it.
› Top 10 LGAs by birth registrations, Q1 2026?

toolcrvs.births.aggregate
connectorcivil-registration
rows scanned2,481,930
cite12 facts · sql shown
latency1.4s
Step 03

Govern every write.

Anything that changes source data goes through dry-run → approval → audit. Tier 1 (low-risk) executes after preview. Tier 2 needs one approver. Tier 3 needs two distinct approvers.

  • Dry-run tokens are HMAC-signed, single-use, expire in 15 minutes.
  • Approval queue scopes to tenant; staff can't approve their own proposals.
  • Compensating actions wired in: every write knows how to undo itself.
proposalcrvs.births.bulk-correct
tiertier-2 · 1 approver
affected214 rows · all reversible
requesteda.olawale · 2 min ago
expiresin 12 min

approve reject request changes
Step 04

Defend the decision.

Every answer and every write is logged with the four-part trace: tool, data, prompt context, approver. Replayable, exportable, kept for seven years by default.

  • Read audit and write audit are separate streams — different retention, different exports.
  • Golden-set evals run on every prompt change so regressions are caught before deploy.
  • Audit envelope export is JSON or PDF, signed with your tenant key.
decisionbudget reallocation · 2026-Q2
tool usedfinance.allocations.compose
data read3 connectors · 41,802 rows
approved by2 of 2 · cfo + audit
exportedsigned envelope · 814 kb
The four-part trace

The unit of value is a defensible decision, not a dashboard.

BI tools have the data. Copilots have the language. Koine wires them together with governance — so the answer survives the meeting, the audit, and the court.

01 · TOOL

Which tool ran.

Tools are typed, versioned, and tenant-scoped. Every invocation records its parameters and its return shape.

02 · DATA

Which rows were read.

Connectors log table, query, and row count per call. PII fields are tagged and can be redacted from the trace.

03 · PROMPT

Which context shaped the answer.

System rules, tenant voice, role persona, session overrides, ContextFacts cited — all snapshotted with the response.

04 · APPROVAL

Who signed off on any write.

Tier 1 inline, Tier 2 single-approver, Tier 3 dual-approver. Compensating actions ready if a decision needs reversing.

Where it lands

One engine. Different connector packs.

Verticals ship as bundles of connectors, tools, prompts, and personas. The core platform is the same — the domain knowledge is what changes.

vertical · live

Census Intelligence

Register-based + traditional enumeration. Stitch civil registration, tax, NIMC, health into one statistical population register.

vertical · live

Civil Registration (CRVS)

Births, deaths, attestations. Indicator calculators, fuzzy duplicates, governed exports. NIN-pipeline aware.

vertical · alpha

Health Systems Intelligence

HMIS + lab + pharmacy + insurance. Cross-system patient query with PII residency rules baked in.

use case

Tax & revenue cross-checks

TIN ↔ VAT ↔ PAYE ↔ CIT. Find taxpayers visible in one system but not the others.

use case

Subnational government

LGA dashboards stitching multiple MDAs. Decision packets sent to commissioners with the trace attached.

use case

Multilateral funder oversight

Read-only governance windows into grantee systems. Auditable without ever copying their data.

use case

Bank & fintech KYC

Match identity across registers, sanctions lists, and internal CRM. Every lookup logged with reason code.

use case

Land & property registers

Title + survey + valuation joined on parcel id. Conflicts surface as Tier-2 reconciliation proposals.

use case

Education sector

NECO/UTME/JAMB + school registers + funding. Track outcomes across the cohort, not the form.

Built for institutions that move in quarters, not sprints.

Residency, retention, RBAC, PII handling, and audit retention are first-class. Not bolt-ons. Designed for ministries, regulators, and multilateral funders before chasing the global market.

RBAC tenant-defined granular roles PII field tagged · redacted in trace RESIDENCY data stays where bound AUDIT 7-year default retention SSO SAML & OIDC

Postpay. Invoiced quarterly.

Built for procurement-led buyers. We bill per active tenant + per million tool calls. Trial is bounded — start a workspace seeded with sample data for your sector.

See pricing Talk to sales →

Bring a database URL and one question you can't yet answer quickly.

Thirty-minute demo. We bind your read-only source live, show Koine compose the answer with citations, and walk you through the four-part trace on a sample write.

Book a demo → Explore verticals