Sentinel Documentation

Sentinel Pro 4.3 Beta Website Content Pack

This document provides website-ready copy and publishing structure for the

Website Content Pack 4.3 Beta Date: 2026-04-01

Sentinel Pro 4.3 Beta Website Content Pack

Copyright (c) Savant Cyprus 2026

>

Bridge & App microsite link: [Savant Sentinel Pro](https://savantcyprus.com/sentinel-pro.html)

Purpose

This document provides website-ready copy and publishing structure for the Sentinel Pro 4.3 beta update cycle.

Use this as the editorial baseline for:

  • public product page updates
  • gated download page updates
  • beta tester onboarding pages
  • release announcement sections

1. Messaging Framework

1.1 Core Positioning

Sentinel Pro is a homeowner-governed monitoring and control-assurance platform for Savant homes, delivered through:

  • a secure local bridge runtime on the host
  • an Apple-native app experience across iPhone, iPad, and Apple TV

1.2 4.3 Beta Key Message

4.3 beta advances Sentinel from feature-rich monitoring into an operationally hardened platform with stronger governance, diagnostics, and deployment discipline.

1.3 Tone Direction

  • confident, technical, homeowner-safe
  • no fear-based language
  • emphasize controlled power and accountability
  • clearly separate "beta" from "production hardening path"

2. Homepage Hero Copy

2.1 Primary Hero Headline (Option A)

Sentinel Pro 4.3 Beta Precision Monitoring and Control Governance for Savant Homes

2.2 Primary Hero Headline (Option B)

Savant Home Visibility, Secured by Design Sentinel Pro 4.3 Beta

2.3 Hero Subcopy

Monitor critical systems, verify host health, and manage trusted access with a local-first bridge and Apple-native command surfaces built for high-end Savant estates.

2.4 Hero CTAs

  • Primary CTA: Request Beta Access
  • Secondary CTA: Download Technical Whitepaper
  • Tertiary CTA: View Bridge Deployment Guide

3. Feature Section Copy

3.1 Section Heading

What Is New in 4.3 Beta

3.2 Feature Cards

Card 1: Homeowner Access Authority

Title: Owner-Controlled Integrator Access Body: Home admins can temporarily disable or permanently revoke integrator access, with immediate session enforcement and auditable records.

Card 2: High-State Telemetry at Scale

Title: Large-Home Telemetry Optimization Body: Sentinel is tuned for large state inventories with optimized harvesting, progressive rendering, and service-aware mapping.

Card 3: Bridge Runtime Identity

Title: Operationally Traceable Runtime Body: Bridge health and config payloads now expose process identity and runtime metadata for safer support and update workflows.

Card 4: Secure User Onboarding

Title: Temporary Password Onboarding Body: Admins can generate temporary credentials for homeowner users and enforce first-login password rotation with controlled delivery options.

Card 5: Guard-Railed Host Tools

Title: Controlled Diagnostics and Actions Body: Terminal, reboot, and doorbell tooling remain role-gated, confirmed, and fully audited for safe operational use.

Card 6: SmartHost Path Standardization

Title: SmartHosts Runtime Root Updated Body: 4.3 beta standardizes SmartHosts bridge deployment under /home/RPM/Sentinel for cleaner path consistency.

4. Architecture Section Copy

4.1 Heading

Architecture Built for Trust and Speed

4.2 Body

Sentinel separates telemetry and control concerns through a host-local bridge, role-aware API contracts, and responsive Apple-native clients. The result is a local-first operations model that scales to complex homes without sacrificing owner governance.

4.3 Diagram Labels (for design team)

  1. Savant Host Sources (StateCenter + host runtime)
  2. Sentinel Bridge v4.3b1-pro (API, policy, audit, tools)
  3. Secure Transport (LAN/VPN, HTTPS recommended)
  4. Sentinel Pro Clients (iPhone, iPad, Apple TV)
  5. Governance Layer (roles, acknowledgments, homeowner controls)

5. Security and Privacy Section Copy

5.1 Heading

Security and Privacy Designed Around the Homeowner

5.2 Body

Sentinel combines modern credential hashing, role and acknowledgment gates, TLS identity signaling, and 90-day structured audit retention. Access is explicit, revocable, and observable.

5.3 Bullet Highlights

  • PBKDF2-HMAC-SHA256 password hashing
  • Role and monitoring acknowledgment workflows
  • Homeowner temporary disable and permanent revoke controls
  • Audit coverage across authentication, admin changes, and host tools
  • Local-first data residency model

6. Beta Program Section Copy

6.1 Heading

4.3 Beta Program for Integrators and Advanced Homeowners

6.2 Body

The 4.3 beta validates large-home performance, governance workflows, and bridge deployment consistency across ProHosts and SmartHosts. Participants receive the full deployment runbook and technical whitepaper set.

6.3 CTA

  • Join the Beta Validation Program

7. Download Hub Structure

Recommended downloadable asset list:

  1. Master Engineering Whitepaper (v4.3 Beta)
  2. Bridge Protocol and API Specification
  3. Security, Cryptography, and Privacy Whitepaper
  4. Deployment and Operations Runbook
  5. Release Notes and Beta Validation Checklist

8. FAQ Content (Website-Ready)

Q: Does Sentinel require cloud connectivity to monitor local Savant systems? A: No. Sentinel's bridge telemetry path is local-first over LAN or VPN.

Q: Can homeowners stop integrator access without deleting the system? A: Yes. Home admins can temporarily disable or permanently revoke integrator access from Sentinel governance controls.

Q: Which hosts are supported in 4.3 beta? A: Both ProHosts and SmartHosts are supported with host-family-specific scripts and Blueprint profiles.

Q: How do I confirm the bridge is updated? A: Use the /health endpoint and verify version 4.3b1-pro with status ok.

Q: Can Sentinel be used on Apple TV? A: Yes. Apple TV is supported for persistent household wallboard monitoring.

Suggested page footer:

Sentinel Pro is provided for managed Savant deployments. Features and safeguards may vary by role, host family, and Blueprint policy configuration.

  1. Update hero and feature copy.
  2. Publish whitepaper/download center files.
  3. Update beta CTA forms and success pages.
  4. Add release notes section to changelog/news page.
  5. Verify all links point to v4.3 beta documents only.

11. QA Checklist for Website Team

  1. All references use 4.3 beta and v4.3b1-pro consistently.
  2. No stale v4.1 or v4.2 links in primary CTA paths.
  3. Download buttons map to this folder's files.
  4. Mobile and tablet rendering preserve headline legibility.
  5. Legal footer and copyright notice are present.