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.
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:
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 callPOST /api/v1/workspace/limits/increase_requests with:
limit- the limit’s keyrequested_value- what you are asking for, in the limit’s unit (replicas, mounts, databases, buckets, or cents forcharge_threshold)reason- what you need it for
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
Usage Billing
Sizes, rates, the monthly minimum, and the spend limit.
Shared storage
Mount one volume across several applications.

