> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/environments/executor-images.md).

# Executor images

Build and manage your organization's own environments.

An **executor image** is an environment your organization builds and shares, so everyone works from the same packages. Admins manage them from **Executor Images**, in the Workspace sidebar.

{% hint style="info" %}
Executor Images is available to organization admins on eligible plans.
{% endhint %}

## Creating an image

An image is defined by:

| Part                      | Details                                                      |
| ------------------------- | ------------------------------------------------------------ |
| **Language**              | Python or R                                                  |
| **Packages**              | The Python or R packages to install, with versions if needed |
| **Linux packages**        | Any system packages the image needs                          |
| **Environment variables** | Settings available to code at run time                       |

You can start from a [preset](/zerve-docs/environments/environment-presets.md) and add to it. Zerve builds the image from your definition, which can take a few minutes for large images.

## Default images

Each organization can mark **one image per language as the default**. New notebooks use the default image, so a team can standardize on one approved set of packages.

## When to use executor images

| Situation                            | Why an image helps                                                           |
| ------------------------------------ | ---------------------------------------------------------------------------- |
| **Your team uses the same packages** | Everyone gets an identical environment, so results are reproducible          |
| **You need approved versions**       | Pin the package versions your organization has approved                      |
| **Builds take a long time**          | Build the image once, rather than installing large packages in each notebook |


---

# 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://docs.zerve.ai/zerve-docs/environments/executor-images.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.