Checkout
Compact sealThe seal reads “Protected by AXIS Sentinel” in its verified state, and the state itself in words in the other two.
SENTINEL PRESENCEOperating layer
SENTINEL, VISIBLE. NEVER MORE THAN IT CAN PROVE.
Presence is the guardian mark and status panel a protected page can show. It reflects what the page can honestly know about its own connection to Sentinel, and it never narrates a certainty the evidence does not support.

The mark
Corner, footer, compact and full, on a light page and a dark page. Then the verify page as this site stands, and the one line that installs the mark. A picture of the badge does not mean the page is reporting. The live mark appears only after Sentinel accepts a batch from that page, and it says it is not reporting, or it is removed, when Sentinel cannot.
Corner
A page wearing the mark.
The mark is the only Sentinel on this page.
Corner
A page wearing the mark.
The mark is the only Sentinel on this page.
Footer
A page wearing the mark.
The mark is the only Sentinel on this page.
Footer
A page wearing the mark.
The mark is the only Sentinel on this page.
Compact
A page wearing the mark.
The mark is the only Sentinel on this page.
Compact
A page wearing the mark.
The mark is the only Sentinel on this page.
Full
A page wearing the mark.
The mark is the only Sentinel on this page.
Full
A page wearing the mark.
The mark is the only Sentinel on this page.
AXIS SENTINEL
PROTECTION STATUS
axis-sentinel.com
Preview of the public page while this site has no accepted batch. Not a live verification, and not a certification.
Open the live status pageOne tag. The mark still waits for an accepted batch.
<script src="https://axis-sentinel.com/agent/v1/sentinel.js" data-sentinel-key="pk_YOUR_DEPLOYMENT_KEY" data-sentinel-seal="on" data-sentinel-banner="on" data-sentinel-banner-style="badge" data-sentinel-banner-placement="bottom-right" data-sentinel-banner-theme="dark" data-sentinel-banner-size="compact" defer></script>Recover returns to Observe
Presence is not a stage. It shows a visitor the loop's current state, as far as the page can know it.
The mark
The Presence is an instrument: a perimeter, the AXIS chevron, a core that carries the state and an aperture that wakes. The compact mark and its panel ship in Sentinel's own Presence package. This is that mark made into an object, with a graduated bezel and an iris, drawn large enough that a state can be read at a glance.



Quiet
Dark gauge, closed aperture
Watching
A third lit, aperture parted
Notice
Past half, aperture open
Warning
Amber arc and core
In place
Presence is the warning surface a customer's own people see. The Protection Banner is its quiet, verifiable line of protection on a company's own pages. Here it is in five places, in five of its presentations, on a fictional house called Northfield. The banner and its reporting are being built and are not live yet.
The seal reads “Protected by AXIS Sentinel” in its verified state, and the state itself in words in the other two.
The panel lists the site's monitoring, deployment and connection state, when it was last verified, and says it is not a certification.
A quiet line of protection: “Protected by AXIS Sentinel. Always on guard. Always watching.” with the monitoring state and when it was last verified.
“Axis Sentinel. Monitoring status cannot currently be verified.” with REPORTING INTERRUPTED, and the last contact. It never wears verified wording in this state.
The block states only the live status of the site's own Sentinel deployment. It says in the panel that it is not a certification.
What it asserts
A banner that claimed more than it could show would be worth nothing. This is what the Protection Banner may say, what it may not, and how a visitor checks it. An illustrative demonstration: the banner is being built and is not live yet.

