Product · Discover
Find Shadow AI without collecting employee content.
See supported AI services reached from managed Chrome and Edge profiles. Compare the finding with approved access, assign an owner, and record the review decision.
From a browser signal to a useful next step
An AI visit starts a question.
- Observe
- Compare
- Review
Claude · claude.ai
A managed browser reported a visit to a supported AI hostname. A visit does not establish account type or reveal the prompt.
- Approved access
- A Claude Enterprise workspace is connected
- Still unknown
- Which Claude account was used during this visit
Ask the responsible team to confirm the business use and account. Keep the finding open until the evidence supports a decision.
Browser discovery is not inline blocking. Controls apply only to requests routed through Tallin.Sources and setup
Bring the right context to each finding.
A browser visit, SSO assignment, provider roster, and expense charge tell you different things. Tallin keeps their sources visible during review.
- Managed browsers
- Deploy the Tallin extension to managed Chrome and Edge profiles. It reports supported AI hostnames, timestamps, managed profile identity, and deployment health.
- Identity and provider
- Connect SSO and approved-provider rosters to compare access. A matching roster does not prove which account was active in the browser.
- Security sources
- Configured CASB, SSE, and network evidence can add managed identity, device, policy, and connection context.
- Expense and uploads
- Card, expense, and CSV evidence can surface paid AI tools missing from your software inventory.
The review
A signal to resolve, not a verdict on an employee.
- Observe
- Review the supported AI hostname, managed profile, timestamp, and source health.
- Compare
- Check approved-provider access and other connected evidence. Do not treat a browser visit as proof of the account used.
- Decide
- Mark the finding sanctioned, unsanctioned, dismissed, or needing review. Assign the follow-up and keep the disposition.
Browser privacy
The activity signal. Not the conversation.
The managed-browser extension reports supported hostnames and the profile context needed for discovery. Unrelated browsing stays on the endpoint.
- Not collected
- Prompts, responses, page content, searches, URL paths, query strings, and unrelated browsing history.
- Not established
- Which provider account was active, what was entered, or whether a conversation occurred.
- Coverage detail
- Recognition depends on the reviewed provider catalog and the sources you deploy.
Standalone service
Start with the visibility you need.
- Monthly
- $500 for up to 250 managed browsers.
- Annual
- $5,000 for up to 250 managed browsers.
- Trial
- 30 days. No credit card required.
- Expand later
- Keep your setup and finding history when you add other Tallin services or move to Core.
Discover questions
D01Does Discover collect prompts or responses?+
D02Does a browser observation identify the provider account?+
D03Which tools can Tallin recognize?+
D04Can we add other Tallin services later?+
Find the AI already in use.
Start with managed-browser discovery, compare approved access, and work through your first findings.