Finance and accounting decision
Dilutracker
A technically competent engineer can build a useful subset (EDGAR fetch, structured extraction, basic API/screener) using existing OSS components in a few weeks, but matching Dilutracker's coverage, extraction accuracy, historical depth, and enterprise features would require more resources and time.
Visit website↗$59/mo
$708/yr
Read off the official pricing page.
$100one-off84 h to build
$235/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 5 seats.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Fetch SEC filings from EDGAR, extract dilution-related items (warrants, converts, shelves, ATMs) into structured records, compute float/runway/risk scores, store results in Postgres, and expose JSON via a REST API plus a minimal web UI and screener.
What it still won’t have
- Coverage and scale (2,000+ tickers and rapid backfill)
- Accuracy and reconciliation quality of production extraction models
- Polish of the hosted web product (UX, real-time alerts, CSV/PDF exports)
- Priority support, SLA, and enterprise data licensing
- Historical depth and refresh credits/bulk-export features
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 5 seats.
Money you would actually spend
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
Build a minimal Dilutracker replacement using Python, FastAPI, Postgres, Celery (Redis broker), and OpenAI (or local LLM) for extraction. In scope: EDGAR fetcher for 10-K/10-Q/8-K/S-1/S-3/DEF14A; a parser pipeline that extracts instruments (warrants, convertible notes, ATM, shelf capacity) into structured tables; computation of float, shares outstanding math, cash runway, and simple LOW/MEDIUM/HIGH/SEVERE risk scoring; REST API endpoints (/ticker/{t}/summary, /ticker/{t}/dilution, /ticker/{t}/float, /ticker/{t}/runway, /ticker/{t}/full) with Bearer auth and basic usage counting; a minimal web UI: ticker page, screener list, and watchlist with ability to queue refreshes; background scheduler to refresh filings and cache results. Out of scope: enterprise licensing, multi-year historical archives at scale, advanced UI polish, and paid-grade SLA. Require robust error handling, unit/integration tests for fetcher, parser, calculations, and API, plus deployment scripts (Docker Compose) and README with run instructions.How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Price verified on pricing page+3
- 3/3 assessment runs agreed+4
- Evidence score62
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.
- official productDilution Tracker — Float Risk, Cash Runway & SEC Filing Analysis | Dilutracker
- official pricingPricing | Dilutracker
- official docsHow It Works | Dilutracker
Integrity checks
What held up, and what did not.
