Resources
Use these starting points to align finance, security, legal, and leadership around a common operating language for employee AI use and policy evidence.
Resources / Start here
AI hiring review starts with use-case inventory, jurisdiction scope, evidence ownership, and the distinction between Tallin-proved data and customer-attested artifacts.
Consumer chatbot review should connect external AI experiences to disclosure text, escalation paths, owner review, jurisdiction scope, and operational evidence.
Gateway privacy modes let a customer choose what Tallin stores while keeping the operational ledger useful for spend, attribution, and policy evidence.
Resources / All guides
A company AI spend ledger should reconcile provider bills, expense evidence, directory context, and usage telemetry without hiding how complete each signal is.
Coverage is the difference between what the company can prove, what it can infer, what it can enforce, and what remains outside the map.
A useful AI usage review gives leadership a forwardable snapshot of spend, adoption, risk, and blind spots without pretending the picture is complete.
AI hiring review starts with use-case inventory, jurisdiction scope, evidence ownership, and the distinction between Tallin-proved data and customer-attested artifacts.
Consumer chatbot review should connect external AI experiences to disclosure text, escalation paths, owner review, jurisdiction scope, and operational evidence.
Gateway privacy modes let a customer choose what Tallin stores while keeping the operational ledger useful for spend, attribution, and policy evidence.
Shadow AI spend usually appears first in card and expense data, long before it appears in an IT inventory.
AI gateway tools govern traffic for AI applications a company builds. Tallin governs employee use of AI tools the company already has.
Resources / Reference
Plain-language definitions of the coverage states and evidence terms Tallin uses, from observed and inferred to auto-proved and open gap. Use them in your own policy and reports.
Tallin documentation starts with setup paths for the AI Exposure Assessment, provider connections, expense CSV imports, coverage labels, and Exposure Snapshot exports. Product-specific setup instructions are available inside each customer workspace.
Customers can contact Tallin through their workspace or through the company contact route. Support requests should include the workspace domain, affected page, and whether the issue involves signup, provider connection, CSV import, Snapshot export, or billing.
Tell us about your AI actors, provider stack, and the runaway spend or policy gaps you need to close. We will help you decide whether Tallin is a fit for the first cohort.