Storage and limits
See what each plan includes, where disk and backup storage go, and what to do when you get close to a limit.
On this page
A hosting plan sets four limits: processor cores, memory, disk and backup storage. Environments share the processor and the memory. Disk is the one thing they cannot share, because each environment is a copy. This page explains where the space goes and what you can do when it runs short.
What each plan gives you
| Plan | Processor cores | Memory | Disk | Backup storage |
|---|---|---|---|---|
| Starter | 2 | 4 GB | 80 GB | 250 GB |
| Business | 4 | 8 GB | 160 GB | 500 GB |
| Scale | 8 | 16 GB | 320 GB | 1 TB |
| Max | 16 | 32 GB | 640 GB | 2 TB |
| Ultra | 4, reserved for you | 16 GB | 160 GB | 1 TB |
| Hyper | 8, reserved for you | 32 GB | 240 GB | 2 TB |
| Apex | 16, reserved for you | 64 GB | 360 GB | 4 TB |
A plan is one server, and a server runs one project. For prices, see Plans and prices.
Disk: one copy per environment
The disk of your server is shared by all environments of your website, and each environment takes its own part of it:
- its releases: the current one and the earlier ones kept for rollback,
- its database and the data of its other services,
- its persistent folders, such as uploaded files.
A staging environment filled from live is therefore about as large as live. The portal shows storage per environment, so you can see where every gigabyte goes.
Backup storage
Backups are kept away from your server, in backup storage that comes with the plan. It is counted on its own, and the portal shows how much of it each environment uses. How backups are made and kept is described in Backups and restore.
Processor and memory
All environments share the cores and the memory of the plan. Your live site always keeps what it needs. The portal shows what each environment uses.
Inside one environment, you can cap what each part may use with resources in .tilizy/app.yaml:
resources:
php:
mem: 1g
cpus: 2
redis:
mem: 256m
The keys are php, webserver, builder and the type of each service. To give one environment different limits, set resources under environments. See The project file.
When you get close to a limit
The portal shows what each environment uses, and tells you when a bigger plan would help, and why. Before you change the plan, check whether you can free space.
| To free | Do this |
|---|---|
| Disk | Remove environments you no longer need with tilizy app:destroy -e <branch>. This deletes their database and files for good. |
| Disk | Create a secondary environment without the files of live when you only need the database: tilizy app:create -e <branch> --files=false. |
| Disk | Make releases smaller with plugins.prune in the project file: documentation, tests, and extensions that are not enabled. |
| Processor and memory | Pause environments you are not using with tilizy app:stop -e <branch>. Their data stays on disk, so this does not free disk. |
To see what is inside a persistent folder of an environment:
tilizy files:list --mount files -e staging
The output is a listing of the files in that folder, three levels deep unless you pass --max-depth. The name after --mount is the persistent name from your project file. The command needs a permission on the project and is refused without it.
Extras
When you need more space but not a bigger server, add storage to your plan:
- Site storage: €10 per 100 GB, per month.
- Backup storage: €10 per TB, per month.
Prices exclude VAT. Larger servers, dedicated servers and servers with a graphics processor are available on request.
What can go wrong
- A paused environment still fills the disk. Pausing frees processor and memory only. Remove the environment to free its disk space.
- A command meant for staging acts on live. The
filescommands use the live environment when you give no flag. Pass-e <branch>or--stagingwhen you mean another environment, above all withtilizy files:rm. - A limit that is too low. A
resourceslimit caps that part even when the server has memory to spare. Raise the limit before you conclude that the plan is too small.
Next: Environments and Plans and prices.