Platform · Governed Data

Tarn

Part of Kundi · For Banking, Asset Management, Government

Tarn is the data platform underneath Kundi. SQL tables, documents, events, vectors and model artifacts live in one catalog on your hardware. Regulatory obligations compile into masks, row filters, purpose limits and retention. Every query, write, read and erasure lands in a hash-chained ledger that an examiner can replay entry by entry. Tarn is part of Kundi and is also available on its own.

Capabilities

Proof, not logs.

Tarn gives data teams the SQL, tools and roles they already use, and gives risk, compliance and examiners an answer to every "who touched this, and why".

  • Lakehouse SQL With Time Travel

    Create, insert, update, delete, merge and alter, each one a single catalog commit. Query any table as of any earlier commit; history does not expire.

  • Structured and Unstructured, One Catalog

    Documents (PDF, text, images), events, vectors, model artifacts and policy sets are content-addressed, write-once objects alongside your tables.

  • Governed Queries That Show Their Work

    A query declares its regulatory context and returns the rows together with the policies applied and the obligations they come from. Tarn refuses a query rather than quietly drop a policy.

  • Regulation Compiled Into Policy

    Obligations become column masks, row filters, purpose restrictions and retention rules, each citing the obligation it enforces.

  • Hash-Chained, Replayable Ledger

    Queries, writes, reads, searches, inference, ingestion, erasure and administration each become a ledger entry that can be replayed by id. Replay reports anything that no longer matches.

  • Privacy by Key

    Personal data is encrypted per data subject. Erasure destroys the key, and erasures are re-applied after a backup restore, alongside write-once storage and legal holds.

  • Access That Follows Purpose

    Principals, roles and grants per scope, purposes bound to grants, attribute-driven row filters, compartments, break-glass overrides and two-person release gates.

  • Standard Tools

    A SQL gateway that standard JDBC clients connect to, Kafka in and out with exactly-once batch append, governed views, scheduled jobs, alerts and a web console.

Zero Trust by the Operating System

No containers. No outside calls.

Tarn installs natively and locks itself down by default.

  • Pinned Components

    One command installs every component, each verified against a pinned SHA-256 hash.

  • One Account per Service

    Every service runs under its own operating-system account with per-install credentials.

  • Loopback by Default

    Every listener binds to loopback unless you expose it, and the platform makes no outside calls.

  • Write-Once Storage

    Records sit in object storage locked in compliance mode, with retention set by obligation and legal holds when you need them.

Quantum-Resilience

A ledger that stays verifiable.

Tarn protects its ledger, its keys and its connections with post-quantum cryptography from Frontier Foundry's own COSMIC library.

  • Quantum-Resilient

    Built for the post-quantum transition that federal deadlines put in 2030 and 2031. Records and decisions stay confidential and verifiable after a cryptographically relevant quantum computer exists.

  • Inside Your Perimeter

    Runs on infrastructure you control. Models and data stay inside your perimeter, and nothing calls home.

  • SOC 2 Type II

    Frontier Foundry is SOC 2 Type II.

Product Walkthrough

See it inside your environment.

Tarn walkthroughs are available under NDA. See a governed query return its proof, a replay, and a crypto-erasure running inside your environment.

Schedule a Deployment Assessment
Related