Deploy safety

Deploying a theme to a live Ghost site should never be a surprise. Inflozo is designed so a deploy is explicit, validated, and recoverable.

Nothing happens automatically

The planned deploy flow will never deploy or activate a theme on its own. You start a deploy, confirm the details, and choose whether to upload only or upload and activate. The first deploy to a connected site is gated behind a backup confirmation you must check.

Validated before upload

The planned deploy flow generates an export artifact and runs GScan against your target Ghost version, and the confirmation screen shows validation status and any compatibility warnings before you proceed.

routes.yaml stays manual

Inflozo is designed never to upload routes.yaml through the Ghost Admin API. When a project uses routes, you get the file plus step-by-step manual upload instructions.

Recovery

The planned deploy flow stores the previous artifact reference so you can attempt to re-activate a known previous Inflozo deployment if Ghost still accepts it. This is recovery support, not a full Ghost site restore.

What is planned

Direct deploy opens with the builder. Until then, this page describes the deploy contract. See export for the artifacts a deploy reuses.

Inflozo is pre-launch, so parts of this describe planned behaviour. Have a question? See support or contact us.