Built to be understandable, controllable, and easier to trust.
Greywake uses a local-first product posture, explicit external-service boundaries, versioned releases, and public policies designed to reduce unnecessary collection and ambiguity.
Focused technology and tools for real operating environments.
Local by default, explicit when external services are used.
Most Greywake applications run entirely in the browser and keep working data in browser storage. Tools that call an external service identify that behavior and restrict requests to the service required for the feature.
Policies and operational transparency.
These pages explain how the public site handles information, what users must validate, and how to report a potential issue.
Measure navigation and reliability, not application content.
Public measurement should be limited to aggregate page use, application launches, guide views, form completion, 404 routes, and technical failure categories. Application inputs, prompts, financial assumptions, audio, imported files, IP-test results, and local backups are outside the measurement scope.
