No surveillance business model
A utility should finish your task and get out of the way—not harvest behavioral data or upload confidential work to ad brokers.
DOC 03 · Revised November 2026 · Design Commitments
Everyday web utilities have largely turned into cookie walls, upload traps, and bait-and-switch paywalls. OTHRYS follows five simple rules instead.
A utility should finish your task and get out of the way—not harvest behavioral data or upload confidential work to ad brokers.
No fake countdowns, no bait-and-switch download buttons, and no paywall appearing after you have already filled out a document.
Whenever browser APIs can do the job locally, computation belongs on the user's own hardware rather than a remote server.
Internal AI maintenance agents are constrained by fixed Aegis rules, and every code change requires human pull-request review before deployment.
Utilities output standard, portable formats (RFC 4122, RFC 9562, RFC 7519, POSIX cron, compose.yaml) with zero vendor lock-in.