> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Agent home for Datum, with what it is, pricing, and how to act: https://agents.datum.net
> If you can only fetch URLs: read https://www.datum.net/docs/llms.txt in full and open the most specific page for the task. Commands, limits, and field paths are on task, operations, and limits pages, not on section overviews. Pages described as "Documentation is coming soon" are placeholders.
> If you have a shell or can save files: download https://www.datum.net/docs/llms-full.txt (every page, about 740 KB) once and search it with grep, instead of fetching pages one at a time.
> datumctl describes itself: `datumctl api-resources` lists resource types and `datumctl explain <resource>` shows a schema. To act on live resources, use Datum MCP or datumctl. To search the docs, use the Docs MCP server at https://www.datum.net/docs/mcp.

# Compute limits and quotas

> Request access to Compute, check your project's compute quota, and review the fixed limits of the Compute preview.

For features that Compute doesn't support yet, see [Limitations and roadmap](/docs/compute/limitations-and-roadmap.md).

> [!NOTE]
>
> Compute is in preview, and the `v1alpha` API can change.

## Request access

Compute is enabled for each project separately, and Datum approves each request manually. Until a project has access, every `datumctl compute` command except `access` and `help` stops and asks you to request access. This includes `build`.

To request access for the active project, follow these steps:

1. To check the current state, run the following command:

   ```bash theme={null}
   datumctl compute access
   ```

   The `Status` line shows a state such as `Not requested`, `Pending approval`, `Active`, `Denied`, or `Revoked`.

2. To submit a request and wait for a decision, run the following command:

   ```bash theme={null}
   datumctl compute access request --message="MESSAGE" --wait
   ```

   Replace `MESSAGE` with a short description of what you plan to run. The message helps Datum review your request.

3. Wait until the `Status` line shows `Active`. You can then deploy workloads.

If a request is denied or access is revoked, submit a new request with `datumctl compute access request --renew`. For all access options, see [Compute commands](/docs/datumctl/compute/overview.md#requesting-access).

## Quotas

Your project's compute quota limits how many workloads and Instances you can run, how much vCPU and memory they use, and how many shell sessions can be open at once. Datum sets the quota. You can't change it yourself.

Each Instance uses the following quota:

* 1 Instance
* 1 vCPU
* 2 GiB (2,048 MiB) of memory

Quota is shared across [runtime classes](/docs/compute/runtimes/overview). A `general-purpose` Instance and a `unikernel` Instance use the same amount.

### Check your quota

To see your project's limits and usage, run the following command:

```bash theme={null}
datumctl compute quota
```

The output is similar to the following:

```text theme={null}
Quota for project your-project-id

RESOURCE    UNIT        LIMIT   USED   AVAILABLE   USAGE
Workloads   workloads   10      3      7           [######--------------]  30%
Instances   instances   50      12     38          [#####---------------]  24%
vCPUs       vCPUs       32      8      24          [#####---------------]  25%
Memory      MiB         65536   16384  49152       [#####---------------]  25%
```

To show only the resources that are at their limit, add `--constrained`.

### If your quota is used up

If your project doesn't have enough quota for a new Instance, Datum doesn't start it. The Instance shows `Pending (quota exceeded)` in `datumctl compute instances` and reports `QuotaExceeded`, and the workload reports `QuotaNotGranted`. To let the Instance start, do one of the following:

* Lower the number of Instances with `datumctl compute scale WORKLOAD_NAME --min=COUNT`.
* Delete workloads that you no longer need.
* Ask for more quota by contacting [support@datum.net](mailto:support@datum.net).

If an Instance reports `QuotaNoBudget`, or another reason that starts with `Quota`, your project's quota isn't set up correctly. The workload exists, but its Instances don't start. Contact support, and Datum fixes the problem.

## Limits

The following table lists fixed limits:

| Item | Limit |
| - | - |
| Instance type | `datumcloud/d1-standard-2` only: 1 vCPU and 2 GiB of memory |
| Instances in each location of a [placement](/docs/compute/placement-and-scaling.md) (`minReplicas`) | 1 to 1,000 |
| Network interfaces for each Instance | Exactly 1 |
| Networks for each workload | 1 |
| Size of each referenced ConfigMap or Secret | 256 KiB |
| Total size of referenced ConfigMaps and Secrets for a workload in one location | 1 MiB |
| ALBs attached to each workload with `datumctl compute deploy` | 1, on one port |
| Unikernel image size | The unpacked image must fit in the Instance's 2 GiB of memory, along with the app. |
| Open shell sessions per Instance | 3 |
| Open shell sessions per project | 10 by default. Datum can grant a project more. |

## What's next

* To deploy your first workload, see [Deploy an app](/docs/getting-started/first-workload.md).
* To review what Compute doesn't support yet, see [Limitations and roadmap](/docs/compute/limitations-and-roadmap.md).
* To fix quota errors and other problems, see [Troubleshooting](/docs/compute/troubleshooting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.