Registry

IAI Service Registry

This page is the current domain-by-domain registry for the iai.one ecosystem. It records intended role, hosting layer, and the observed live response as of March 28, 2026.

Observed Snapshot

Temporal note

The statuses below are a live verification snapshot taken on March 28, 2026. This registry should be updated whenever DNS, custom-domain routing, or product ownership changes.

Domain Role Stack Observed State Notes
iai.one Charter / constitutional root Wix 301 → www.iai.one, then 200 Public root is live and appears to front the main charter-style site through Wix.
home.iai.one Portal entry surface Cloudflare Pages 200 HTML Acts as the system-entry portal for the broader IAI stack.
app.iai.one Web app apex Cloudflare Pages / Next.js routing 302 → www.app.iai.one, then 200 Apex currently redirects into the live V2 web app surface hosted at www.
flow.iai.one AI Workflow Builder Cloudflare Pages 200 HTML Primary workflow builder and runtime-facing UI.
api.iai.one Platform REST API Cloudflare Worker 200 JSON Root exposes version and route list for user, post, verification, lesson, media, and IPFS operations.
api.flow.iai.one Flow Engine API Cloudflare Worker 404 JSON at root Worker is reachable, but root is not a landing endpoint. Treat it as an explicit route surface, not a homepage.
docs.iai.one Documentation hub Cloudflare Pages 200 HTML Canonical knowledge base for architecture, flows, app, mail, API, and service map.
dash.iai.one Dashboard entry shell Cloudflare Pages 200 HTML Live HTML includes a client-side redirect toward /dashboard/.
developer.iai.one Developer portal Cloudflare Pages 200 HTML Live title and content describe an IAI Developer Portal for APIs, SDKs, and node development.
noos.iai.one Civilization OS meta-architecture Cloudflare Pages 200 HTML Intended NOOS surface is live, though the current page title appears to carry older Muon Noi investor-shell branding.
cios.iai.one AI control layer / Customer Intelligence OS Cloudflare Pages + separate backend repo 200 HTML Live shell presents an AI Agent Flow control-layer message and the repo also contains API/backend foundations.
mail.iai.one Mail UI + delivery operations VPS / Hetzner / Mailcow 200 HTML Current surface is Mailcow login UI fronted by nginx, not a Pages-hosted app.
cdn.iai.one CDN surface Cloudflare CDN DNS unresolved Could not resolve host on March 28, 2026. Treat as planned or unpublished until DNS is live.
flows.iai.one Automation / n8n surface n8n DNS unresolved Could not resolve host on March 28, 2026. Document as intended automation surface, not as live public infrastructure yet.

Layered View

Public Entry + Constitution

iai.one and home.iai.one together define the public narrative layer: charter, portal, orientation, and system entry.

Product Surfaces

app.iai.one, flow.iai.one, dash.iai.one, and developer.iai.one are the operator, builder, dashboard, and developer-facing shells.

Execution + Service Interfaces

api.iai.one, api.flow.iai.one, mail.iai.one, cdn.iai.one, and flows.iai.one form the service and infrastructure interface layer.

Strategic Control Layers

noos.iai.one and cios.iai.one sit above daily app usage as higher-order architecture and control-layer surfaces.

Documentation Build Priority

  • Done in this phase: establish a single registry page so the docs hub reflects every listed domain, including unresolved and route-only surfaces.
  • Done in this phase: add dedicated docs pages for dash.iai.one, developer.iai.one, noos.iai.one, and cios.iai.one.
  • Done in this phase: add surface pages for iai.one, home.iai.one, mail.iai.one, cdn.iai.one, flows.iai.one, and the Owner Checklist.
  • Then: split API docs into platform API, Flow Engine API, mail delivery API, and developer-facing SDK/onboarding paths.
  • Finally: publish CDN and n8n docs only after DNS and public entrypoints are live, so docs do not imply availability that users cannot reach.