Ship overview

Publish & releases — deploy policy, webhooks, and scoped push from approval to production.

Note

Creytix Ship is where a reviewed change becomes a release — the last stop after Studio and Inspector, before it's live.

Overview

Creytix Ship is what happens after your team decides a change is ready — it's the gate and the mechanics that move an approved change from your workspace to production, and tells the rest of your stack that it happened. Instead of a deploy being a separate, disconnected step from the QA and review work you already did, Ship checks the same gates and keeps a record of exactly what shipped.

How it works

Deploy policy gate — before anything goes out, Ship checks QA and review status on the change, so a broken or unreviewed change can't slip through.
Scoped push — an approved change goes out along a defined path, rather than an unscoped push straight to production.
Notify — a release record is kept and webhooks fire, so other tools and your team know what shipped and when.

Steps

•
Open Ship in the Control Panel
From the Creytix Control Panel, open Releases to see pending and completed changes.
•
Review the deploy policy gate
Check whether a change clears the QA and review status the gate requires before it can ship.
•
Push the approved change
Once the gate passes, push the change through Ship rather than around it.
•
Check the release record
Confirm the release was recorded and any connected webhooks fired as expected.

Capabilities

Deploy policy gate — checks QA and review status before a change is allowed to ship.
Release records — a record of what shipped, when, and from which change.
Webhooks — other systems, including your own tools, get notified when a release happens.
Scoped push — ship a specific, reviewed change rather than an all-or-nothing deploy.

Limits & honest scope

Ship is built around Creytix workspaces — it isn't a general CI/CD platform you'd point at an arbitrary, unrelated codebase.