Upptime vs cState: privacy compared
Upptime and cState are both rated in status pages and uptime monitoring against the same 7 public criteria. Upptime does better on public uptime history. cState does better on no trackers or telemetry.
| Criterion | Upptime Our pick | cState |
|---|---|---|
| Grade | Grade B B (78/100) | Grade B B (84/100) |
| Jurisdiction | Unknown | Unknown |
| Open source Is all the source code needed to run the product public? | Yes source | Yes source |
| No trackers or telemetry Are the website and apps free of third-party trackers, with any analytics anonymous and any telemetry off by default? | Partial source | Yes source |
| No ads or data sales Is the product funded without advertising, ad targeting or selling user data? | Yes source | Yes source |
| Independent audit Has an independent security or privacy audit been published within the last three years? | No | No |
| Runs on your own infrastructure Can it run entirely on your own infrastructure or repository, without a vendor account? | Yes source | Yes source |
| No visitor tracking Is the public status page free of third-party trackers and analytics? | Yes source | Yes source |
| Public uptime history Does it publish response times and incident history? | Yes source | Partial source |
Summaries
Upptime. Upptime scores 78 out of 100 (grade B) on the status pages and uptime monitoring criteria. It meets 5 of 7 criteria: open source, no ads or data sales, runs on your own infrastructure, no visitor tracking and public uptime history. It partly meets no trackers or telemetry. It does not meet independent audit.
cState. cState scores 84 out of 100 (grade B) on the status pages and uptime monitoring criteria. It meets 5 of 7 criteria: open source, no trackers or telemetry, no ads or data sales, runs on your own infrastructure and no visitor tracking. It partly meets public uptime history. It does not meet independent audit.