Operator workspace

Creytix platform overview

The rails behind "writes the code, builds the site, runs the client" — Connect native tools, team chat, mail ops, SEO pipeline, and commerce rails, plus operator UX mocks. Sign in from the header when you need the operator console.

Creytix platform studio — five module chips and Connect tool lanes

Eight departments, one platform

Everything a site needs, in-house

Every Creytix workspace ships all eight departments together — pick one below to see what it does and where it lives in the docs.

Planning & intake

Creytix Forge

Creytix Forge intake, Brand DNA gates, scaffold, and naming — structure before any page generates.

  • Creytix Forge intake
  • Brand DNA validate
  • Scaffold + manifest
  • Forge Prompt Studio
Open docs →
Creytix Forge intake wizard — pattern brief canvas and Brand DNA lock gate

How it works

One workflow, start to finish

  1. 1 · Plan

    Intake, Brand DNA, and structure before anything generates.

  2. 2 · Build

    Studio + Design Labs produce on-brand pages and assets.

  3. 3 · Govern

    Inspector + Prompt Guard catch issues before they ship.

  4. 4 · Ship

    Supervised deploys with gates and rollback readiness.

The operating path

Every product moves through the same governed system.

Define, design, build, verify, ship, operate, then learn. Control is built into the path — Brand DNA, tests, audit trail, environments, recovery — not bolted on after launch.

Skip to lantern chaptersSkip story — the page stays readable with motion off.

01 / Define

Forge · Brand DNA · project intake

Work starts with requirements, constraints, and identity — not an unstructured prompt.

Open Define →

02 / Design

Studio · Design Labs

The product is designed as a reusable system before components multiply.

Open Design →

03 / Build

IDE · governed AI workflows

AI can produce work quickly inside the project’s real context.

Open Build →

04 / Verify

Inspector · Prompt Guard

Code, UX, prompts, security, and release readiness are checked before exposure.

Open Verify →

05 / Ship

Release controls · environments · client handoff

Shipping is governed, observable, and recoverable.

Open Ship →

06 / Operate

Inspector · Mail · Chat · Shield · Workforce (MVP)

The product remains operable after launch — within the honesty table.

Open Operate →

07 / Learn

The Creytix Method · Playbooks · Guide

The team builds repeatable capability instead of depending on a prompt expert.

Open Learn →
The story

Lantern journey

Start with a plan before the first prompt.

One active workspace frame at a time. The stone companion uncovers the path with a lantern. The teal Guide — in the cards beside each operating stage — teaches the gate.

Skip to proof

  1. 01 / Someone has an idea

    Someone has an idea

    A napkin sketch is enough to start — Forge turns it into a brief, Brand DNA, and a governed build. Not a vibe-coded landing page.

    Lantern: The lantern finds the sketch and traces a small structure.

    Resolved: Notes become a coherent blueprint silhouette.

    Forge · Brand DNA · intake

    Creytix Forge →
    Founder sketching a product idea — Creytix starts before the dashboard
  2. 02 / The idea becomes a live product

    The idea becomes a live product

    Design Labs locks tokens. The IDE writes and ships. Build is done when something is live, not when a mock exists.

    Lantern: The beam enters the product frame and holds the edges.

    Resolved: A controlled product crop — no invented UI lettering.

    Design Labs · Studio · IDE

    Creytix IDE →
    Creytix IDE on the dark operator shell — write and ship a live product
  3. 03 / Proof: sites Creytix actually runs

    Proof: sites Creytix actually runs

    First-party fleet marks, not invented customers. Names without a locked logo stay names.

    Lantern: Light isolates real marks and leaves gaps honest.

    Resolved: A governed logo wall of sites we operate.

    /sites · locked fleet logos

    Every site →
    ExpediaParts
    Expedia Reman Transmissions
    Expedia Reman Engines
    EarnedStar
    AlignHeart
    AlignAlgo
    Gold Medal Injury
    House of Bid
    Sancochi
    Praxium Law
    Creytix
  4. 04 / Support stays on

    Support stays on

    Inspector, Mail, Chat, and Shield keep the live site honest. Not a 24/7 human agency.

    Lantern: Light follows an issue from signal to organized action.

    Resolved: Verified, calm recovery — status colors only when they mean something.

    Inspector · Mail · Chat · Shield

    Creytix Shield →
    Operator watching fleet health — post-launch care in the same OS
  5. 05 / Get found, then add what works

    Get found, then add what works

    SEO OS, Social, and Mail grow the site. Frontier Bind and Playbooks add features. Workforce when hiring starts.

    Lantern: The beam expands through search and content motifs into an ordered system.

    Resolved: Distribution is a lane in the OS, not a second vendor stack.

    SEO OS · Social · Mail · Frontier Bind

    Creytix SEO OS →
    Growth as a system — search, social, and the same Creytix OS
  6. 06 / Then the company itself

    Then the company itself

    Payroll-lite, books connection, tax guidance — when those matter, Creytix stays on. Not a loan. Not ADP or QuickBooks today.

    Lantern: Copper light maps fragmented tools into an installed pattern.

    Resolved: Takumi’s systemize moment: repeatable work leaves a deterministic tool.

    Workforce payroll-lite · Books · Tax guidance · Takumi

    Creytix Books →
    Business records and guidance in Creytix — operate the company in the same OS

