What changed in Shipways

Most of the time somebody opens the panel on a phone, they are away from a laptop and want to know one thing. Is the machine still checking in? Did the deploy go out? So the panel now has a phone layout.

• The rail moves into a drawer behind a compact context bar that keeps the organization, server and site in view.
• Tables drop the columns a row can do without. Each row's menu stays on screen, because nothing on a phone can hover to reveal it.
• Controls are sized for a finger, and dialogs open as bottom sheets.
• Field help sits behind an info button, so a narrow screen shows state and what a change will do, not paragraphs.

Nothing about what the panel can do changed. Everything it does on a laptop it does on a phone.

When a deploy fails, the first thing anybody asks is which step stopped and what it printed. An assistant connected to Shipways over MCP can now ask the same thing.

• list-deployments finds deployments started anywhere: from the panel, from a push, from CI or from the assistant itself.
• deployment-status names the step that stopped and quotes its last lines.
• deployment-log reads any step's output in full.

Both redact secrets before anything leaves the panel.

A Composer or npm install that fails with 401, 403 or 404 on a private package usually means the machine has no login for that host. list-package-credentials says which hosts have one. Adding a login is still something a person does in the panel.

list-sites now also shows the source control account each site uses. When the organization already has an account for the repository's owner, it suggests that one.

Shipways is now priced by the machines it manages, and by nothing else.

Prices exclude VAT. Paying yearly costs ten months.

Every plan has every capability. Sites, databases and deployments are not counted, and neither are people on a paid plan. Free is for your personal organization and has no end date. It replaces the trial.

Students, open source projects and non-profits can apply for Studio from Billing in the panel. It is granted for a year at a time and renewed for as long as you still qualify.

Importing a Forge server already moved each site's code, environment, database and workers onto a machine Shipways runs. What it left to you was the last mile: pointing the domain at the new machine and requesting its certificate.

That part is now guided. Each moved site shows its last two steps, with a live check of where every one of its names currently resolves. A name behind Cloudflare's proxy is recognised for what it is, not reported as pointing somewhere else. The top of the import says what to do next.

The site's own certificate is requested once the move is finished, when the name already points at the new machine. It is no longer requested while the name still points at Forge.