# Account limits and quotas: what they are and how to raise them

https://www.gyrohosting.com/en/knowledgebase/article/hesap-sinirlari-ve-kotalar

- **What you will learn**: which limits your account has, where to see your current usage and how to raise a limit.
- **Time**: 4 minutes

## 1. Why limits?

Limits protect your account: a leaked API key or a faulty script cannot open hundreds of servers and drain your balance. New accounts get a lower limit in their first days. If you really need more, we raise the limit on request.

## 2. Default limits

| Limit | Default | How to raise |
| --- | --- | --- |
| New account, first 7 days (prepaid cloud) | 5 Gyro Cloud Istanbul servers, 1 container environment | Support ticket |
| Gyro Cloud Istanbul servers per account | 10 | Support ticket |
| Largest single server | 32 vCPU / 256 GB RAM / 4000 GB disk | Fixed |
| Custom server templates | 10 | Support ticket |
| Additional IPv4 per server | 5 (at most 3 additions per hour) | Support ticket |
| Additional disk per server | SSD 500 GB, HDD 2048 GB | Support ticket |
| Snapshots per server | Per plan (Istanbul plans: 3) | Support ticket |
| Servers ordered through the API | 10 | Support ticket |
| Services per order | 25 | Support ticket |
| Paid API operations per day | 50 (resets at 00:00 Istanbul time) | Support ticket |
| API requests per key | 60 per minute | Fixed |
| Sub-account keys / SSH keys / webhooks | 20 (resellers 1000) / 50 / 10 | Support ticket |
| Projects | 50 | Support ticket |
| Firewall rules per server | 10 + 20 per extra rule pack | Extra pack or support ticket |
| Security groups | 5 per server, 50 per account, 60 rules per group | Support ticket |
| Storage buckets and access keys | Per plan | Bigger plan or support ticket |
| Bucket renames | 5 per bucket, 10 per service per day | Support ticket |
| DNS zones | Free 5, Pro 50 (per service) | Pro plan or support ticket |
| Services per container environment | Mini 3, Small 5, Starter 10, Standard 20, Pro 40, Serverless 30 | Bigger plan or support ticket |
| Copies per service | Mini 3, Small 3, Starter 5, Standard 10, Pro 20, Serverless 10 | Bigger plan or support ticket |
| Gyro Pipeline | 10 pipelines, 1 parallel build, 300 build minutes a month per environment | Support ticket |
| Uptime monitors | Plan + extra monitor packs | Extra pack |
| One-click app (re)installs | 3 per server per hour | Wait (rate limit) |

If a limit was raised for you, the effective value always shows in the list in the next section.

## 3. See your limits and usage

**gyro CLI:**

```
gyro limits
```

The output starts with the new-account limit (e.g. "Istanbul servers 2/5"), then every limit with its maximum, your usage and how to raise it. `*` marks a limit changed for your account.

**API:** `GET /api/v1/client/cloud/account/limits` (the `cloud_read` scope is enough). The answer has `new_account` (new-account limit and when it ends) and the `limits` list (`key`, `limit`, `used`, `how_to_increase`).

**Terraform:** the `data "gyro_account_limits" "this" {}` data source returns the same list; use it in a `precondition` to stop a plan that would go over a limit before anything is applied.

## 4. When you hit a limit

The client area, API, CLI and Terraform give the same explanation: which limit, its value, your usage and how to raise it. Sample CLI output:

```
Error: New accounts can run at most 5 Istanbul cloud servers during the first 7 days (you have 5). Please contact support to raise the limit.
  (code: limit_exceeded, HTTP 422)
  To raise the limit: gyro ticket create --department-id 3 --subject "Limit increase: new_account.servers" --message "..."
  All limits and usage: gyro limits
```

In the API answer `error.details` holds `limit_exceeded: true`, `limit_key`, `limit`, `current`, `how_to_increase` and a ready ticket request (`support_ticket`). A price quote (`dry_run`) warns in advance with `quote.limit_exceeded`; the CLI then stops without asking for confirmation.

## 5. Raise a limit (support ticket)

1. In the client area open **Support** > **New ticket** and choose the **Order** department.
2. Put the limit in the subject (e.g. "Limit increase: new_account.servers").
3. In the message, write the new value you need and briefly what you are building.

The same ticket from a terminal or a script:

```
gyro ticket create --department-id 3 \
  --subject "Limit increase: new_account.servers" \
  --message "Requested limit: 10. Reason: staging and production cluster."
```

API: `POST /api/v1/client/tickets` with `{"department_id": 3, "subject": "...", "message": "..."}` (the key needs the `Tickets/CreateTicket` scope). An AI agent can open it too: the `support_ticket` field of the error is a filled-in request.

## 6. Frequently asked questions

**Is raising a limit paid?**

No. A limit only sets how much you can open; you pay for the services you use.

**When does the new-account limit end?**

Automatically 7 days after registration; then the account-wide limits apply. `gyro limits` and `ends_at` in the API answer show when.

**Which limits cannot be raised?**

API requests per key per minute, the largest single server size and short rate limits (e.g. 3 app installs per hour) are fixed. For a rate limit, wait a few minutes and retry.

**Plan limit or account limit?**

Buckets, zones and container services depend on your plan; a bigger plan or an add-on raises them at once. If you need more than the largest plan, open a support ticket.

## Next step

- **How to open a ticket:** [Opening a support ticket](https://www.gyrohosting.com/en/knowledgebase/article/destek-talebi-acma).
- **Automation:** [Gyro Cloud Istanbul: API, CLI and Terraform](https://www.gyrohosting.com/en/knowledgebase/article/gyro-cloud-istanbul-api-cli-terraform).
- **Prepaid usage:** [Getting started](https://www.gyrohosting.com/en/knowledgebase/article/on-odemeli-kullanim-baslarken).