What the pilot delivers
- Facility-level audit-pack exportFor supported facility datasets, export the available source URL, loaded observation date, row key, methodology version, and documented limitations. Fields absent from the loaded source are identified rather than filled in.
- Pinned methodology versioningNamed exports identify the methodology version used. Historical row replay is available only for sources that retain row history, and the export states that scope.
- Source-specific deliveryThe pilot statement of work names the datasets, loaded observation dates, delivery schedule, and limitations. No platform-wide refresh cadence is promised.
Enterprise-tier protections
Fonteum pilots named public-record datasets and supplies no PHI. The protections below concern your firm's query footprint; contractual requirements are scoped in the pilot agreement.
- Isolated instanceYour query traffic runs in a dedicated environment — not co-mingled with other tenants. What your team looks up stays within your instance.
- Non-logged queriesLookups against public federal data are not retained in shared access logs. Your usage pattern — which providers you query, how often, in what sequence — is your own.
- Dedicated throughput, signed SLAA contractual throughput commitment means your production traffic is not throttled by shared-tier demand spikes.
- Procurement-ready provenanceVendor-review packages document the named source, loaded observation, methodology, and limitations. Snapshot-level chain artifacts, when available, are reported separately from row-level provenance.
Terms
Compliance posture
See the work before you commit
Pilot intake
Four fields. The operator reviews each request by hand and replies within 1 business day.
Share with your team