AI-native compliance that keeps up with your growth.
Always audit-ready, with every answer backed by your real data and evidence.
Early access is by email for now. It opens your mail app.
Logical access to systems and data is restricted
- Counts for 61 h moreSign-in policy exportEvidence · version 3 · from Okta
- PassingAdmin accounts require multi-factor sign-inCheck · Google Workspace
- Failing until fixedStorage buckets block public accessCheck · AWS
Illustration. Sample values, not customer data.
SOC 2, laid out so you can see what is left.
Clew starts from the SOC 2 requirements and the controls that answer them. Every requirement is a square, so you can see which ones have evidence and which do not.
- 8 Evidenced
- 2 Evidence expired
- 14 Mapped · no evidence
- 9 Not mapped
Illustration. Sample values, not customer data.
Evidence keeps its history.
See what was collected, when it was collected, and when it stops counting. A new version never erases the old one, so an auditor can ask about last quarter and you can answer.
Sign-in policy export
- Version 3Collected today. Current.
- Version 2Collected 4 days ago. Replaced by version 3.
- Version 1Collected 11 days ago. Kept.
Illustration. Sample values, not customer data.
Connect your systems. Clew checks them for you.
Clew reads AWS, Okta and Google Workspace, runs its checks, and files what it finds as evidence. No screenshots to chase.
AWS
Read-only checks of your AWS accounts.
Failing until fixedStorage buckets block public accessOkta
Users, groups, apps, admin roles and sign-in policies from your Okta org.
PassingAdmin roles are limited to named peopleGoogle Workspace
People, admin roles and 2-Step Verification settings from your Google Workspace.
PassingAdmin accounts require multi-factor sign-in
Illustration. Check names and results are samples. Provider names are text only.
A failing check comes with a guide to fix it.
Each one says what is wrong and how to put it right. When the check passes again, the evidence shows it.
Block public access on storage buckets
- Control
- CC6.1 · Logical access to systems and data is restricted
- Found by
- AWS check
- Owner
- Assigned to you
Guide
- Open the storage settings for the bucket in your AWS console.
- Turn on the setting that blocks public access.
- Run the check again to record the new evidence.
Illustration. The task and its steps are a sample, not a real fix guide.
Coming: ask AI in plain words and get the rows from your own data.
Clew is being built to look things up in your risks, tasks and vendors and show you the rows it found. If it has nothing to show, it says so. It is not switched on for customers yet.
Every answer would open by saying which lookup ran. The rows would come straight from your workspace.
Illustration. This field is a picture and does not run a search.
Clew is AI-native. Here is where it stands.
Clew is being built AI-native. Some parts exist and are in early access. None is switched on for customers yet.
Here is where each part stands, so you can tell them apart.
In early accessBuilt, not switched on for customers yet
- Ask in plain wordsQuestions over your risks, tasks and vendors return the matching rows. Switched off until it passes our quality checks.
- Connect your AI assistantOver MCP, your assistant can read your posture, frameworks, requirements, controls with check status, and tasks. Read-only. In testing, not open to customers.
Where Clew is headedIn development, not available yet
- Notice a broken rule as it happensWatch your connected systems and flag a violation when it appears.
- Help resolve itHelp your team put things right. How far this goes is still being decided.
Neither list is switched on for customers yet. The second is our direction, not a feature. No dates are promised.
Illustration of what exists and what is planned. No sample customer data.