> 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/operate/data-developer/data-product-developer.md).

# Overview

A **Data Developer** builds and operates Data Products and data-movement pipelines within a Tenant using **Vulcan** for Data Products and **Nilus** for data movement, along with the Secrets and Depots they use.

This section is the **operations** side of that work, the day-to-day running and maintenance that [Build](https://v2.dataos.info/build) does not cover. Build tells you *how* to author models, semantics, contracts, and how to deploy; Operate covers what surrounds it: getting the access and resources you need, promoting across environments, keeping a live product healthy, and the governance you are responsible for. When you need the how-to, this section links into Build.

## What you run and maintain

* [Get access and confirm readiness](/operate/data-developer/access-and-readiness.md): the roles and grants you need, and a checklist that the tenant can actually run your product.
* [Deploy and promote across environments](/operate/data-developer/deploy-and-promote.md): the operational path from a dev tenant to production.
* [Manage Data Product access](/operate/data-developer/governance.md): the access policies your product enforces, and who you let consume it.
* [Operate your product](/operate/data-developer/operate-your-product.md): runs, failures, versioning, breaking changes, and the cost of what you run.

By default you hold no access to shared Compute, Depots, Minerva, or Secrets; each needs an explicit `Can Use` grant from your [Tenant Admin](/operate/tenant-admin/governance.md). So your first stop is [Get access and confirm readiness](/operate/data-developer/access-and-readiness.md).

## What you cannot do

* **Manage access to resources you didn't create:** Unlike Tenant Admin and Data Admin, you don't hold `manage-access-other-users-resources`: you can view others' resources, but only their owner (or an admin) can grant you rights on them.
* **Administer the Lakehouse:** Structuring namespaces, schemas, tables, and views beyond your own product's needs is [Data Admin](/operate/data-admin/data-admin.md)'s job.


---

# 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/operate/data-developer/data-product-developer.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.