Skip to app details
Back to app library
APPNEURAL APP FAMILYCommunity & Events

Subscriptions

A clear way to follow updates

Build website update lists with double opt-in and one-click unsubscribe.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
Website updates with clear choices
ListSign-up pageConfirmation
Product updatesupdate listsEXAMPLE
Learning updatessign-up pagesEXAMPLE
Company newsdouble opt-inEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Subscriptions does for you.

01

Website sign-up pages

Give each website its own update sign-up page.

02

Double opt-in

Confirm subscriptions through double opt-in.

03

Simple unsubscribe

Provide one-click unsubscribe for subscribers.

03 / GETTING STARTED

Start small. Build from there.

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

01

Choose the website

Start with the website’s update list.

02

Review sign-up and confirmation

Check the sign-up page and double opt-in journey.

03

Prepare the update

Review the update and its unsubscribe route.

YOUR NEXT MOVE

Make Subscriptions 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
P2VERIFIEDPUBLISHED
Overview

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.

Update lists for connected domains: sign-up pages at subscription.<domain>, double opt-in consent, updates written in each brand's voice, delivery from each domain's own address and one-click unsubscribe.

Message content and channel providers belong to Communication; received mail belongs to Mail.

Priority
P2
Portfolio
Community & Events
Capability
Community & Events
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:02:59
Semantic inventory

Every number says what it counts

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

Governance evidence required

6 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
ConfiguredGitHub 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

subscription schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

subscriptions.appneurox.com DEPLOYED

subscriptions.appneurox.com

Worker
subscription-catalog
Health
HEALTHY
Last deployment
2026-11-03T00:00:00.000Z
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

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