For enterprise & data licensing

Every row carries its license. Every answer cites it.

The 16-class license registry classifies every data row as commercial-OK or blocked at ingest. Your tenant's enabled licenses gate every read through row-level security — you never see a row you can't legally use.

# A Concierge response — note license_tag and citations on every row
{
  "answer": "Kyoto's Higashiyama district has 14 listed POIs...",
  "citations": {
    "data_sources": [
      { "row_id": "poi:JP-26100-9842",
        "license_tag": "CC-BY-4.0",
        "source": "OSM" },
      { "row_id": "narrative:JP-26100-987",
        "license_tag": "michelin_licensed",
        "source": "michelin_guide" }
    ]
  },
  "confidence": 0.94
}

Commercial-OK licenses are restrictive: Apache-2.0, CC0, CC-BY-4.0, ODbL, michelin_licensed, and others. Blocked sources never make it into a tenant query at all — Yelp non-commercial, default-deny, and unclear-pending-review rows are filtered before retrieval.

What changes: your compliance team's review of a travel data dependency moves from eight weeks to one afternoon. The DPA, sub-processor list, and license posture are all live URLs — they don't wait for a sales call.

16-class

License registry classifying every commercial-table row. Per-tenant enabled-license whitelist enforced via row-level security in Postgres. See license posture.

MSA + SLA + DPA

Drafted on Common Paper CSA v2.1, INR-billing, MFN-protected. DPA includes EU SCCs Module 2, UK IDTA, DPDPA-IN supplementary clauses. Request the MSA.

On-prem

Single-GPU Docker compose deployment, weekly Parquet refresh, encrypted delta delivery. Air-gapped variant for highest-residency posture. 99.0% on-prem SLA.

Trust posture, in writing.

We're pre-SOC2 and honest about it. The /security page publishes the current Trust posture v0.2 with a versioned pill and an explicit roadmap table — every [GAP] item carries a target date. Sub-processor list lives at /legal/sub-processors with a 30-day-notice policy per the DPA §7.3. CAIQ-Lite v4.0.3 is pre-filled and downloadable; many answers resolve to "roadmapped — see §F.X" with the corresponding date.

That's not procurement theater — it's the posture we can defend today. The 90-day "if we tell you we have SOC2 we'll have it" story has burned every enterprise buyer who's tried to onboard a pre-revenue vendor. We'd rather show you what's in place and what isn't, and let your team make the call.

Pre-revenue, post-security-posture. Talk to the founder direct.

If you're scoping an enterprise travel-data dependency and want a security questionnaire turned around within the week instead of the quarter, we'll have a call this week.

Talk to founder → Read the trust posture