> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/build/stage-1-discover/bring-data-in.md).

# Bring data in

Use this section when the data you need for your Data Product does not yet exist in the source system. Nilus is DataOS’s data movement framework for managing data movement between various source systems and the engine powering your Data Product. It supports different data movement modes depending on how fresh the data needs to be and what the source system supports.

***

## Choose your data movement mode

<table><thead><tr><th width="140.804931640625">Mode</th><th width="383.472900390625">Best for</th><th>Freshness</th></tr></thead><tbody><tr><td><strong>Batch</strong></td><td>Large volumes, scheduled syncs, full or incremental loads from databases, warehouses, or SaaS platforms</td><td>Minutes to hours</td></tr><tr><td><strong>CDC</strong></td><td>Operational databases where every insert, update, and delete must be captured without full reloads</td><td>Near real-time</td></tr><tr><td><strong>Stream</strong></td><td>Event streams and message queues where records must be processed continuously as they arrive</td><td>Near real-time</td></tr></tbody></table>

If you are unsure which mode fits, start with Batch. Use CDC when you need row-level change capture from a transactional database. Use Stream when your source produces continuous events through systems such as Kafka or NATS.

***

## Next steps

* [Batch Data Movement](/build/stage-1-discover/bring-data-in/batch-ingestion.md): schedule-driven data movement from databases, warehouses, and APIs.
* [Change Data Capture](/build/stage-1-discover/bring-data-in/cdc-ingestion.md): capture inserts, updates, and deletes from operational databases.
* [Streaming Data Movement](/build/stage-1-discover/bring-data-in/streaming-data-ingestion.md): ingest events continuously from sources such as Kafka or NATS.

***


---

# 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, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/build/stage-1-discover/bring-data-in.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.