> 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/get-started/prerequisites.md).

# Prerequisites

Get your environment ready before your first real build.

A production build needs three things: the DataOS Command Line Interface (CLI), the Local Development Kit (LDK) for authoring and testing, and a Git repository that DataOS can access during deployment.

Complete the following steps once. Then use the [Quickstart](/build/get-started/quickstart.md) to create your first Data Product.

{% hint style="info" %}
**New to DataOS?** Confirm with your DataOS administrator that you have a user account and access to your organization's DataOS context before you start.
{% endhint %}

<table><thead><tr><th width="195.6884765625">Step</th><th>What it does</th></tr></thead><tbody><tr><td><a href="/build/get-started/prerequisites/cli-setup.md">CLI setup</a></td><td>Install and authenticate <code>dataos-ctl</code>, the tool you use to apply and inspect DataOS Resources.</td></tr><tr><td><a href="/build/get-started/prerequisites/ldk-setup.md">LDK setup</a></td><td>Install the Local Development Kit (LDK): Python, a virtual environment, Vulcan, and a local engine.</td></tr><tr><td><a href="/build/get-started/prerequisites/repository-setup.md">Repository setup</a></td><td>Connect your Git repository so DataOS can pull your project at deploy time.</td></tr></tbody></table>

You connect your data sources as the first step of [Understand → Connect sources](/build/understand/connect-sources.md), not here. Connecting a source is part of understanding it, so that step belongs there rather than here.

{% hint style="warning" %}
**You will also need access to run what you build.** DataOS is deny-by-default, so a new `Data Developer` starts with no access to shared compute, Depots, or Secrets. These are granted, not self-served: you request a `Can Use` grant for each from your tenant admin. Sort this out before you deploy. The full checklist is in [Operate → Get access and confirm readiness](https://v2.dataos.info/operate/data-product-developer/access-and-readiness).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/build/get-started/prerequisites.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.