Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 1 min read

How We Built a Fast Prop Firm Comparison Engine & Risk Simulator on Cloudflare Workers and D1

Comparing proprietary trading firms sounds simple until you try to structure the actual data. Across 80+ futures, forex, and crypto prop firms, every provider uses different rules for trailing drawdowns, daily loss limit

How We Built a Fast Prop Firm Comparison Engine & Risk Simulator on Cloudflare Workers and D1

Comparing proprietary trading firms sounds simple until you try to structure the actual data. Across 80+ futures, forex, and crypto prop firms, every provider uses different rules for trailing drawdowns, daily loss limits, consistency scores, activation fees, and payout capsβ€”and those rules change frequently.

To solve this without relying on bloated server infrastructure or static spreadsheets, we built PropFirmVS, a quantitative prop firm comparison engine and risk simulator designed for speed and transparency.

Why Edge-First Architecture?

When traders filter dozens of account sizes and rule combinations side by side, latency matters. Instead of spinning up a heavy traditional backend, we structured the stack around edge execution:

  • Cloudflare Workers for fast request routing, dynamic filtering, and programmatic comparison pages.
  • Cloudflare D1 (SQLite at the edge) to store normalized firm metadata, account tiers, fee structures, and automated rule verification timestamps.
  • Automated Rule Auditing to flag unverified claims or rule updates rather than guessing missing parameters.

Modeling Drawdown Risk Instead of Just Headline Prices

One of the biggest traps in prop trading is picking an evaluation solely on the lowest upfront discount code while ignoring trailing drawdown mechanics or hidden activation fees.

Alongside the structured dataset on propfirmvs.com, we focused on surfacing the true cost to first payout and modeling how drawdown rules impact survival probability across different account sizes.

Key Lessons Learned

  1. Normalize aggressively upfront: Treating drawdown type (intraday trailing vs. end-of-day vs. static) as a first-class database column makes side-by-side filtering drastically cleaner.
  2. Track verification dates per record: Displaying when rules were last audited builds far more user trust than unverified marketing summaries.
  3. Edge SQL scales effortlessly for read-heavy comparison datasets: With proper indexing on account size and market type, queries resolve in milliseconds globally.

If you're building data-heavy comparison tools or working with Cloudflare Workers + D1, I'd love to hear how you structure schema updates and automated data checks!

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.