Client Portal
Every engagement gets its own tenant — its own dashboards, its own log index, its own alert channels. Access is granted per person and scoped to your environment. Nobody sees across tenants, including us, without a named reason.
Sign in
Cloudflare Access handles the login and hands you off to your identity provider.
No account yet? Your engagement lead sets those up. Ask for access or call (815) 263-6964.
What's in your tenant
Telemetry dashboards
Grafana views over your own Prometheus and OpenSearch tenants — interface throughput, container resources, flow analytics.
Log search
Graylog across your retained wire and system logs, scoped to your tenant, with PII and PHI already stripped at ingest.
Security alerts
Suricata and Wazuh findings, config drift notices, and triage summaries written by models running on your own hardware.
Engagement documents
Diagrams, runbooks, change records, and deployment reports for the work we are doing for you.
Surfaces come online as each part of your stack is deployed. Sign in to see where yours stands.
How access works
- Your identity provider, not our password database
- Cloudflare Access sits in front of the portal and authenticates against whatever you already use — Entra ID, Okta, Google Workspace, or a one-time PIN by email. We never store a password for you.
- Named people only
- No shared logins. Access is granted per person, and revoking someone takes effect on their next request — not whenever a session happens to expire.
- Verified on every request
- The portal checks the signed assertion Access issues against Cloudflare's public keys before it renders anything. A forged header gets you a 403, not a dashboard.
- Already redacted when it reaches you
- Anything visible in the portal has passed the sanitisation step described in the security whitepaper.