On-prem, license-clean, weekly refresh. The destination data layer built for the data-residency posture your procurement office actually requires — not the cloud-only API your last vendor wanted to renew. Bihar Tourism pilot live; conversation-ready for other state boards.
Three named acceptance criteria, three months, no invoice during Phase 1. The Tourism Secretary's office gets a deployed Concierge layer; we get a case study and the right to talk about it.
Open the Bihar Buddhist Circuit demo → Or fly through the 3D circuit map →Phase 2 commercial terms — pricing, term length, MFN clause — are detailed under MNDA. The MFN guarantees the first state-DMO buyer gets our lowest comparable rate for the life of the contract.
Cloud-only travel APIs assume your queries can leave India. For a state board, that's a non-starter the moment legal reviews the DPDPA Section 16 cross-border clauses. The on-prem stack runs the same Concierge surface on infrastructure you control — Docker compose on a single GPU box, weekly Parquet refresh, encrypted delta delivery. Your traveller queries never touch a third-party LLM endpoint.
The same architecture supports air-gapped deployments for boards that need stricter posture (single-tenant cluster, no public DNS, keyed refresh). Both options carry the same 99.0% SLA and 16-class license registry.
If your state tourism board is sizing up an agent-driven content strategy and wants a pilot scope tailored to your circuit, we'll send a 30-minute discovery call invite within a week.