ALGORITHM TRANSPARENCY STUDY

We Asked 47 Algorithm Vendors to Show Us Live Data. 26 Refused.

A collective of burned investors conducted a market study. Here's who actually shared their broker data and who wanted to 'get on a phone call' instead.

Started by 6 burned investors
$2.3M collective losses
Zero affiliate relationships

Why this exists, and how it works

Algorithmic trading vendors all promise verified, institutional-grade returns. Most will not let you check before you pay. This study grades each one on the same public-information checklist, so the gaps are visible before any money moves.

01

Same checklist for everyone

Every vendor is held to the same standard: can performance be independently verified, ideally through read-only data, instead of screenshots or a sales call.

02

We score four things that matter

Every fund is graded across four pillars and sixteen checks: can you verify it, does the strategy hold up, is the company real, and how does it treat people. One color per check.

03

We publish exactly what we find

Green means we verified it. Orange is partial. Red fails. Grey means the vendor never disclosed it, and we leave it grey rather than guess. We invent no numbers.

Green is earned. Grey is a choice the vendor made.

Study Summary Matrix

21 vendors analyzed from public information.

1

Holds up

Scored 70 or above: discloses enough, in a checkable way, to clear our bar across the four pillars.

View the leaderboard →
15

Mixed

Scored 45 to 69: some real transparency, but meaningful gaps. Verify the specifics before trusting capital to them.

View the leaderboard →
5

Weak or undisclosed

Scored below 45, or disclosed too little to grade at all (1 weak, 4 with insufficient public data).

View the leaderboard →

Where the 21 vendors landed

All 21 vendors, grouped by their overall trust grade.

The System Transparency Leaderboard

Every fund scored on what it actually lets you verify. Tap a card for the full breakdown. Last updated: .

Verified Partial / conditional Fails Not disclosed
ORIGIN ARCHIVE

Why this study exists.

Algorithmic trading has become a crowded space filled with confident promises, impressive-looking dashboards, and performance claims that are often difficult to verify.

This project started after a small group of private investors compared their experiences with automated trading vendors and noticed the same pattern: unclear risk disclosures, selective performance reporting, limited transparency, and very little independent verification. The goal was never to attack the industry. The goal was to create a simple public reference point for retail investors who want to understand what is actually disclosed before trusting capital to an algorithmic system.

Our approach

Every vendor is reviewed using the same framework: transparency, verifiability, track record quality, company longevity, business robustness, and reputation integrity. We do not score based on marketing claims. We only use public information, official disclosures, archived pages, regulatory references, and sources that can be checked. When something cannot be verified, it is not assumed. It stays grey.

In an industry built on performance claims, transparency should not be optional.

How to read the scores

Green means the information is publicly disclosed and verifiable. Orange means the information is partial, unclear, or self-reported. Red means there is a visible concern. Grey means the information was not found publicly. Scores may evolve as vendors publish more information or improve their disclosures.

Want to help keep this study maintained?

We accept community contributions to pay server architecture and public domain data audit costs.

5 OF 21 SCORED WEAK OR INSUFFICIENT

How vendors avoid verification

When asked for verifiable performance, vendors tend to deflect in four common ways. Watch for these before you buy.

01. The Sales Pivot

Trying to sweep clear API requests under the rug by aggressively pushing a "quick validation Zoom call" instead.

02. The Proprietary Shield

Claiming that showing execution paths violates private code intellectual property (Read-only API access exposes zero system logic).

03. The Terminal Ghost

Immediate communication blackout. Chat rooms and support channels go completely silent the second API protocols are listed.

04. Aggressive Defense

Stating that tracking real portfolio accounts constitutes unfair industry harassment or bad-faith intent.

Pre-Purchase Verification Audit Script

Copy and paste this directly into support tickets to filter out unverified market risks before buying.

Subject: Read-Only API Performance Request

Hello,

Prior to finalizing my software deployment allocation, I require access to a read-only tracking link (Tradovate compliance link, NinjaTrader account sync, or Rithmic data node) linked to a live capitalized production execution server. 

Please note that our compliance checks do not parse historical spreadsheet logs, custom screenshot uploads, or video platform presentations. 

Let me know if your configuration is ready to authorize a tracking node.

Thank you.

The Phone Script They Don't Want You to Use

Keep this breakdown open next time you explore an upcoming portfolio vendor.

5 Questions to End Sales Patter Instantly

  1. "Is this absolute equity curve accounting for live slippage and execution loops?"
  2. "Can I view your data link directly inside a clean clearing portal terminal?"
  3. "What is the longest historical holding period tracking duration across your open index options data?"
  4. "Can you export this tracking architecture without forcing an introductory strategy call?"
  5. "If this model is highly robust, why are tracking variables barred from public view parameters?"

Get Status Updates

Get notified when the scorecards are updated or a new vendor is added to the study.

SUPPORT OUR CAUSE

Promote Infrastructure Transparency

Your contribution helps us keep this website running and advertise our mission to promote transparency in algorithmic trading. Choose an amount that you're comfortable with.

🔒 Allocation Routing: 100% used for server clusters, public domain renewals, and API performance data node hooks.