The Creytix Method

Build the system. Learn the method.

Creytix does not just produce the next output. It shows your team why the step exists, what good looks like, and how to recover when the project changes — so every project leaves the business more capable than the last.

Playbooks guide the work inside the product. Articles and docs teach the operating pattern in public.

  • Founder

    From idea to governed launch

    1. Turn the business goal into a product brief
    2. Lock scope, roles, and Brand DNA
    3. Review generated architecture before implementation
    4. Approve release evidence — not just a visual preview
  • Builder

    Generate inside the project, not a chat

    1. Work in the same repo, DNA, and gates
    2. Treat AI output as a reviewable change set
    3. Do not ship until Inspector and Prompt Guard pass
  • Reviewer

    Block on evidence

    1. Status colors mean pass, warning, or blocker — never decoration
    2. Customer-facing AI needs evaluation evidence
    3. Handoff includes environments and recovery

Absorb the glue

Creytix is redefining its core to absorb Zapier-like workflow tasks natively.

Event triggers, routing, approvals, notifications, and the internal tools that usually live in a separate automation bill belong in the operating system — not in another login.

Fragmented stack

Zapier connects fragmented tools.

Glue sits between apps. Every repeated flow stays an integration — billed, fragile, and outside the product you actually run.

Native core

Creytix replaces the fragmentation.

Takumi finds the glue work. Creytix absorbs it into the core — a tool you own, not a zap that has to keep firing.

Compare the stack →

Public comparison pages — not a 9,000-integration catalog.

Creytix Connect registry

SSOT: brand/creytix/CREYTIX_CONNECT_REGISTRY.json — native tools register here before per-site routes wire.

  • Team & guest messaging

    Creytix Chat

    3 tools registered

  • Checkout & events

    Commerce

    3 tools registered

  • Creytix Mail ops

    Store & Mail

    2 tools registered

  • Organic pipeline

    SEO & growth

    3 tools registered

  • Site intake & HF

    Forge tools

    4 tools registered

Full tool catalog → /docs/connect/overview

Connect tool groups

  • Team + assistant

    Creytix Chat

    Deterministic chat assistant, internal thread bridges, and guest support widgets — native fleet tools, not Composio SaaS.

    • Creytix Chatintegrated
    • Internal chat mirrorshipped
    • Support chat widgetshipped
  • Creytix Mail

    Store & Mail

    Campaign enqueue, staff inbox, and transactional rails — build-only Creytix Mail stack under the Creytix Mail customer label.

    • Creytix Mail enqueueowned
    • Creytix Mail inboxowned
  • Organic + programmatic

    SEO OS

    SEO pipeline ingest, page generation enqueue, and Growth & AEO playbooks — free-tool stack, no Ahrefs subscription required.

    • SEO OS pipelineshipped
    • Page generationshipped
    • Growth & AEOintegrated
  • Attached rails

    LLM & models

    Local Creytix models on fleet minis, BYOK cloud keys, Higgsfield Nano/Seedance, Dev Agent tiers, and deterministic Creytix Brain routing.

    • LLM connectionsintegrated
    • Ollama SEO (mini-tool)integrated
    • Higgsfield Nano Banana Prointegrated
    • Dev Agent BYOKintegrated
  • Checkout + events

    Commerce

    Checkout tool with IDV, events ticketing pilot, and native booking-kit scheduling — fleet packages before per-site routes.

    • Creytix Arrivemvp
    • Checkout toolshipped
    • Creytix Eventsshipped
    • Cal bookingshipped

