Enterprise

Built for a staffed security function.

Signal over noise.

Sentinel assumes a team that is accountable for outcomes, not a dashboard that is watched occasionally. Authority is graded, actions are recorded, and escalation to an executive is reserved for the cases that warrant one.

Graded operator authority

Viewer, analyst, commander and owner. Containment and resolution sit above routine acknowledgement, and the boundary is enforced server-side rather than by hiding a control.

Tenant and workspace isolation

Boundaries are enforced at the data path and validated on every release through Range, including against a forged workspace claim.

Retention you set

Index and raw evidence retention are configured separately, because the searchable record and the preserved original serve different obligations.

Safe Mode scope

Define the narrowest boundary Safe Mode should apply to, and which operations may be allowlisted during an incident, before you need it.

Continuity coordination

Sentinel signals COLOSSEUM to preserve critical state at detection, and records the confirmed restore position as part of the incident evidence.

Executive signal

Founder and executive notification is reserved for critical incidents, material unresolved risk, and decisions that genuinely require them.

Executive signal

An alert that always fires is not an alert.

Sentinel does not generate a continuous stream of executive notifications. Founder and executive signal is reserved for critical incidents, material unresolved risk, and decisions that require someone with authority to make them. Everything else is worked by the team in Command.

Deployment

Discuss a deployment.

Sentinel deployments are scoped against your estate, your tenancy model and your continuity obligations rather than sold from a price list.

Request a briefingRead the architecture