Skip to content

SERVICE LEVEL

Targets by tier. Contractual SLA at Enterprise.

Pilot is best-effort with stated targets. Standard adds an uptime target and faster support response. Enterprise is the tier with a contractual uptime SLA and credit terms — finalized in the signed agreement.

Tier	Uptime	Support response	Status reports
Pilot	95% target best-effort, no SLA	1 business day email, business-hours	—
Standard	99% target target, not contractual SLA	4 hours Slack + email, business-hours	Monthly
Enterprise	99.9% SLA contractual + credit terms	1 hour P1, defined incident response dedicated point of contact	Custom cadence

REFRESH CADENCE

Data freshness is governed by the named source and written delivery agreement, not inferred from tier. Publisher cadence is not proof of a completed load; source and observation dates must be stated per dataset.

Full per-source cadence is documented at /refresh-cadence.

STATUS

Public status page

Fonteum's public status board is available at /status. It separates HTTP transport uptime from pipeline freshness, source completeness, and incident signals, so a data concern is not presented as an outage. Customer notification terms remain governed by the relevant signed agreement.

Note: this page describes contractual obligations as they appear in the relevant tier's signed agreement. Pilot agreements supersede this page; signed Enterprise agreements supersede this page where they conflict.

SEE ALSO

What’s on file, by the numbers

Platform snapshot · 2026-08-11

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file

26.2Msource-linked factsSource-linked field facts in the dated platform snapshot

90sources with dataDistinct snapshot source IDs with at least one positive record count

73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days

111sources integratedActive registry rows; integration does not establish a load

13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →