// Prop Firms · ZvxScore™ — Systematic ES/MES Fit

Fit for the workflow, not hype

ZvxScore ranks a defined 50K public account path at each firm for cross-firm comparability, while account-size panels enumerate the current size family and openly flag fields that are partial, dynamic or awaiting recheck. The score focuses on automation policy, TradingView/Tradovate fit, funded risk structure and payout access — not overall firm quality.

Scope: The public page always reads the last manually reviewed and published snapshot. New candidate data can be staged server-side, but it cannot replace the public ranking without an explicit review-and-publish action.
VERIFIED DATA · LOADINGDataset engine: checking published snapshot…
// COMPARISON SELECTION

COMPARE EXACT ACCOUNT PATHS

Select exact firm/account combinations and compare up to three structural paths side by side. Promotions remain secondary to verified risk and rule structure.

Choose up to three exact account paths to compare.
FILTER RANKING
// Current published ranking

Systematic fit snapshot

Loading the last reviewed snapshot…

Loading verified dataset…
// Methodology

Reproducible by design

Structural rules are weighted more heavily than fast-changing promotions. The public score is recalculated by the server-side validation gate from the score breakdown submitted with each candidate snapshot.

Price remains context, not score: official pages can mix standard prices, temporary promotions and checkout-only pricing. ZvxScore v1.1 therefore keeps standard and promotional price separate and excludes price from the systematic-fit score.
Open current published JSON → Publication history →
// Publication controls

Review before publish

The data engine keeps candidate snapshots separate from the public snapshot. Candidate uploads are schema-checked, scores are recomputed, source URLs are required, future verification dates are rejected, and an older snapshot cannot silently replace a newer one.

Candidate stage

  • New research is uploaded to a protected admin endpoint.
  • The server validates the dataset and recomputes firm scores.
  • The candidate is stored separately and remains invisible to public visitors.

Publish gate

  • A human reviewer must name themselves.
  • The exact publish confirmation phrase is required.
  • The published snapshot is versioned and added to publication history.
  • The previous bundled verified snapshot remains the emergency fallback.
// Evidence policy

What “verified” means

A material scoring field requires a current first-party firm source. If an exact value is not supported, it stays unknown. Promotions do not silently replace standard pricing, and the dataset verification date changes only after a new verification is completed.