auths.appneural.com
AUTHS
Sign-up, sign-in, email verification, password reset and sessions for every APPNEURAL app, with each domain signing people in at auth.<domain>.
Purpose and boundaries
Sign-in by password, emailed one-time code, Google or GitHub, plus email verification, password reset and sessions for any app, with every authentication event in one private dashboard. Each domain signs people in on its own address, auth.<domain>, and auths.appneural.com lists every domain with its setup progress. A domain gets a public site key, a secret key and a ready-made Next.js integration, so apps never store passwords or build login screens. The public inventory lists connected domains only, without names, keys or counts.
Machine credentials stay in Secrets; authorization rules inside an app stay with that app.
- Priority
- P2
- Portfolio
- Identity & Security
- Capability
- Identity & Security
- Technical owner
- Not configured
- Runtime
- Cloudflare Workers / OpenNext
- Last verified
- 2026-11-08T06:18:33.573Z
Every number says what it counts
Governance evidence required
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
auth schema v1
Where it runs
auths.appneural.com
- Worker
- auth-catalog
- Health
- HEALTHY
- Last deployment
- 2026-11-03T00:00:00.000Z
Confirmed infrastructure only
Technical context
Documentation
Registered relationships
Checks and verification
Review posture
GitHub · Cloudflare · DNS · catalog APIs
Drift findings
Trust record
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Human-reviewed drafts
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.