subscriptions.appneural.com
SUBSCRIPTIONS
One update list per website: a sign-up page at subscribe.<domain>, double opt-in, updates and one-click unsubscribe.
Purpose and boundaries
APPNEURAL Subscriptions keeps one update list per connected website. Visitors sign up on subscription.<domain> (or the older subscribe.<domain>), through the footer newsletter form of every portfolio site (via site-enquiry), an HTML embed, a Next.js component or the JSON API; sign-ups are confirmed by double opt-in. Updates are written in the composer (Claude can draft them in the brand's voice), sent through Cloudflare Email Service from each domain's own address, and every email carries a one-click unsubscribe.
Message content and channel providers belong to Communication; received mail belongs to Mail.
- Priority
- P2
- Portfolio
- Communication & Engagement
- Capability
- Communication & Engagement
- Technical owner
- Not configured
- Runtime
- Cloudflare Workers / OpenNext
- Last verified
- 2026-11-08T06:19:42.976Z
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.
subscription schema v1
Where it runs
subscriptions.appneural.com
- Worker
- subscription-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.