A database that argues with its sources

Architecture

StockQL ships as a Docker Compose stack: a PostgreSQL instance, an ingestion engine, a job scheduler, and a validation suite. You configure which exchanges you care about and provide your own provider keys; everything else is automatic.

┌─────────────┐   ┌─────────────┐
│  EODHD API  │   │   FMP API   │      your keys, your accounts
└──────┬──────┘   └──────┬──────┘
       │                 │
   ┌───▼─────────────────▼───┐
   │   ingestion + validation │      calendars · completeness ·
   │        (scheduled)       │      liveness · corporate actions
   └────────────┬────────────┘
                │
        ┌───────▼────────┐
        │   PostgreSQL   │           documented schema, plain SQL,
        │  your machine  │           yours forever
        └────────────────┘

The error-checking machinery

Each of these guards exists because the raw feeds failed us in production. They run automatically; you read the audit log, not the vendor's changelog.

Completeness re-pass

Vendor bulk end-of-day files are mutable: fetched two hours after the US close, a file can be missing hundreds of symbols that appear later with no indicator. StockQL re-fetches recent date-addressed files on the following days and fills only what was missing — so a quiet vendor delay never becomes a permanent hole in your history.

Trading-calendar validation

Every exchange gets its own calendar cohort — 72 in total, including venues that don't trade Monday–Friday and asset classes that can't share a venue calendar at all. Rows on impossible dates and zero-volume placeholder padding are rejected instead of stored. Where vendor metadata is wrong (it happens — we've caught an exchange whose entire listed cohort belonged to a different country's calendar), StockQL's mapping wins.

Delisting and resurrection guards

Delisted symbols are retained with full history, so your universe is survivorship-bias-free. In the other direction, a symbol marked dead that starts printing real volume again is automatically revived and backfilled — vendors mis-flag both ways, and StockQL cross-checks a second provider daily to catch it.

Corporate-action coherence

Splits and dividends are applied consistently across the whole history, and adjusted series are recomputed rather than trusted, so a late-arriving corporate action can't leave half your history on one basis and half on another.

What's in the box

See pricing →