OpenGov
opengov.com · Software for local government · checked 2026-09-04
Rank 1 of 29 in Software for local government, where the median is 13.
- 6 found
- 6 not found
- 0 not measured
We measured 12 of 12 criteria for OpenGov on 2026-09-04. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 52 out of 100, band D.
Overview
Transparency labelsaas-ranking.com
OpenGov
- A
- B
- C
- D
- E
- F
Published commitments5 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-04. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that OpenGov has no such document.
What they state
The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.
- Named on that page FedRAMP, SOC 2, SOC 2 Type II.
Show the 3 exact wordings
Physical and environmental controls are inherited from AWS’s FedRAMP-authorized infrastructure.
Read at https://opengov.com/security/Results are documented and reviewed during annual SOC 2 audits.
Read at https://opengov.com/security/Visit the OpenGov Trust Center SOC 2 Type II Security, Availability, Processing Integrity & Confidentiality AES-256 Encryption at Rest T
Read at https://opengov.com/security/ - Locations named next to the hosting wording Oregon.
Show the exact wording
Pre-production environments are geo-isolated in the US West (Oregon) Region. OpenGov personnel do not have physical access to data centers.
Read at https://opengov.com/security/ - Highest uptime figure on that page 99.9 %.
Show the exact wording
OpenGov’s Quarterly Uptime Percentage is 99.9% for the Software Services (excluding any OpenGov software not hosted by OpenGov).
Read at https://opengov.com/service-sla/ - Third-party hosts we saw on the first load 5 cloudflare.com, cloudflarestream.com, cookiebot.com, gaug.es, gstatic.com.
Show the 5 exact wordings
cdnjs.cloudflare.com
Read at https://opengov.com/embed.cloudflarestream.com
Read at https://opengov.com/consent.cookiebot.com, consentcdn.cookiebot.com
Read at https://opengov.com/secure.gaug.es
Read at https://opengov.com/fonts.gstatic.com
Read at https://opengov.com/ - HSTS max-age 31536000 seconds (365 days).
Show the exact wording
max-age=31536000
Read at https://opengov.com/
Gaps, heaviest first
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-04.
Show the 7 addresses we checked
https://opengov.com/legal/subprocessors– reached, no match (HTTP 404)https://opengov.com/subprocessors– reached, no match (HTTP 404)https://opengov.com/sub-processors– reached, no match (HTTP 404)https://opengov.com/legal/sub-processors– reached, no match (HTTP 404)https://opengov.com/trust/subprocessors– reached, no match (HTTP 404)https://opengov.com/privacy/subprocessors– reached, no match (HTTP 404)https://opengov.com/legal/subprocessor-list– reached, no match (HTTP 404)
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-04.
Show the 5 addresses we checked
https://opengov.com/pricing– reached, no match (HTTP 404)https://opengov.com/pricing/– reached, no match (HTTP 404)https://opengov.com/plans– reached and rendered, no matchhttps://opengov.com/en/pricing– reached, no match (HTTP 404)https://opengov.com/pricing-plans– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
- Third-party hosts we saw on the first load 5 cloudflare.com, cloudflarestream.com, cookiebot.com, gaug.es, gstatic.com.
Show the 5 exact wordings
cdnjs.cloudflare.com
Read at https://opengov.com/embed.cloudflarestream.com
Read at https://opengov.com/consent.cookiebot.com, consentcdn.cookiebot.com
Read at https://opengov.com/secure.gaug.es
Read at https://opengov.com/fonts.gstatic.com
Read at https://opengov.com/
Checked 1 address on 2026-09-04.
Show the 1 address we checked
https://opengov.com/– third-party requests before any interaction: cdnjs.cloudflare.com, consent.cookiebot.com, consentcdn.cookiebot.com, embed.cloudflarestream.com, fonts.gstatic.com, secure.gaug.es
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-04.
Show the 8 addresses we checked
https://opengov.com/legal/subprocessors– reached, no match (HTTP 404)https://opengov.com/subprocessors– reached, no match (HTTP 404)https://opengov.com/sub-processors– reached, no match (HTTP 404)https://opengov.com/legal/dpa– reached, no match (HTTP 404)https://opengov.com/dpa– reached, no match (HTTP 404)https://opengov.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://opengov.com/trust/subprocessors– reached, no match (HTTP 404)https://opengov.com/legal/sub-processors– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-04.
Show the 1 address we checked
https://opengov.com/.well-known/security.txt– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3We found this behind a sign-in, so it is not published openly.
Seen at https://opengov.com/privacy-policy/ · checked 2026-09-04
Show the 7 addresses we checked
https://opengov.com/legal/privacy– found, but behind a sign-inhttps://opengov.com/privacy– found, but behind a sign-inhttps://opengov.com/privacy-policy– found, but behind a sign-inhttps://opengov.com/legal/privacy-policy– found, but behind a sign-inhttps://opengov.com/legal/privacy-notice– reached, no match (HTTP 404)https://opengov.com/trust/privacy– found, but behind a sign-inhttps://opengov.com/datenschutz– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 6
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://opengov.com/terms-of-service/data-processing-addendum/ · checked 2026-09-04
Data location stated
weight 3 of 3The hosting location is stated on a public page.
- Locations named next to the hosting wording Oregon.
Show the exact wording
Pre-production environments are geo-isolated in the US West (Oregon) Region. OpenGov personnel do not have physical access to data centers.
Read at https://opengov.com/security/
Source: https://opengov.com/security/ · checked 2026-09-04
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://www.opengovstatus.com/ · checked 2026-09-04
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
- HSTS max-age 31536000 seconds (365 days).
Show the exact wording
max-age=31536000
Read at https://opengov.com/
Source: https://opengov.com/ · checked 2026-09-04
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
- Named on that page FedRAMP, SOC 2, SOC 2 Type II.
Show the 3 exact wordings
Physical and environmental controls are inherited from AWS’s FedRAMP-authorized infrastructure.
Read at https://opengov.com/security/Results are documented and reviewed during annual SOC 2 audits.
Read at https://opengov.com/security/Visit the OpenGov Trust Center SOC 2 Type II Security, Availability, Processing Integrity & Confidentiality AES-256 Encryption at Rest T
Read at https://opengov.com/security/
Source: https://opengov.com/security/ · checked 2026-09-04
Uptime SLA with a figure
weight 1 of 3An availability commitment with a figure.
- Highest uptime figure on that page 99.9 %.
Show the exact wording
OpenGov’s Quarterly Uptime Percentage is 99.9% for the Software Services (excluding any OpenGov software not hosted by OpenGov).
Read at https://opengov.com/service-sla/
Source: https://opengov.com/service-sla/ · checked 2026-09-04
History
Not enough completed runs yet to draw a line. The next runs fill this in.