What changed in July 2026
The July 2026 changelog has the full details.
Object storage and a Resources page
A new Resources page in the dashboard shows your organisation's object storage and managed caches in one place. You can create object storage, attach it to any application environment, detach it and delete it. The environment receives the credentials as environment variables on its next deploy, with an optional name prefix. Templates that use object storage can provision it during a one-click template deploy.
Server-side commands with qc exec
Cloud CLI v0.6 adds
qc exec, which runs a command in a one-off container for your environment. The run continues if your laptop sleeps or your connection drops. You can watch the output, detach and re-attach later. Runs are capped at one hour.Startup grace period
You can set a startup grace period in the create and edit environment forms and through the API. During the grace period, failing health checks do not cause a newly started container to be replaced. The value is between 0 and 3600 seconds, and the default is 120.
Payload CMS template
You can create a Payload CMS 3 application from a template. It runs the Payload website starter with a managed PostgreSQL database and keeps uploads on a persistent volume. The template generates its secret key when you create the application.
Managed cache in more places
You can now add June's Redis-compatible managed cache when you create an application from a template, a pre-built application or a GitHub repository. A new Cache tab on the environment metrics page charts memory use, hit rate, processing units and connections.
PHP performance settings
Applications on the Quant PHP base image, including the Drupal and WordPress templates, can tune the PHP opcode cache with
PHP_OPCACHE_*environment variables. The defaults are unchanged. Static files such as images, CSS and JavaScript now send 7-day cache headers by default, so the CDN serves them instead of your application storage.
By the numbers
- maximum run time for qc exec
- 1 hour
- maximum startup grace period
- 3600 seconds
- PHP base image static cache
- 7 days
Action needed
- Rebuild your application to apply the new PHP and static file cache settings.
Who it is for
Application developers
Run imports and migrations server-side with
qc exec, and give slow-starting applications more time to become ready.Teams with shared files
Keep uploads, exports and generated files in object storage, and attach the same storage to more than one environment.
PHP application teams
Tune the PHP opcode cache with environment variables, and let the CDN serve your images, CSS and JavaScript files.
How it works
Object storage belongs to your organisation, not to one application. The Resources page lists it next to your managed caches. You can attach the same object storage to several environments, and every environment that you attach sees the same objects. When applications share object storage, agree on a folder layout first. When you attach storage, you can set a name prefix for its environment variables. The credentials take effect on the environment’s next deploy, so redeploy after you attach.
qc exec is for long jobs that must continue when your connection drops, such as imports and migrations. It runs the command server-side, and the CLI only watches the output. If you close the CLI, the run continues. Use the run ID to re-attach:
qc exec status <run-id> --watchUse --container to pick a container when your environment has more than one.
The startup grace period is a maximum, not a fixed delay. A container that passes its health checks early goes into service early, so a higher value does not slow a healthy deployment. The compose and create-environment APIs now also accept the single-task setting. It runs one container at a time and turns off scaling for the environment.
For PHP applications, the new static file cache headers are on by default. Set QUANT_STATIC_CACHE=0 to turn them off.
Get started
Create object storage
Open the Resources page in the dashboard and create object storage.
Attach the storage
Expand the resource, then select an application and an environment.
Redeploy the environment
The environment receives the storage credentials on its next deploy.
Set a grace period
Use the create or edit environment form. Pick a value from 0 to 3600 seconds.
Run a remote command
Install Cloud CLI v0.6 or later. Read Remote commands.
Related: Explore Quant Cloud · Documentation · July 2026 changelog
Ready to try it on Quant?
Use Quant Cloud on your own project, or read the docs first.