> For the complete documentation index, see [llms.txt](https://docs.orbitfin.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbitfin.ai/part-2-how-it-works/2.3-one-home-for-all-your-data.md).
# 2.3 One home for all your data
Research data is fragmented by default, and the fragmentation is expensive. Public filings live in one system, market and pricing data in another, news in feeds, broker research in inboxes and shared drives, and a firm's own notes, models, and meeting records scattered across teams and individuals. Each source has its own way of naming companies, its own access method, and its own gaps. The work of pulling them together for any given question — and making sure they all refer to the same company — falls on the analyst, every time. It is repeated, manual, and never reusable.
Orbit's answer is to be the one home for all of it. Every source sits in the same place, anchored to the same entity master, and is queryable as a single body of knowledge. The data falls into three kinds.
**Public data** is the global corpus Orbit sources and maintains: company filings, earnings transcripts, sustainability and regulatory documents, news, and market data, spanning more than 60,000 listed companies across the Americas, APAC, and Europe, with over a decade of history behind it. This is the shared foundation every client starts from, and it arrives already connected — not as a feed to be integrated, but as part of the linked layer.
**Internal data** is the firm's own: broker research it receives, analyst notes, proprietary models, meeting records, and any other documents it holds. Brought into Orbit, this private material is anchored to the same entity master as the public corpus, so a firm's own view of a company sits directly alongside the full public record of that company. This is where much of the value is, and it is covered in full in 2.7.
**Third-party data** is the specialist sources a firm subscribes to or wants to bring in — additional data providers, niche feeds, alternative datasets. Rather than living in yet another silo, these too can be connected through the backbone and read alongside everything else.
> *Caption: One company, every source — public, internal, and third-party — in a single view.*
The point of putting all three in one place is not tidiness; it is that the combination is worth more than the sum. A question answered across public filings, market data, the firm's internal research, and third-party feeds at once is a question that previously required pulling from four systems and reconciling the results by hand. Connecting internal research into the public corpus, in particular, is where a firm's proprietary edge meets the full public record — its analysts' private view, set against everything publicly known, in a single query. That is the combination no individual source can offer and no general-purpose tool can assemble, because it depends on the backbone underneath.
This is also the most direct expression of what it means for Orbit to be infrastructure rather than a tool. A tool is one more source a firm adds to the pile. Infrastructure is the layer that holds the pile together. When all of a firm's research data lives in one connected home, every capability above it — asking, monitoring, automating — operates across everything at once, rather than across one fragment at a time. The breadth of the foundation is what gives the rest of the platform its reach.
The same layer also includes a private space — a sandbox — where a firm's own data lives securely within the platform, governed in one place rather than spread across personal drives and inboxes. How that data is secured, and how it is connected, is covered in Parts 2.7 and 5; the point here is simply that it belongs in the same home as everything else.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.orbitfin.ai/part-2-how-it-works/2.3-one-home-for-all-your-data.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.