---
title: "Workspace Limits"
description: "Every limit your workspace runs into, what is in use, and how to ask for more."
---
A workspace runs into a handful of limits that are not about the resource plan you paid for: how many replicas one process can run without a resource, how many applications can mount one shared storage volume, how much Usage Billing usage you can run up before you are charged mid-cycle, and how large a single Usage Billing workload can be.
**Limits** (under **Manage** in the dashboard), or `GET /api/v1/workspace/limits`, lists every one of them with its current value and what the workspace is using right now - so you find out about a limit before it refuses you, not from a `422`. Any workspace member can read it.
| Limit | What it limits | Default on Team | Can be raised |
|---|---|---|---|
| `replicas_per_process` | Replicas (or the autoscaling maximum) of one process - the web or a worker - on Usage Billing, or scaling beyond a resource's plan | 20 | Yes |
| `mounts_per_volume` | Applications mounting one [shared storage](/persistent-storage/shared-storage) volume | 10 | Yes |
| `databases_per_workspace` | PostgreSQL, MySQL, and Valkey databases in the workspace, read replicas included | 40 | Yes |
| `buckets_per_workspace` | [Buckets](/persistent-storage/buckets) in the workspace | 100 | Yes |
| `charge_threshold` | Unbilled [Usage Billing](/pricing/usage-billing) usage at which you are charged before the renewal | starts at $25, grows with paid renewals | Yes, while there still is one |
| `cron_minutes_per_resource` | [Cron minutes](/deployments/cron-jobs#included-cron-minutes) a resource's plan includes each billing cycle | 1,000 at the plan's own size | No - this one is set for enterprise contracts only, and not by request |
| `hobby_process_cpu` / `hobby_process_ram` / `pro_process_cpu` / `pro_process_ram` | The largest single workload of each CPU class on Usage Billing or in the workspace pool | the largest size on sale of that class | No - a larger workload needs a resource instead |
| `volume_size` | The largest disk a single Usage Billing workload can hold | 1 TB | No |
A database your `app.json` or compose file declares is never refused for `databases_per_workspace` - what is already running keeps running.
## Limits by workspace plan
The first four limits follow your workspace plan. Personal has half of Team's, Organization one and a half times, and Enterprise twice:
| Limit | Personal | Team | Organization | Enterprise |
|---|---|---|---|---|
| `replicas_per_process` | 10 | 20 | 30 | 40 |
| `mounts_per_volume` | 5 | 10 | 15 | 20 |
| `databases_per_workspace` | 20 | 40 | 60 | 80 |
| `buckets_per_workspace` | 50 | 100 | 150 | 200 |
Moving to a higher plan raises them at once. A value Miget set for your workspace - on request or not - replaces your plan's and stays when you change plans, so moving to a higher plan does not raise it. Moving to a lower plan deletes nothing: you cannot add databases, buckets or mounts past the new limit, and a process above the new replica limit is scaled down to it at its next deploy.
## Asking for more
A refusal for crossing a raisable limit ends with "Ask for more on the Limits page." To ask, click **Request increase** next to the limit, or call `POST /api/v1/workspace/limits/increase_requests` with:
- `limit` - the limit's key
- `requested_value` - what you are asking for, in the limit's unit (replicas, mounts, databases, buckets, or cents for `charge_threshold`)
- `reason` - what you need it for
This needs the `workspace:billing` permission, since a higher limit means a higher possible bill - a workspace API token cannot carry it, so this call needs a personal token. Only one request per limit can be waiting at a time; a second is refused with `422`.
A request is not an instant change. Miget reviews it by hand and emails you once it is decided - approved, possibly at a different value than you asked for, or declined with a reason.
## Next steps
Sizes, rates, the monthly minimum, and the spend limit.
Mount one volume across several applications.