Six steps per app
Confirm the domain, add DNS, attach the hostname, deploy with its schema, set secrets and open it.
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.
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.
What Setup does for you.
Confirm the domain, add DNS, attach the hostname, deploy with its schema, set secrets and open it.
DNS resolves through Cloudflare and /health answers 200; a passing check marks the steps it proves.
Check the selected apps together: each app's DNS and health, its steps done and the overall percentage.
A suggested path for Setup. What you can do depends on your access in the app.
The guides then use that domain's real hostname for every app.
Copy each DNS value and command, deploy, then verify DNS and the host.
Check the selected apps in one go and see which hosts still need work.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
setup.appneurox.com
Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.