Skip to main content
The terces.io platform is continuously assessed across 7 dimensions using an automated health scorecard. This ensures every aspect of the platform — from data quality to security to operational maturity — meets production standards before serving client data.

Continuous Assessment

Unlike one-time audits, our platform health scorecard runs 65 automated checks on every assessment cycle. Each check is deterministic and evidence-based — the same platform state always produces the same score.

Assessment Model

  • 65 checks across 7 dimensions
  • Deterministic scoring — no subjective judgement, fully reproducible
  • Weighted dimensions — security and data quality weighted higher than documentation
  • Gate rules — a critical gap in any dimension prevents an inflated overall score
  • Trend tracking — scores are recorded over time to show improvement trajectory

What We Measure

Security

Infrastructure access controls, encryption, network exposure, secrets management, and container hardening. Security is weighted 3x in the overall score — reflecting its non-negotiable importance for client data.

Data Quality

Automated assertion coverage, referential integrity between data models, schema consistency checks, and exception handling. Every data refresh is validated against 21 assertions before downstream consumption.

Performance

Query optimization (partitioning, clustering), incremental processing patterns, bounded lookback windows, and caching layers. These ensure fast dashboard response times and efficient data processing.

Scalability

Multi-environment support, infrastructure-as-code modularity, deployment automation, and capacity management. These ensure the platform grows reliably as client volume increases.

Enterprise Readiness

Documentation completeness, production environment configuration, multi-tenant access control framework, SLA/SLO definitions, and change management. These ensure the platform meets enterprise buyer requirements.

Operational Maturity

Pipeline scheduling, backup automation, monitoring and alerting, disaster recovery procedures, and infrastructure version control. These ensure the platform operates reliably without manual intervention.

Monetization Readiness

Tiered access control, client portal dashboards, usage metering, API layer readiness, and policy seed data. These ensure the platform can serve differentiated experiences to free, premium, and enterprise clients.

Scoring Methodology

Weighted Dimensions

Not all dimensions are equal. Security and Data Quality carry more weight than documentation — because a secure, accurate platform with incomplete docs is better than a well-documented platform with security gaps.

Gate Rules

A critical failure in any single dimension prevents an inflated overall score. This ensures that platform strengths cannot mask critical weaknesses in areas like security or data quality.

Score Labels

ScoreLabelWhat it means
8.0 – 10.0StrongMeets or exceeds production standards
6.5 – 7.9GoodProduction-capable with minor improvements needed
4.0 – 6.4Needs WorkFunctional but requires hardening before enterprise use
Below 4.0CriticalFundamental gaps that must be addressed

Cross-Dimension Dependencies

The scorecard enforces logical dependencies between dimensions. For example, Enterprise Readiness cannot score higher than Security — because no platform is enterprise-ready if its security posture is weak, regardless of how complete its documentation is. This prevents misleading scores and ensures the overall health rating reflects the weakest critical link, not just the average.

Data Quality Commitment

Our Guarantees

  • No PII: All data is public regulatory information — no personally identifiable data
  • Single source of truth: Codex Alimentarius (CXS 192-1995) as the authoritative standard
  • Automated validation: 20+ data quality assertions run on every pipeline refresh
  • Exception monitoring: Dedicated exception tables capture and surface any data anomalies
  • Source provenance: Every data point is traceable back to its source document and load timestamp

Continuous Improvement

The scorecard is not static. As the platform evolves, new checks are added to reflect emerging best practices and client requirements. The scoring methodology itself is versioned and documented, ensuring transparency in how platform health is measured over time.