An illustrative demonstration of what the Protection Banner can and cannot assert. Three plates in a stack: the record at the bottom, which is Sentinel's own status of a registered deployment; the connection in the middle, which is the batches the page sends; and the customer's page at the top, with the banner set into it as a sealed bar. What the banner may say is a column of light that rises from the record to the banner: the live status of the site's own Sentinel deployment. In the second state, dashed empty frames appear beside the stack for what it cannot say (a certification, a rating of the whole site, who is looking at a page), and no light reaches them. In the third state a small tablet, the public verification page, lights from the record, because a banner is drawn by the page it sits on and is not itself the proof. The Protection Banner is being built and is not live yet.
What it can say. The live status of this site's own Sentinel deployment: registered, reporting, and when it was last verified. The light rises from Sentinel's record to the banner, and only that light.
What the guardian may say
Presence reflects decisions made at the edge; it does not make them. Each state carries the strongest wording it may use, and no stronger. Choose a state, and a voice.
Connection state
Voice
The state a page can establish about its own connection, and nothing stronger.
Illustrative demonstration
Observing
MotionA controlled sweep scans the perimeter.
Every recent batch was accepted.
AXIS SENTINEL
Observing
Batches keep being accepted, so telemetry is flowing.
Protection is enforced at the edge. This panel reports status only.
What this page knows
Batches keep being accepted.
What Watchtower knows
The deployment is visible on its heartbeat rhythm, evaluated every minute.
The server's view is not sent back to the page. A page can describe its own connection and nothing more.
Reading this page, nowNot a demonstration
Reading the pageLooking for a Presence on this page.
A page's connection, over time
The Presence on Sentinel's own pages follows seven moments: no key, an agent that starts, a first accepted batch, batches that continue, one that is throttled, one that is lost, and reporting that resumes.
Illustrative demonstration
Not registeredNormalVerifiedObservingObserving, unchangedDegradedObserving
Step 7 of 7
Reporting resumes
The next accepted batch returns the Presence to Observing. Nothing in between was claimed.
A build with no registered key mounts nothing: no agent and no mark. There is no fallback identity and no demonstration mode, so a page never shows a guardian connected to nothing.
With a registered key the agent starts and the Presence mounts in its Normal state: the agent is running and Sentinel has not answered yet.
Sentinel accepts a batch from the page, so the deployment is registered and its origin is permitted. The Presence says Verified.
Further batches keep being accepted, so telemetry is flowing. The Presence says Observing, and the sweep scans.
Sentinel declines a batch under its own ingestion budget. The page still reached Sentinel, so saying it cannot would be false. The state stays exactly as it was.
A batch is refused or never arrives. The page reports the consequence and not the cause: the mark stops moving and says not reporting. Protection at the edge is unaffected.
The next accepted batch returns the Presence to Observing. Nothing in between was claimed.
Simulated states, written to show how the system behaves. Nothing here reads or changes a live system.

Signal path
Signals in
Outputs
Ten questions
The questions every Sentinel system must answer, in the same order on every system page.
Presence is the visible face of Sentinel on a protected page: a guardian mark with a status panel that shows what the page can honestly know about its own connection to Sentinel.
Whether this page's agent is running, and whether Sentinel's gateway is accepting what it sends.
The outcome of each of the page's own telemetry batches: accepted, throttled, refused or unreachable.
Which of a small set of states it may show. On the public site that is normal, verified, observing or degraded.
Show that monitoring is on once Sentinel has accepted a batch, say not reporting when it has lost its connection, and open a panel that explains the state.
It enforces nothing. Removing it from a page changes what a visitor sees and nothing about what is enforced.
Nothing directly. The agent beneath it reports to First Light; Presence only reflects the outcomes.
Presence reflects whether First Light accepts the page's telemetry. Watchtower's server-side view of the deployment is deliberately not sent back to the page, and Shield's words reach a visitor through Presence only under the rules of what Sentinel may say.
When the page cannot reach Sentinel the mark stops moving and says not reporting; protection at the edge is unaffected. A misconfigured canary removes itself rather than leave a guardian claiming protection.
The visitor seal's rule is a pure, tested function: it appears only after an accepted batch, disappears when Sentinel refuses the page, and admits not reporting after two lost batches in a row.
Relations
Failure and health
In operation
ObservingOn failure or loss of visibility
When it fails or loses visibility
DegradedHow its own health is verified
Presence states
The Sentinel system family