Limits and quotas
The limits on a Drasken Cloud organisation — CPU, memory, storage, projects, apps, databases, volumes, jobs, domains and monitors — and how they grow.
Each organisation has limits on what it can run at once — CPU, memory, storage and the number of projects, apps, databases and other resources. Limits grow on their own as you use them, up to a ceiling, and you can ask for more. See yours under Organisation → Limits.
What are the limits?
New organisations start with these limits, which grow with use up to the ceiling:
| Resource | Starting limit | Grows up to |
|---|---|---|
| vCPU | 8 | 64 |
| Memory | 16 GB | 256 GB |
| Storage | 250 GB | 4 TB |
| Projects | 5 | 50 |
| Apps | 20 | 200 |
| Databases | 5 | 50 |
| Volumes | 20 | 200 |
| Scheduled jobs | 20 | 200 |
| Custom domains | 10 | 100 |
| Uptime monitors | 10 | 10 |
Organisation → Limits always shows your organisation's current limits, which may differ.
What happens at a limit?
At 100%, new resources and scale-ups are refused with a message saying which limit was reached. What is already running isn't affected. You get an email as you approach a limit.
How do I get a higher limit?
Select Request more on Organisation → Limits, or open a support request.
Can I cap a project?
Yes. Edit caps on Organisation → Limits sets how much of the organisation's limits one project may use, so one project can't use everything.
Are there other limits?
| Limit | Value |
|---|---|
| Instances per app | 1 to 20, depending on the size |
| Ports per app | 1 to 10, one of them public |
| Environment groups per app | 10 |
| Volumes | 5 per app, 20 per project; 1 to 100 GB each |
| Database size | Up to 4 vCPU and 16 GB of memory |
| Database connections | Set by the plan |
| Job run time | 30 seconds to 24 hours |
| Invitations | 20 addresses at a time, each valid for seven days |
Last updated on