SafeRouter Home
A local router project that connects an owner interface with controlled network-policy changes and recovery after interrupted updates.
- My role
- Product requirements, network-policy workflow and AI-assisted engineering.
The problem
Home network controls need to explain what changed, preserve owner access and recover when an update is interrupted.
Constraints
- Keep core operation local
- Apply configuration changes as controlled transactions
- Distinguish service health from verified network protection
Current stage
Engineering alpha
Engineering baseline
SafeRouter combines a local owner interface with a router stack for controlled policy changes. The implementation includes transaction guards, persistent records of interrupted changes and boot recovery hooks.
First-hand accountChanging a network safely
A requested change passes through validation, application and confirmation. Recovery is part of that process, so an interrupted configuration update has a defined path back. Core operation does not depend on a cloud service.
First-hand accountAlpha boundaries
The project still needs work on owner-access recovery, device identity and accurate status reporting. Service health alone cannot establish that a household is protected. Filtering, routing and recovery need verification on the actual hardware and traffic path before a broader pilot.
First-hand accountView the technical architecture
Conceptual workflow
- 01Owner request
- 02Policy validation
- 03Apply and confirm
- 04Recovery if interrupted
Decisions
- Keep configuration changes reviewable
- Record interrupted transactions for recovery
- Expose the limits of each reported status
Evidence
- OpenWrt router stack and owner interfaceFirst-hand account
- Policy transaction and recovery contractsFirst-hand account
- Browser and network-contract test suitesFirst-hand account
Safety boundary
- Engineering alpha, not a certified security product
- Device identity and owner-access recovery remain areas for further work
- Installed packages do not prove filtering or VPN enforcement; hardware and traffic checks are required
Working vocabulary
OpenWrt / Linux / nftables / UCI / Local web UI / Transaction recovery
The basis for this case.
Record reviewed: . This describes the published account, not a new check of the project's runtime.
My role, implementation details and unlinked outcomes are first-hand statements. Public sources support only the claims identified alongside them. A project status or screenshot does not independently verify every result.