HTTP request counts
Requests handled by the company website's Cloud Run service, grouped into broad UTC time buckets. A request is not a unique person or a page view.
ENGINEERING NOTE / CORPORATE WEBSITE
We use a restrained approach to understanding website reliability and broad usage patterns. Our initial analytics are derived from aggregate request counts that Google Cloud Run already exposes to operators. We do not install a visitor analytics tag or build profiles.
Explore our approachRequests handled by the company website's Cloud Run service, grouped into broad UTC time buckets. A request is not a unique person or a page view.
Broad 2xx, 3xx, 4xx, and 5xx response-class totals help identify operational problems. Requests made by automated tools may be included.
Read-only reporting is restricted to the dedicated Pythagorean Technologies Cloud Run service, not Academra, Acceredra, or unrelated projects.
The corporate website host and Google Cloud may still process operational request data as part of standard service delivery. The wider logging configuration and retention practices require separate operator and legal review.
A restricted Windows-only workflow can retrieve aggregate Cloud Monitoring metrics and render an offline local report. No additional collection scripts are loaded on public pages; reports stay outside the deployed website container. If Cloud Monitoring permissions or metric data are unavailable, the report says so instead of inventing a trend.
Publication boundary: The existing privacy notice and terms remain legal-review drafts. The contact form and search-indexing gates remain disabled until independently approved.
Review the draft privacy noticeExplore our broader commitments to measured claims, governance, and responsible engineering.
Trust & governance