Skip to app details
Back to app library
APPNEURAL APP FAMILYPeople & Operations

Setup

Set up every app on a domain, verified

Every app on a domain set up step by step: DNS, hostname, deploy, secrets, then a live check.

01 / OVERVIEW

See where it fits in your day.

Add a domain and every catalog gets the same six steps: confirm the zone, add its DNS record, attach the hostname in wrangler.jsonc, deploy with its schema, set its secrets and open it. The guide knows each app's real production host from the repository registry (82 catalogs), so the DNS target is always the app's own host (never a CNAME to itself); an app without a host is shown its workers.dev URL instead. Verify DNS resolves through Cloudflare DNS-over-HTTPS and check https://<host>/health (then /) from the Worker; a passing check marks the steps it proves, and progress per domain, app and step is kept in D1. Select any apps and run one domain-wide sweep: DNS and health for every host, four at a time, with each app's result, DNS and health status, its steps done and the overall setup percentage, plus apps ready. Admin only: EDIT_PASSCODE sign-in, same-origin writes, progress scoped to the saved domain.

A LOOK INSIDEExample layout · sample content
Setup
AppIllustrative configuration
01Campaign · ok · okExample
02Setup · ok · okExample
03Appearance · no recordExample
02 / CAPABILITIES

Built around the work you do.

What Setup does for you.

01

Six steps per app

Confirm the domain, add DNS, attach the hostname, deploy with its schema, set secrets and open it.

02

Live checks

DNS resolves through Cloudflare and /health answers 200; a passing check marks the steps it proves.

03

Domain-wide sweep

Check the selected apps together: each app's DNS and health, its steps done and the overall percentage.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Setup. What you can do depends on your access in the app.

01

Add the domain

The guides then use that domain's real hostname for every app.

02

Work the checks

Copy each DNS value and command, deploy, then verify DNS and the host.

03

Run the sweep

Check the selected apps in one go and see which hosts still need work.

YOUR NEXT MOVE

Make Setup part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P1VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Add a domain and every catalog gets the same six steps: confirm the zone, add its DNS record, attach the hostname in wrangler.jsonc, deploy with its schema, set its secrets and open it. The guide knows each app's real production host from the repository registry (82 catalogs), so the DNS target is always the app's own host (never a CNAME to itself); an app without a host is shown its workers.dev URL instead. Verify DNS resolves through Cloudflare DNS-over-HTTPS and check https://<host>/health (then /) from the Worker; a passing check marks the steps it proves, and progress per domain, app and step is kept in D1. Select any apps and run one domain-wide sweep: DNS and health for every host, four at a time, with each app's result, DNS and health status, its steps done and the overall setup percentage, plus apps ready. Admin only: EDIT_PASSCODE sign-in, same-origin writes, progress scoped to the saved domain.

Priority
P1
Portfolio
People & Operations
Capability
People & Operations
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:18
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

setup schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

setup.appneurox.com DEPLOYED

setup.appneurox.com

Worker
setup-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:18
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/setup-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app