Skip to main content
GRC LakeCloud, identities, AI agents, and activity logs above an evidence lake.

Onboarding

Start with a public repository or connect your own sources.

Start with a public repository

Paste a GitHub URL. No GitHub token needed.

Public evidence only. Private governance settings remain unknown.

What this checks

Reads public files and ownership signals at a recorded commit, plus current repository metadata. Branch protection, private alerts and organization policies remain unknown until you connect authenticated access. Public observations are not proof of compliance. Repository code is never executed. Connector management permission is required to add evidence.

Connect cloud, identity or an existing lake

Choose how evidence enters GRC Lake

Both paths end in the same normalized evidence → control evaluation → audit proof loop.

Connect sources directly

Use a read-only cloud, identity, SIEM, or source connector. GRC Lake probes access, syncs raw observations, normalizes them, and evaluates controls.

Choose a connector

Bring an existing lake

Read an existing Snowflake or ClickHouse lake, or normalize pre-landed raw JSONL with the CLI before evaluation.

Open lake path
No local paths or raw secrets are accepted in the console. Use the CLI for local raw files, then connect the resulting lake through a read-only connector.
Loading progress…