Website sign-up pages
Give each website its own update sign-up page.
A clear way to follow updates
Build website update lists with double opt-in and one-click unsubscribe.
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.
What Subscriptions does for you.
Give each website its own update sign-up page.
Confirm subscriptions through double opt-in.
Provide one-click unsubscribe for subscribers.
A suggested path for Subscriptions. What you can do depends on your access in the app.
Start with the website’s update list.
Check the sign-up page and double opt-in journey.
Review the update and its unsubscribe route.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
subscriptions.appneural.com
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.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.