Use case
One project spine for cross-functional fleets
Projects link briefs, assets, QA runs, guardrail violations, and release records — so marketing, design, engineering, and ops share stage language instead of siloed tool tabs.
Who is this for?
Small platform teams running multiple brands from one Mac fleet workspace with Creytix ECP as operator console.
Typical workflow
Project create in root-brand-platform → stage progression Intake→Monitor → Creytix Chat handoffs on blockers → client portal traffic light for external stakeholders.
Next step
Explore the modules behind this workflow
Forge, Studio, Design Labs, Inspector, Prompt Guard, and Releases connect through one project record.