Sentinel Local 2.3.2
Protection inside WordPress. It must continue safely through network, licensing, or future cloud outages.
WordPress security · local first
SEDAJ Sentinel is a focused security layer designed to protect the site locally, respect the data it handles, and keep essential protection working even when external services are unavailable.
Purpose
Security software should reduce uncertainty—not create a new dependency. Sentinel’s local core lives inside the WordPress environment and remains responsible for essential protection. Licensing and future cloud services are separate extensions, never a remote switch for the local security layer.
The result is a deliberately restrained foundation: understandable operating states, minimal data sharing, safe failure behaviour, and no marketing blur between what works today and what is still being built.
Available today
✓Protection runs where it matters: inside the WordPress installation
✓The essential security layer remains available without a cloud connection
✓Sensitive form contents are not sent to apps.sedaj.com
✓Current local version: 2.3.2
View version and distribution status →Clear boundary
Protection inside WordPress. It must continue safely through network, licensing, or future cloud outages.
Future signed feeds and cloud signals. They are not a current feature or part of a paid plan.
Privacy
The licensing platform does not need form submissions, visitor cookies, WordPress users, or raw IP addresses. Future integrations are designed around pseudonymous installation identity, narrowly scoped permissions, short-lived tokens, and the minimum technical data required to deliver the service.
Read the security model →Licensing
A future license may govern access to downloads, updates, or optional cloud capabilities. A delayed verification or unavailable licensing service must never turn off Sentinel’s essential local protection.
That separation is part of the product architecture, not merely a promise on the pricing page.