Creytix Connect

Native fleet tools — registered before routes ship

Cross-site capabilities register in Creytix Connect and wire through Forge — chat, commerce, mail, SEO, and intake tools without horizontal SaaS lock-in. Grouped from CREYTIX_CONNECT_REGISTRY.json.

Full tool catalog → /docs/connect/overview

Team & guest messaging

Creytix Chat

Native chat assistant, internal team mirrors, and storefront support widgets — wired through Creytix Connect without Composio-scale SaaS.

Creytix Chat — split thread view with tools panel and handoff chips
  • Creytix Chat assistant

    Live

    Deterministic tools assistant with module context sync and Forge handoffs.

    creytix.chat.assistantDocs →
  • Internal chat mirror

    Live

    Slack and RingCentral connectors into the operator team-chat surface.

    internal-chat.mirrorDocs →
  • Storefront support chat

    Live

    Guest widget routed to sales and CS queues on gamma storefronts.

    support.chat.widgetDocs →

Related module overview →

Checkout & events

Commerce

Events ticketing, checkout verification, and public BFF routes — fleet packages registered before per-site wiring.

Commerce checkout — identity verification and liveness step rail
Events ticketing admin — tier capacity bars and waitlist strip
  • Creytix Events

    Live

    Catalog, tiers, cart stub, and scan-at-door ticketing for pilot sites.

    events.ticketingDocs →
  • Checkout tool

    Live

    Identity verification, fraud review, and payment intent flows.

    checkout.toolDocs →
  • Scheduling & booking

    Live

    Native booking-kit appointments — Cal.com self-host wire-later on fleet minis.

    scheduling.cal-bookingDocs →

Creytix Mail ops

Store & Mail

Self-hosted Creytix Mail enqueue and staff inbox — customer-facing Creytix Mail labels on native fleet rails.

Creytix Mail composer and inbox split on the dark operator shell
Operator intake inbox — triage queue with priority pills
  • Creytix Mail enqueue

    Live

    Workspace campaign batches and structured export packs from Studio.

    mail-gorilla.enqueueDocs →
  • Operator inbox

    Live

    Staff JWT BFF inbox for communications queue on Expedia admin.

    tianguis-mail.inbox

Organic pipeline

SEO & growth

SEO OS ingest, programmatic page generation, and Growth playbooks — free-tool stack, no Ahrefs lock-in.

Creytix SEO OS dashboard with crawl graph and index-gate checklist on dark chrome
SEO OS dashboard — crawl rotation and index gate checklist
  • SEO OS pipeline

    Live

    Weekly ingest, GSC rotation, and index gates on fleet storefronts.

    seo-os.ingestDocs →
  • Page generation

    Live

    Programmatic landing enqueue with human review gates before publish.

    page-generation.enqueueDocs →
  • Growth & AEO

    Beta

    Answer-engine optimization playbooks paired with Design Labs governance.

    growth.aeoDocs →

Related module overview →

Site intake & HF

Forge tools

Creytix Forge scaffold, Brand DNA naming, path registry, and Higgsfield Flow submit — register in Connect before site routes wire.

Creytix Forge intake dashboard with DNA lock gate on dark chrome
Creytix Forge intake wizard — pattern brief canvas and Brand DNA lock gate
  • Creytix Forge scaffold

    Live

    Intake, asset manifest, and brand:scaffold-site from one ECP panel.

    site-forge.scaffoldDocs →
  • Forge Prompt Studio

    Beta

    Brand naming CLI and auto prompt system builder — first steps on every site.

    forge.creator-toolsDocs →
  • Path registry

    Live

    Curated fleet paths, combinatorial resolver, and dry-run apply smoke.

    forge.path-registry
  • Higgsfield Flow submit

    Live

    Chrome CDP batch submit with essence URLs and master queue order.

    hf.flow.submitDocs →

Related module overview →

Six precision modules — Forge · Studio · Design Labs · Inspector · Prompt Guard · Releases

Platform stills gallery

CREYTIX018–029 operator UX mocks — WebP masters at public/creytix/. Wired on homepage Connect sections and module pages where copy fits. Sync after ingest: npm run brand:site-assets:sync -- --slug=creytix

Creytix Connect registry — abstract operator panel with native tool lanes

CREYTIX018

Connect registry overview

ECP Connect panel — native tool grid with status pills.

