Skip to content

The evidence engine

Turn sources that disagree into answers you can defend.

Khora connects your documents, systems, and external data. It resolves what they say, shows where they conflict, and keeps every number tied to its source.

One product, configured per workflow. Proven on datasets of tens of millions of records.

Research workspace · North Harbor Opportunities IV

Reporting period: Q2 2026

Illustrative workflow and data

Portfolio exposure

Current view and material changes

Reviewed

Net asset value

$842.6M

Connected sources

12

Items for review

3

StrategyQ2ChangeStatus
Private credit 31.8% +4.2 pts Reviewed
Asset-backed 24.1% +0.8 pts Current
Special situations 18.5% Definition changed Review
Cash and equivalents 8.9% −1.5 pts Reviewed
01

Documents and files

PDFs, presentations, spreadsheets, scans, statements, and data-room materials.

02

Internal systems

Databases, warehouses, CRM, ERP and accounting systems, email, and document stores.

03

External data

APIs, filings, registries, market and reference data, and licensed feeds.

04

Websites and portals

Authorized web sources, with the pages retained as evidence.

The problem

The sources disagree. The work continues.

The same fund, company, or property appears under different names, definitions, and dates in every source. Reports get revised. Totals don't match. And the spreadsheets that reconcile them can't explain themselves.

Without Khora

Every review starts over.

  • Re-collect facts from revised reports and systems.
  • Re-match entities with inconsistent names and identifiers.
  • Re-reconcile metrics that define things differently.
  • Re-build the trail when someone asks where a number came from.

With Khora

Work done once stays done.

  • Sources stay connected in one place.
  • Entities and claims stay resolved, with disagreements preserved.
  • Corrections and approvals stay on the record.
  • Reviewed results flow to workbooks, reports, APIs, and feeds.

What Khora is used for

Five hard problems. One engine.

Most broken data workflows come down to a few recurring problems. Khora is built for them, and configured with your sources, your definitions, and your review process.

01

Track what changes.

Documents get revised. Positions shift. Definitions drift. Khora tracks entities and metrics across every version and shows exactly what changed, with the source alongside.

Used for

  • Fund and disclosure tracking — exposures, strategies, and metrics across prospectuses, quarterly reports, and revisions.
  • Clinical trial tracking — trials across registries, protocol amendments, publications, and conference disclosures.
  • Regulatory filing monitoring — what a filer said this quarter, last quarter, and what moved in between.
Fund comparison · Reporting periods Illustrative

Private credit · Q1

27.6%

Quarterly report · p. 17

Private credit · Q2

31.8%

+4.2 percentage points

FundPeriodChangeEvidence
North Harbor IVQ2 20267 changes12 sources
Atlas Credit IIIQ2 20262 changes9 sources
Fieldstone IncomeQ1 2026Current15 sources
02

Reconcile what disagrees.

The ledger says one thing. Management reporting says another. Khora keeps reported figures, adjustments, and assumptions separate, and pinpoints where and why they diverge.

Used for

  • Deal diligence and modeling — a target's ledger, management reports, and data room in one defensible model.
  • LP capital account reconciliation — capital accounts, notices, and valuations across GPs in one reviewed view.
  • Royalty and rights reconciliation — entitlements against statements across contracts, catalogs, and payments.
Deal model · Reconciliation review Illustrative
MetricReportedReviewedStatus
Revenue$128.4M$128.4MMatched
Adjusted EBITDA$34.9M$31.2MReview
Bookings$146.8M$138.1MConflict
Cash sales$119.7M$119.7MMatched

Definition requires review

3 sources

Management reporting includes one-time implementation revenue that is excluded from the reviewed operating definition.

03

Resolve what has no shared key.

The same property, company, or owner appears in ten sources under ten names. Khora links the records that belong together and flags the matches it isn't sure about instead of guessing.

Used for

  • Title and chain of title — deeds, liens, and encumbrances across county records, without papering over the gaps.
  • Beneficial ownership — corporate structures and ultimate owners across registries, filings, and watchlists.
  • Real-estate portfolios — properties, entities, and owners resolved across registries, filings, and portals.
Portfolio review · Ownership relationships Illustrative
Harbor Portfolio18 assetsReviewed
245 West 18th StOffice4 sources
80 Franklin AveMixed use6 sources
120 Mercer LLCEntityReview
Cypress HoldingsOwner8 sources
04

Monitor what must stay true.

A covenant, a mandate, a thesis: a claim someone has to keep checking against new evidence. Khora re-runs the check when new material arrives, with the evidence attached.

Used for

  • Covenant monitoring — covenant calculations across credit agreements, amendments, and compliance certificates.
  • Investment thesis tracking — a thesis's claims pinned to evidence, confirmed or contradicted as the record grows.
  • Mandate compliance — portfolio positions checked against mandate restrictions, with breaches traceable to source.
Covenant monitor · Facility B Illustrative
CovenantRequiredQ2Status
Net leverage≤ 4.50x4.12xPassing
Interest coverage≥ 3.00x3.41xPassing
Minimum liquidity≥ $25.0M$24.1MBreach
Capex limit≤ $18.0M$16.6MReview

Definition changed by amendment

2 sources

