Creytix
Sign in
ReferenceLive

Connect registry schema

The nativeTools[] and plannedProducts registry shape.

Creytix Connect registry — abstract operator panel with native tool lanes

Overview

Every tool in the Creytix Connect catalog — Mail, SEO OS, Scheduling, Checkout, and the rest — is described by the same underlying shape. That's what lets the docs sidebar, the /platform catalog, and tier badges all stay consistent instead of drifting page by page. This page describes that shape at a conceptual level: what a registry entry captures, not the internal wiring behind it.

How it works

Each entry in the registry answers the same handful of questions, regardless of which department the tool belongs to:

  • What is it? A customer-facing label and a short capability summary.
  • Which department owns it? Every tool maps to one of the eight Creytix departments (Forge, Design Labs, Studio, Connect, Inspector, Prompt Guard, Ship, Dev).
  • How mature is it? A tier — Live, Building, or Preview — that drives the badge you see on the page and in the sidebar.
  • What does it replace, if anything? An optional comparison to the SaaS product a customer would otherwise be paying for.

Two related lists sit behind the catalog: tools that are shipped and in active use today, and products that are still being planned or built toward general availability. Both are entries in the same schema — they just differ by tier.

Steps

  1. •

    Find a tool's page

    Every registry entry corresponds to one doc page under /docs/connect/... (or its owning department for umbrella modules).

  2. •

    Read the tier badge

    The badge at the top of the page — Live, Building, or Preview — reflects the tier field for that entry. Live means available today; Building and Preview mean the honest-scope section is doing real work.

  3. •

    Check the replaces comparison

    If a tool has a vendor comparison, it shows up as a simple table: the Creytix tool on one side, the SaaS product it replaces on the other.

  4. •

    Cross-check against the department

    A tool's department tells you which part of the Control Panel it lives under, and which sibling tools it's grouped with.

Capabilities

  • One shape, whole catalog — every tool, from shipped Connect services to in-progress Dev features, is described consistently.
  • Drives the tier badges — Live/Building/Preview labeling across docs and the /platform catalog comes from this same source.
  • Powers the replaces comparisons — the vendor-swap tables you see across the guides and Connect docs are pulled from this registry.
  • Department-grouped — every entry belongs to exactly one of the eight departments, so navigation stays predictable.

Limits & honest scope

This page documents the shape of the catalog for readers, not a public API.

  • There's no customer-facing API to query the registry directly today — this page is a documentation-level description, not an endpoint contract.
  • The schema evolves as new tools and departments are added; a field described here at a conceptual level may be represented differently internally, and that internal representation isn't something we publish.
  • Tier changes (a tool moving from Building to Live, for example) are reflected here and in the changelog — but not on a fixed release calendar.

Related