Transparency alternatives to COAST Systems
Other Manufacturing execution vendors we measure, sorted by how much we found at them and not at COAST Systems. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from COAST Systems on at least one criterion we measured for both. Public transparency score, not a product or security rating.
COAST Systems has 12 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at COAST Systems” is the one that closes them.
| Vendor | Score | Found there, not found at COAST Systems | Found at COAST Systems, not found there | |
|---|---|---|---|---|
| Dozukidozuki.comSee also Transparency alternatives to Dozuki | 39/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Tuliptulip.coSee also Transparency alternatives to Tulip | 39/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | nothing | Compare |
| Ams Erpams-erp.comSee also Transparency alternatives to Ams Erp | 35/100 | 4 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | nothing | Compare |
| Forcam Eniscoforcam-enisco.netSee also Transparency alternatives to Forcam Enisco | 26/100 | 4 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), +1 | nothing | Compare |
| Evoconevocon.comSee also Transparency alternatives to Evocon | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Scytec DataXchangescytec.comSee also Transparency alternatives to Scytec DataXchange | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | nothing | Compare |
| Simussimus-systems.comSee also Transparency alternatives to Simus | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Abasabas-erp.comSee also Transparency alternatives to Abas | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| ECI Solutionsecisolutions.comSee also Transparency alternatives to ECI Solutions | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| MPDVmpdv.comSee also Transparency alternatives to MPDV | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Reverreverscore.comSee also Transparency alternatives to Rever | 17/100 | 3 Certifications named, Uptime SLA with a figure, Notice before subprocessors change | nothing | Compare |
| Asset Scienceassetscience.comSee also Transparency alternatives to Asset Science | 17/100 | 2 Public pricing, No third-party tracking before consent | nothing | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.