Creytix Chat — split thread view with tools panel and handoff chips

CREYTIX019

Creytix Chat thread

Team chat with module context and Forge handoff chips.

Creytix Mail — campaign composer with block lanes and enqueue preview

CREYTIX020

Creytix Mail composer

Campaign enqueue with brand-locked preview panel.

SEO OS dashboard — crawl rotation and index gate checklist

CREYTIX021

SEO OS dashboard

Crawl rotation, index gates, and snippet targets.

Commerce checkout — identity verification and liveness step rail

CREYTIX022

Checkout verify flow

Identity upload and face-scan liveness step.

Creytix platform studio — five module chips and Connect tool lanes

CREYTIX023

Platform studio shell

Operator UX — module switcher and eco dashboard strip.

Creytix Forge intake wizard — pattern brief canvas and Brand DNA lock gate

CREYTIX024

Creytix Forge intake

Pattern brief, route classes, and DNA lock gate.

Inspector diff triage — side-by-side panels and classification matrix

CREYTIX025

Inspector diff triage

Screenshot classify matrix — fix vs accept vs baseline.

Events ticketing admin — tier capacity bars and waitlist strip

CREYTIX026

Events ticketing admin

Tier capacity, venue map stub, and waitlist panel.

Operator intake inbox — triage queue with priority pills

CREYTIX027

Operator queue inbox

Founder queue + software-operator intake slice.

Freight tracking console — shipment timeline and route trace

CREYTIX028

Freight track console

Shipment timeline and carrier adapter status.

Compliance readiness hub — framework checklist columns and progress rings

CREYTIX029

Compliance readiness hub

Framework checklists — no paid GRC SaaS.

Creytix AI Business OS home dashboard on a dark teal operator shell

CREYTIX030

Business OS hero dashboard

Operator home — module tiles on the dark Creytix shell.

Creytix Forge intake dashboard with DNA lock gate on dark chrome

CREYTIX031

Creytix Forge dashboard

Site intake, Brand DNA lock, and scaffold gates.

Creytix IDE split editor and agent panel on the dark operator shell

CREYTIX032

Creytix IDE dashboard

Governed agent workspace — editor and agent panel.

Creytix Inspector side-by-side triage dashboard on dark chrome

CREYTIX033

Creytix Inspector dashboard

Screenshot triage and release-gate matrix.

Creytix Design Labs token and component matrix on the dark shell

CREYTIX034

Creytix Design Labs dashboard

Token swatches and code-native component matrix.

Creytix Command Center operator hub with status chips on dark chrome

CREYTIX035

Command Center dashboard

Operator hub — gates, inspect, daily OS control.

Creytix OS three-column canvas for Build, Be Found, and Systemize on a dark teal shell

CREYTIX036

Build + Be Found + Systemize

Three-column OS canvas — build, discovery, systemize.

Creytix SaaSI pipeline — learn, design and implement, then exit, with the deterministic system that remains once no agent is running

CREYTIX037

SaaSI pipeline

AI enters to learn, design, and implement — then exits routine work and leaves behind deterministic systems. Stage names track the canon and the three cards rendered beneath it on the homepage. Quarantine lifted 2026-09-01: the Qwen still (CJK UI, hex labels, orange truck) was replaced by a deterministic render, and the homepage was switched onto it — SaasiPipelineVisual, the interim English stand-in, is gone.

Split Creytix still — fragmented tool pile on the left, unified native core on the right

CREYTIX038

Native core vs fragmented tools

Disconnected app tiles versus one absorbed operator core.

Creytix Takumi consultant panel stepping away from an installed deterministic tool

CREYTIX039

Takumi consultant

Consultant panel stepping away after installing a tool.

Creytix SEO OS dashboard with crawl graph and index-gate checklist on dark chrome

CREYTIX040

Creytix SEO OS dashboard

Crawl graph, index gates, and snippet targets.

Creytix Mail composer and inbox split on the dark operator shell

CREYTIX041

Creytix Mail workspace

Campaign composer and staff inbox on one OS shell.

Creytix Prompt Guard eval matrix and guardrail checklist on dark chrome

CREYTIX042

Creytix Prompt Guard

Eval matrix and guardrail checklist.

Creytix Playbooks saved procedures and routine runner on the dark operator shell

CREYTIX043

Playbooks and routines

Saved procedures and a routine runner.

Have a code from email or QR?