Deployment templates

Your profile now has a Sign-ins section. Connect Google or GitHub to sign in with it, remove a connected sign-in after confirming it is you, and set a password if your account was created with one of them.

You can now start a new order while an earlier one is still being set up or not finished yet. Opening an order link asks whether to start the new order or go back to one you have, and each order has its own status page.

Company › Orders lists every order placed for your company, with its state, who placed it and a link to its status page. It is shown to the company's owner and to anyone with a billing role.

The Control Panel has a simpler menu (Home, Managed Websites, Managed Clusters, Tickets and Company), and you can now create a CoreStack site, a fully managed website with its own staging environments, and choose a Standard or Performance server type you can change later. CoreStack and CoreCluster sites have a Logs tab, company owners and billing contacts can add a card or set up a Direct Debit and see usage and invoices under Company › Billing, and new customers can order online.

AI agents connected to the control panel's MCP server can read its guides and playbooks, use its ready-made prompts, and open the log viewer, usage charts, smoke test and site picker as apps inside the conversation, in AI apps that support them. Every logs query says the exact time window it read.

A deployment's page now says which revision of your company's deployment template, or of Corefinity's default, each stage was built from, and which stages that environment sets for itself.

Use the Feedback button at the bottom right of any page, or press Shift+F, to report a bug, suggest a feature or ask for a new platform. You can add a screenshot of the page and mark it up; passwords and other secrets on screen are hidden automatically.

Every CoreStack site now deploys in three stages, build, database and post-deploy, which you edit on the Deployments tab, each line with its own step and time limit. Existing pipelines are converted automatically, a group of sites at a time, and deploy exactly as before; credentials written into commands are moved into encrypted variables.