Skip to app details
Back to app library
APPNEURAL APP FAMILYDeveloper Platform

Status

Is everything up? Know first, tell everyone

Watch your sites and APIs, open and close incidents, plan maintenance and show a public status page with a 90-day history.

01 / OVERVIEW

See where it fits in your day.

A monitor is an address with a method (GET, HEAD or POST), expected status, optional keyword present or absent, timeout, slow limit, interval of 1, 5 or 15 minutes, group and a public flag; up to 300 per domain, and unsafe addresses are refused. Checks run only from the scheduler every minute, at most 100 per run with the rest carried to the next minute; Check now queues a monitor for the next run. A host that cannot be checked from the Worker shows cannot check from here and never a false down: a connection error counts as down only for a monitor that has been reached before, a run in which all five or more of our own hosts fail counts nothing, and a real wrong answer always counts. Results are up, slow, down or cannot check, with response time, 90 days per day and uptime. An incident opens after a number of failed checks in a row and resolves after good ones (both in Settings); manual incidents carry updates; maintenance windows of up to 14 days silence alerts and stay out of uptime. Alerts are sent once per change of state by signed webhook, by email to chosen people and to confirmed subscribers. The public /status page shows monitor names only, groups, 90-day bars, incidents, maintenance, 30-day history, double opt-in email subscribe and a badge; it returns 404 until the owner turns it on. Add every APPNEURAL app of a domain imports them from the suite list as /health monitors. API /api/v1/monitors, /api/v1/incidents and a change feed with an API key or the workspace key; webhooks monitor.down, monitor.up and incident.opened, updated and resolved. Not built: Notifications as an alert channel, escalation, reminders while down, SMS, hourly graphs. Whether the scheduler can reach APPNEURAL's own hosts must be confirmed live after deploy.

A LOOK INSIDEExample layout · sample content
Monitors
MonitorExplore
StatusCompare
UptimeUnderstand
WebsiteAPICheckout
Illustrative chart · no live metrics
02 / CAPABILITIES

Built around the work you do.

What Status does for you.

01

Monitors

A URL with method, expected status, keyword, timeout and interval, run by a minute cron within the Workers limits.

02

Incidents

Opened after repeated failures, with manual incidents, updates and maintenance windows that silence alerts.

03

Status page

A public page with groups, a 90-day history, email subscribe and a badge; switchable off.

03 / GETTING STARTED

Start small. Build from there.

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

01

Add monitors

Add URLs or every app of a domain.

02

Set alerts

Choose who is told.

03

Share

Turn on the public page.

YOUR NEXT MOVE

Make Status 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

A monitor is an address with a method (GET, HEAD or POST), expected status, optional keyword present or absent, timeout, slow limit, interval of 1, 5 or 15 minutes, group and a public flag; up to 300 per domain, and unsafe addresses are refused. Checks run only from the scheduler every minute, at most 100 per run with the rest carried to the next minute; Check now queues a monitor for the next run. A host that cannot be checked from the Worker shows cannot check from here and never a false down: a connection error counts as down only for a monitor that has been reached before, a run in which all five or more of our own hosts fail counts nothing, and a real wrong answer always counts. Results are up, slow, down or cannot check, with response time, 90 days per day and uptime. An incident opens after a number of failed checks in a row and resolves after good ones (both in Settings); manual incidents carry updates; maintenance windows of up to 14 days silence alerts and stay out of uptime. Alerts are sent once per change of state by signed webhook, by email to chosen people and to confirmed subscribers. The public /status page shows monitor names only, groups, 90-day bars, incidents, maintenance, 30-day history, double opt-in email subscribe and a badge; it returns 404 until the owner turns it on. Add every APPNEURAL app of a domain imports them from the suite list as /health monitors. API /api/v1/monitors, /api/v1/incidents and a change feed with an API key or the workspace key; webhooks monitor.down, monitor.up and incident.opened, updated and resolved. Not built: Notifications as an alert channel, escalation, reminders while down, SMS, hourly graphs. Whether the scheduler can reach APPNEURAL's own hosts must be confirmed live after deploy.

Uptime monitoring for a connected domain's team: monitors on a schedule, results and uptime for 90 days, incidents opened and resolved by rule or by hand, planned maintenance, alerts by email and webhook, a public status page with subscribe and a badge, and an API.

Product analytics belongs to Analytics; error tracking and logs belong to the developer catalogs; the list of apps comes from the suite.

Priority
P2
Portfolio
Developer Platform
Capability
Developer Platform
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:16
Semantic inventory

Every number says what it counts

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

Governance evidence required

5 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
MissingGitHub 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

status schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

status.appneurox.com DEPLOYED

status.appneurox.com

Worker
status-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:16
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

APPNEURAL-Catalogs/status-catalogLOCAL · NOT CONFIGURED

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