Compare
PIT vs RavenPack
RavenPack scores news and classifies events for institutions, through a sales process. PIT returns filing rows, their clocks, and a coverage certificate recording each day it read. You buy it on a card, and it has no sentiment product at all.
If you came here looking for Bigdata.com: that is a RavenPack product, their AI research assistant, launched 2024. RavenPack is still trading as RavenPack, checked August 2026. Nothing below changes if you meet the data business under the other name.
Updated 2026-08-26. PIT figures read off a running server; vendor figures off each vendor’s own pages.
Fit
Who each product is for
| RavenPack | PIT | |
|---|---|---|
| Buyer | A desk or research team that wants scored news, event taxonomies and a sentiment factor. Trials start with a form, and delivery includes API, Snowflake and WRDS among others. | Someone who already has prices and needs a filing cut on a named clock with certificates attached. |
| What comes back | Analytics over news: event sentiment, composite sentiment, event types. The underlying text is licensed premium news. | Rows, coverage objects, mapping intervals and parquet partitions, one file per source per day. You bring the model. |
| How you buy | Through a sales conversation. | Stripe, with an attestation that the use is internal. Commercial redistribution is priced by email. |
Clocks
Where a score still needs a clock
| RavenPack | PIT | |
|---|---|---|
| Point-in-time | Institutional feeds often ship vintages. Their exact timestamp rules are not published, so check them with RavenPack directly. | visible_by is required rather than optional. It defaults to published_at; the strict setting is available_at. |
| Scores | The score sits on an event, and using it in a backtest still means knowing when the score itself was computable. | There is no score. If you compute one over PIT rows, the knowable time is the named clock on the row you computed it from. |
| Coverage | Vendor completeness is a contract conversation. | A coverage certificate — our record of one source on one day — per source_id and partition_date. row_count is JSON null wherever we never read that day. |
Corpus
What each side holds
| RavenPack | PIT | |
|---|---|---|
| Depth | Their pages date the analytics product to 2003 and cite 40,000-plus premium sources. | 587,689 and counting rows across seven sources: ten months of SEC backfill from 2008-09 on, and a live tape recording since 2026-08-26. |
| Sentiment and events | The product. | Neither exists here, and neither is on the roadmap. |
| Filings as the object | An input to the analytics. | The thing you are buying. |
Payload
The rows carry no filing text yet
If you are scoring PIT rows yourself, this is the constraint to design
around. A row holds form type, company name, accession, CIK, five clocks, a
content hash and the SEC URL. The filing text is not in there yet. Any score
computed over a cut is therefore a score over metadata, plus whatever the
scoring model already knew about the period. Filing text is being ingested
now. Until it lands, fetch the document from source_locator and
score that.
Price
What is published, and what is not
RavenPack publishes no self-serve price grid, so treat it as enterprise pricing and get a quote. Roundups that print a RavenPack dollar figure are not quoting a first-party source, which is why no figure appears here.
PIT is Researcher $29, Power $79 or Desk $499 a month. All three read the whole ingested history, and all three are internal use. Plans and what the corpus covers.
Limits
Where RavenPack is the better buy
- PIT has no event sentiment score, no composite score and no news factor.
- PIT holds ten months of SEC filing metadata against their two decades of scored premium news.
- PIT publishes no score, so there is no accuracy comparison to run against theirs.
- PIT holds no SOC 2 report.
Check it
Self-serve as-of, in one call
If the job is a scored news factor, this is not the product. If the job is the information set at an instant on the public record, the sample runs without an account.
Responses carry sample: true. Security posture is on /security.
Nearby