# Limits on Aria Cloud: apps, services, databases and more

> Every public limit of Aria Cloud in one place: apps per server, services and databases per aria.yaml, versions, backups, email and plans.

Source: https://getaria.cloud/docs/limits (updated 1 November 2026)

One Aria server runs up to 5 projects, and one `aria.yaml` holds up to 12 services and 6 databases. Memory is the limit that matters first: Aria estimates your stack before you pay and names the smallest plan that fits. These limits are the ones the product enforces today. Where a number is a default that Aria's team can change, the table says so.

## What are the limits?

| Limit | Value | Notes |
|---|---|---|
| Projects on one server | 5 | The default. Each project also has to fit in the server's memory. |
| Services in one `aria.yaml` | 12 | A service is a `web`, `api`, `worker` or `static` entry. |
| Databases in one `aria.yaml` | 6 | Postgres, Redis or Supabase. |
| Variables in one `aria.yaml` | 200 | Under `env`. |
| Size of `aria.yaml` | 64 KB | |
| Volumes on one service | 8 | |
| Paths in `access_exceptions` | 20 | On a service with `access: owner`. |
| Projects in one workspace | 10 | A default that Aria's team can change. |
| Servers in one workspace | 10 | A default that Aria's team can change. |
| Workspaces you own | 10 | A default that Aria's team can change. |
| Free address | 3 to 48 characters | Lowercase letters, numbers and hyphens, with at least one letter. |
| Service memory limit | 128 MB to 64 GB | The `memory` field. By default twice Aria's estimate. |
| Name of a service, database, volume or registry | 31 characters | Lowercase letters, digits and dashes, starting with a letter. |
| A build or start command | 1,000 characters | One line, with no backticks, single quotes or `$( )`. |

## Which databases and versions can I run?

| Database | Versions | Notes |
|---|---|---|
| Postgres | 16 and 17 | Leave `version` out unless you need to pin one. Extensions: `vector`, `pg_trgm`, `btree_gin`, `btree_gist`, `fuzzystrmatch`, `citext`, `pgcrypto`, `uuid-ossp`, `hstore`, `unaccent`. |
| Redis | 7 | A cache. It is password-protected and not restored from backups. |
| Supabase | The official self-hosted stack | Needs about 4 GB of memory on its own. See [Self-hosted Supabase](https://getaria.cloud/docs/supabase). |

There is no MySQL, MongoDB or object store. Postgres and Redis addresses have no TLS, so an app that insists on SSL has to be told not to.

## What can a plan do?

- **Grow or shrink.** A bigger plan grows the server in place where it can, with one restart. Where it cannot, Aria moves your app to a bigger server and shows you the price and the downtime first. A smaller plan moves your apps to a smaller server, once what they use fits and they are running. See [Servers and plans](https://getaria.cloud/docs/servers).
- **Run in one place.** A plan is one server in one location, which you choose when you pay. It is not spread across regions.
- **Be a private VPS.** A managed plan has no customer root login. SSH reaches the server only from Aria's control network, so you work through `aria.yaml`, [Aria AI](https://getaria.cloud/docs/aria-ai), the [command line](https://getaria.cloud/docs/cli), the app and your [coding agent](https://getaria.cloud/docs/agents).
- **Dedicated and GPU servers** are by request, with a consultation. They have no public price. Email hello@getaria.cloud with the memory, cores and disks you need.

## What are the limits for backups?

| Limit | Value |
|---|---|
| Nightly backups | Every Postgres database, every volume and Supabase with its Storage files. Kept 30 days by default. |
| A `backup` block: retention | Defaults of 14 daily, 8 weekly and 6 monthly. You can keep 1 to 90 days, 0 to 52 weeks and 0 to 36 months. |
| A `backup` block: schedule | A five-field cron in UTC, at most once an hour. |
| Backup hook timeout | 1 to 600 seconds, 120 by default. |
| Redis | Not restored. |

See [Backups](https://getaria.cloud/docs/backups) for how to restore and how to hold your own key.

## What are the limits for email?

Port 25 is blocked on a managed server, so an app cannot send straight to other mail servers. Send through [Aria Mail](https://getaria.cloud/docs/mail), or through a mail provider on port 465 or 587.

| Limit | Value |
|---|---|
| Recipients in one email | 50 |
| Attachments in one email | 10 MB in total |
| Included in the price | 2,000 emails a month across your workspace, then £0.50 per 1,000. See [Aria Mail](https://getaria.cloud/docs/mail). |
| Sending from | A domain the project owns. The free address cannot send email. |

## What are the limits for the command line and agents?

- `aria logs` shows 1 to 2,000 lines, 200 by default.
- `aria db url` gives a temporary login for 10 to 480 minutes, 60 by default.
- An agent's `db_query` returns at most 500 rows, and runs as a read-only role.
- A key can be limited to one project, and you can revoke it at any time. See [the safety model](https://getaria.cloud/docs/mcp).

## What are the limits for your data?

| Limit | Value |
|---|---|
| The Archive | Deleted users, rows and files wait 30 days. |
| Copy database | The download link works for one hour. |
| Direct access | Open for two hours from one computer. |
| Credentials on screen | 60 seconds. |

## What are the limits for Aria AI?

Attachments, pictures and message length are on [Aria AI](https://getaria.cloud/docs/aria-ai).

## Where do I go next?

[Pricing](https://getaria.cloud/pricing) has every plan. [A managed VPS for developers](https://getaria.cloud/managed-vps-for-developers) explains what the server is and is not. The [aria.yaml reference](https://getaria.cloud/docs/aria-yaml) lists every field.

Next: [Aria Cloud documentation](https://getaria.cloud/docs)