Finance and accounting decision

Zero G

A competent technical user can build a useful self-hosted replacement using existing open-source trading/backtest projects and libraries; Zero-G's pages provide no evidence of durable moats or unique data.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off160 h to build

$50/mo6 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Zero G alternatives, with the arithmetic →

What a replacement has to do

  • Ingest market data, visualize a market-map, backtest strategies, and send orders to an exchange/broker.

What it still won’t have

  • polished commercial UI/UX and product polish
  • SLAs and uptime guarantees for live order routing
  • customer support and onboarding
  • any proprietary models, datasets, or integrations Zero-G may bundle
  • regulatory/compliance assurances or insurance

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Zero G does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal self-hosted trading map web app using Python FastAPI, Postgres, Celery, and React + D3 for the frontend. Core features in scope: 1) ingest live market data (exchange REST/websocket) and store normalized ticks/ohlc in Postgres; 2) simple backtester that replays historical OHLC from Postgres and outputs PnL metrics; 3) broker integration using CCXT for live order placement, cancels, and position sync; 4) interactive market-map UI showing symbols, metrics, and allowing strategy parameter edits and paper/live toggles; 5) simple auth, logging, and audit of orders. Out of scope: mobile app, institutional compliance/custody, advanced risk engine, high-frequency low-latency execution. Require: error handling for all external calls, unit and integration tests for ingestion, backtest, and order flows, Docker-based deployment manifests, and basic CI pipeline.
How we checked3 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • Evidence score60

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded