Deployments queued on the same pipeline now go live in the order they were started

Pick the 4-hour slot for routine maintenance on each website, CoreCluster or your whole company. It is 00:00–04:00 UK time unless you change it.

Add your IP address once for your company, a website, one environment or just for yourself, with Add my IP on the environment's page. It opens SSH, and on CoreStack and CoreCluster it also lets you past HTTP authentication and maintenance mode.

On CoreStack and CoreCluster, add SSH keys for your agency, company, website or a single environment in one place, in the Corefinity control panel or through its API, and see every key that can reach an environment and where it came from.

On CoreStack and CoreCluster, everyone with access to an environment can log in over SSH with their own username and personal key, alongside the shared web username.

When you restore a snapshot, you can now choose another environment of your website as the destination, for example to restore a production snapshot into a staging environment. You confirm the destination by typing its name before anything in it is replaced.

Magento 2 sites on CoreStack and CoreCluster can now serve pages from Varnish. Switch it on or off, choose its version, purge it by URL, tag or pattern, add your own VCL with validation, history and revert, and follow its hit ratio in the Corefinity control panel, the API and the MCP tools; deployments purge it for you.

A redirect rule can now apply to chosen domains of a site instead of all of them, so two shops on one site can each keep their own redirects. On its domains a limited rule runs before the rules for every domain.

On every CoreStack environment you can now run a separate PHP application in a folder of your site (such as a WordPress admin), serve a folder of files, block a path, or limit a path or host name to a list of addresses, from the Nginx tab. Only the PHP files you list ever run, and every change is checked before it goes live.