FAQ — Licensing, Deployment, and Commercial Model

A: No. All processing occurs in-place. Source documents and derived outputs remain within the customer environment. No data is exported to external models or third-party services.

A: No. Kestri does not train models on customer data, retain data for reuse, or broadcast source material to large language models under any condition.

A: All outputs are traceable to source documents and generated in-place. Each explanation can be reconstructed, reviewed, and validated by auditors, regulators, and counsel without reliance on external model inference of any kind.

A: Yes. Kestri is purpose-built for regulated environments and supports deployments where data residency, licensing control, and auditability are mandatory.

A: Customers retain full ownership and control of all source documents and derived outputs.

A: No. Customers retain full operational control of their infrastructure, data, and access policies. Kestri operates as a service layer within customer-controlled environments and does not assume system ownership or administrative control unless explicitly agreed in writing.

A: No. Kestri is an independent platform and does not resell, bundle, or sublicense Oracle software. All deployments operate under the customer’s existing Oracle licenses using a Bring Your Own License (BYOL) model.

A: No. Customers use their own licensed Oracle infrastructure. Kestri does not provide database licenses or infrastructure services.

A: Kestri charges fees exclusively for its proprietary services:
•  In-place document decoding
•  Document-to-document comparison
No fees apply to database licensing, infrastructure, or data hosting.

A: Commercial terms are based on Kestri’s decoding and comparison services—not on data volume, compute resale, or database licensing metrics.