About 3spread

SEC filings are public. Usable SEC data isn't.

Every public company in the United States files detailed financial reports with the SEC: income statements, balance sheets, cash flows, insider transactions, institutional holdings, proxy statements, and more. It's one of the richest datasets in the world, and it's entirely free to access.

The problem is that “free to access” and “ready to use” are very different things. Every company structures its filings differently. They use different labels for the same data points, different layouts for the same tables, and different conventions for the same disclosures. Comparing two companies means hours of manual reconciliation. Building a pipeline across thousands of companies means building an entire data normalization infrastructure from scratch.

The existing solutions fall into two camps. Enterprise vendors like FactSet and Bloomberg solve the problem, but at price points that start in the hundreds of thousands and scale into the millions, designed for institutions with dedicated data budgets. Smaller vendors either don't cover the full breadth of filing types, can't maintain consistency across companies, or charge prices that don't reflect what they're actually delivering.

We started 3spread because we think that's a solvable problem. Public companies file their data with a public agency. It exists to serve the public, and there's no reason it should be this hard to use. So we did the hard part, and for the community we give it away: the full datasets through our API. The data was always yours. We just make it usable.

Who we are

3spread is a small team based in Denver, Colorado. Our backgrounds span mathematics, engineering, and finance, including time spent in banking and at major tech firms.

We built 3spread because we lived the problem firsthand. As long-time investors, we spent years reading through filings and trying to integrate that data into our own analysis. The experience was consistently painful. Not because the information wasn't there, but because getting it into a usable format required more engineering work than the actual analysis. When we looked at what was available, we found enterprise platforms we couldn't afford and smaller providers that couldn't deliver the consistency we needed.

So we decided to build it ourselves.