The March amendment revised the EBITDA definition used in the leverage test. The Q2 certificate still cites the original definition.

05

Defend what you reported.

An auditor asks why you reported a number eight months ago. Today that answer is archaeology: old spreadsheet versions, emailed PDFs, and someone who left. Khora reconstructs any figure as it stood, with the evidence and definitions in force at the time.

Used for

  • Audit and exam response — any reported figure, reconstructed with the sources and rules that produced it.
  • LP and investor reporting — why this quarter's number differs from what was shown last quarter.
  • Valuation mark history — how a mark moved, who corrected it, and what each version was based on.
Reported figure · Net asset value history Illustrative
As reportedValueBasisStatus
Mar 31, 2026$811.4M9 sourcesReported
May 12, 2026$814.9MRestatedCorrected
Jun 30, 2026$842.6M12 sourcesReported

Viewing as of March 31, 2026

Reconstructed

The May correction attributed a misclassified feeder-fund position. The March figure is shown exactly as reported, with the evidence and definitions in force on that date.

If your workflow depends on sources that disagree, entities without shared keys, or answers someone will challenge, it probably fits. Tell us about it.

Core capabilities

One system from source to output.

Every workflow above runs on the same five capabilities. Only the configuration changes.

01

Connect sources

Documents, spreadsheets, databases, warehouses, APIs, filings, and authorized websites, all in one working model.

02

Resolve and reconcile

Match records that refer to the same thing. Keep competing values, definitions, and uncertain matches visible.

03

Calculate and classify

Formulas, classifications, and checks that keep their inputs. Change an input and see what moves.

04

Review and correct

Conflicts, failed checks, and proposed changes go to the people responsible. Every decision is recorded.

05

Publish results

Reviewed work flows to the workbooks, dashboards, reports, APIs, and systems your team already uses.

For people

  • Evidence-backed workbooks
  • Fund and portfolio views
  • Deal models and review queues
  • Cited analysis and reports
  • Presentations and recurring deliverables

For systems

  • Application-specific APIs
  • PostgreSQL-compatible access
  • Warehouse exports
  • Reviewed datasets
  • Recurring data feeds

Khora and AI

AI on the record.

Models and agents research across your connected sources. Their findings don't stay in a chat transcript. They become structured claims your team reviews before anything is accepted.

From model-assisted research to accepted work
01

Research

Agents gather and compare material across every connected and authorized source.

02

Structure

Findings land as claims, entities, relationships, and calculations, not prose.

03

Review

Conflicts, uncertain matches, and assumptions stay visible until someone signs off.

04

Operate

Accepted work feeds the workbooks, reports, and systems that depend on it.

Provider flexibility

Swap models without rebuilding the workflow.

Khora works with any LLM provider. As models improve, or your risk and cost requirements change, your workflow and its accumulated evidence stay put.

Evidence and change

Every number can show its work.

Click a value and follow it down: the calculation, the claims that support and contradict it, and the source it started from.

Deal model · Reviewed result

Adjusted EBITDA

Illustrative workflow and data

Result used in model

$31.2M

Reviewed

General ledger

Operating result

$31.2M Supports

Management report

Reported adjustment

$34.9M Conflict

Analyst correction

One-time revenue removed

−$3.7M Approved

Trace anything

Any number, back to the page, cell, row, or record it came from.

See disagreement

Losing claims stay visible. Nothing is silently overwritten.

Corrections survive

A fix made last quarter isn't wiped by this quarter's refresh. Who corrected what, and why, stays on the record.

The engine

Built to hold up.

Underneath the workflows is a data engine designed for scale, history, and safe change. You don't have to think about it. It's why the rest works.

01

Fast at scale

Workbooks and views stay interactive across millions of rows and relations. Aggregations over hundreds of thousands of entities return in under a second.

02

Nothing is overwritten

Every change, human or agent, is a new version of the record. Reconstruct any past view, or preview today's data under yesterday's rules.

03

Change is reviewed

New matching rules, definitions, and calculations are tested against real data first. Nothing changes the accepted model without review.

04

Results become artifacts

One reviewed model produces workbooks, presentations, reports, database and API exports, and live query access. Every artifact keeps its citations.

Getting started

Configured around your workflow.

Khora is one product, configured per workflow: your sources, your entities, your definitions, your review process. Our team does the configuration with you and keeps it current as your sources change.

01

Define

Map the decisions, sources, definitions, and outputs that matter to the workflow.

02

Connect

We configure Khora against your representative sources and rules.

03

Review

Your experts check values, conflicts, and matches against the underlying evidence.

04

Operate

The workflow goes live. When sources or requirements shift, it's updated, not rebuilt.

Evaluating Khora

Test it on the workflow that hurts.

Khora has handled datasets with tens of millions of records. Scale is the easy part. The real test is your sources, your definitions, and your review requirements.

  • Connect real documents, systems, and external data.
  • Define the entities, relationships, and rules that matter.
  • Probe conflicts, uncertain matches, corrections, and revisions.
  • Deliver results into the tools your team already uses.

Khora is configured per workflow. It is not a document chatbot.

Get a demo

Bring us the workflow that will not reconcile.

Tell us about the sources, the definitions, and the numbers your team has to defend. We'll show you Khora configured for a workflow like yours.