Swift native
Network Extension, local VPN/DNS, Family Controls and Managed Settings where approved, optional configuration profiles for stronger lockdown.
Product overview
SentryPact is a privacy-preserving, lockdown-first blocker for adults and families who want protection that stays on at the exact moment it is needed most. It combines DNS, app, and browser filtering with timer-locked Solo Pacts, optional co-signers, tamper detection, and minimal accountability reporting.
Wedge
The user can disable them when impulse is strongest. SentryPact starts from the opposite assumption: ask the user to make a clear pact up front, record the server-verified release time, and keep enforcement active until the pact is fulfilled or a documented release path completes.
Architecture direction
The cloud control plane owns accounts, subscriptions, devices, pact state, server-side time, partner relationships, approvals, tamper ingestion, reports, and signed configuration publishing. The enforcement layer stays native because the operating system is the only place real control lives.
Network Extension, local VPN/DNS, Family Controls and Managed Settings where approved, optional configuration profiles for stronger lockdown.
VpnService filtering, Device Admin friction where policy allows, accessibility services only when truly needed, no surveillance by default.
Windows Filtering Platform with locked DNS and hosts controls, tamper-resistant service registration, deterministic update behavior.
Chrome, Edge, Firefox, and Safari companions for cosmetic filtering, DoH detection, SafeSearch enforcement, and YouTube Restricted Mode.
Server-rendered dashboard, JSON APIs for native clients, signed configuration publishing, audit trail, and operator inspection.
SQLite for the local Rails scaffold today, PostgreSQL likely once the control plane stores real pact and device state.
First product target
The MVP focuses on the smallest believable loop: a person can install the app, choose categories, lock a Solo Pact, and stay locked through the release time even when their willpower changes.
Roadmap direction
Each step earns the next. We will not start a full native app until the control plane has contracts the native client can actually consume.