Control plane
Creytix Forge
Creytix Forge intake, scaffold, Brand DNA gates, and Higgsfield queue — the fleet command surface for new sites.
Control plane
Creytix Forge
Forge is the fleet command surface for new sites — Creytix Forge intake, scaffold scripts, Brand DNA validation, and Higgsfield staging queues before any page ships.
What does Creytix Forge do?
Forge registers workspace templates, runs brand:scaffold-site, locks VISUAL_DNA, and wires essence URLs into HF staging jobs. ECP Creytix Forge at localhost:3010 is the operator UI; creytix.com/forge is the public module overview.
When do you use Forge?
Start every net-new site or major vertical here. Intake questions, asset tier gates, and Connect registry rows land in Forge before Studio or Design Labs touch customer routes.
Operator entry vs this public page
This page is a marketing overview. Operators run Creytix Forge on Creytix ECP (local: localhost:3010/?tab=site-forge). Creytix Connect registry row site-forge.scaffold lists native fleet tools registered before per-site routes wire.
Legacy Creytix Forge redirect
tianguisforge.com will 301 to this module when Cloudflare rules are live — see docs/creytix/CREYTIX_LEGACY_REDIRECTS.md.
Key capabilities
Creytix Forge intake
Pattern brief, route classes, and asset manifest from one ECP panel.
Brand DNA gates
VISUAL_DNA lock required before Nano Banana batches enqueue.
HF staging queue
Prep chain, submit order, and Flow upload — fleet SSOT in brand/.
Creytix Connect registry
Cross-site tools register here before per-site routes wire.
Related modules in the Creytix stack
Creytix Forge connects to other umbrella modules — explore adjacent lanes before you contact us.
Operator surface preview
Platform UX mock (CREYTIX024) — full gallery on /platform.
Auto Prompt System
Every net-new site starts with a locked master prompt pack — brand/creytix/AUTO_PROMPT_SYSTEM.json exports tone, safety, SEO, and review modules into brand/creytix/prompt-pack/. Run Forge Prompt Studio on ECP or regenerate from the example intake JSON before Nano batches enqueue.
- Manifest SSOT
- brand/creytix/AUTO_PROMPT_SYSTEM.json
- Example intake
- brand/forge/examples/auto-prompt-intake.creytix.example.json
- Prompt pack
- brand/creytix/prompt-pack/
- Regenerate
- npm run brand:forge:auto-prompt -- --intake brand/forge/examples/auto-prompt-intake.creytix.example.json
Platform scope & Creytix Connect
Fleet tracker platform.forge phase 2 — Creytix Forge intake, scaffold, and Brand DNA gates on ECP locally. Wireframe persist + Creytix Forge import handoff still in progress; prod ECP URL TBD.
- Fleet tracker row
- platform.forge
- Connect registry
- site-forge.scaffold
- Fleet phase
- 2 · Beta (operator)
- ECP tab (dev)
- ?tab=site-forge
Registry SSOT: brand/creytix/CREYTIX_CONNECT_REGISTRY.json · Tracker: docs/fleet/FLEET_SERVICES_PHASE_TRACKER.json
One platform
The full Creytix suite — Forge, Studio, Design Labs, Inspector, Prompt Guard, and the IDE.
Six modules, one governed workspace — no separate logins, no per-tool billing.
See all modules
Explore the umbrella
See how modules connect
Creytix Forge is one lane in the Creytix stack. Browse related modules and Connect capabilities on the homepage — use Admin sign in in the header for the operator console.