For data and research teams

Stop rebuilding public-data pipelines. Start testing the model.

Replace internal disclosure ingestion and reduce manual processing of paid feeds with maintained historical financials, operating KPIs, guidance, and alternative data delivered through the platform, REST API, or Data Warehouse.

Try the platform Review Data Warehouse delivery

Data Warehouse · Operating KPI actuals

How much research time is spent collecting rather than testing?

Start with maintained observations in the warehouse.

The delivery layer resolves company identity, standardized metric, fiscal period, reported value, and source timing. The preview shows a small selection of actual KPI records across GitLab, MongoDB, and Okta rather than a synthetic schema example.

Teams can replace issuer-specific extraction work while retaining the source and point-in-time fields needed for research, revision handling, and downstream quality controls.

Research outputLess extraction maintenance and faster coverage expansion.
Delivered through supported warehouse platforms

Selected KPI actual observations

A compact view of reported operating metrics in the delivered fact table.

Data Warehouse tablekpi_facts
TickerMetricPeriodValuePeriod end
GTLBcRPOQ1 FY27$724.1m2026-04-30
MDBRPOQ1 FY27$1.46b2026-04-30
OKTACustomersQ4 FY2620,0002026-01-31

SoftwareIQ data for the companies, metrics, and periods shown.

Guidance + Operating KPIs · Okta

How consistently does management guide relative to the realized KPI?

Calibrate the model against the guide and the result.

Final cRPO guidance ranges are matched to the reported value for the same target quarter. The history shows realized variance without losing the filing date on which the guide entered the research set.

The resulting panel supports forecast priors, guide-quality factors, and earnings scenario ranges without requiring the research team to reconstruct disclosure history.

Research outputReproducible guidance calibration and forecast testing.
Six completed target periods

Final cRPO guidance versus reported actual

Guide ranges and results remain matched to the same fiscal period.

Q1 FY27Guide $2440–$2450mActual $2,499m+2.2% vs. midpoint
$2,600m$2,475m$2,350m$2,225m$2,100m+5.4%Q4 FY25+1.8%Q1 FY26+2.8%Q2 FY26+2.9%Q3 FY26+2.7%Q4 FY26+2.2%Q1 FY27

SoftwareIQ data for the companies, metrics, and periods shown.

Cross-dataset delivery · GitLab

Can one research system preserve different observation cadences?

Join the evidence without flattening its meaning.

GitLab's reported cRPO, daily job inventory, and daily-delivered developer signals resolve to the same company while retaining each observation's native date, unit, source, and version context.

That separation lets a backtest distinguish company change from data-model change and supports monitored features across REST and Data Warehouse delivery.

Research outputAuditable panels for backtests, forecasts, and monitoring.
Distinct cadences · consistent identities

A maintained cross-dataset panel

Representative current observations from the delivered research layer.

Operating KPIsGitLab · cRPO$724.1m
Ticker
GTLB
Observed
2026-04-30
Availability
Quarterly
Job PostingsGitLab · Active postings218
Ticker
GTLB
Observed
2026-08-31
Availability
Daily
Developer SignalsGitLab · Runner Docker pulls837,227
Ticker
GTLB
Observed
2026-08-24
Availability
Daily

SoftwareIQ data for the companies, metrics, and periods shown.

Read together

The value is not another feed; it is a maintained research layer.

The warehouse supplies structured history, the guidance comparison demonstrates a reproducible analytical use, and the cross-dataset panel shows how distinct cadences remain usable together. Material methodology improvements are documented and versioned.

Connected datasets

One company and product taxonomy. Distinct evidence.

Each measure retains its own cadence, definition, and evidentiary weight while resolving to consistent company and product identities.

Operating KPIs and guidance

Established historical financials, canonical operating metrics, guide ranges, actuals, sources, and calculations.

Job Postings

Daily event and inventory history with software-specific role, function, geography, and investment classifications.

Developer Signals

Mapped product activity with controls for outages, resets, source migrations, and versioned methodology.

Continue the research

Spend the research cycle on the model, not the parser.

Inspect the delivery model and historical definitions or evaluate the observations directly in the platform.

Try the platform Review documentation