Integrations
Does it work with what you run?
RedactWall sits in front of the AI tools and the mail path your organization already uses, and scans the cloud drives you point it at. Each one below says what it covers and how far it has been proven.
Proof status
Every integration, and how far it is proven
RedactWall integrations, what each covers, and its proof status
8 integrations shown.
Anthropic
Claude models
Decides before data leavesProven liveOpenAI-compatible
Supported OpenAI-style traffic routed through RedactWall
Decides before data leavesBuilt to the vendor’s own connection and testedGoogle Gemini
Google’s Gemini models
Decides before data leavesBuilt to the vendor’s own connection and testedAmazon Bedrock
Models hosted in your AWS account
Decides before data leavesBuilt to the vendor’s own connection and testedEmail / SMTP
Your existing mail path
Decides before data leavesProven against a real clusterMicrosoft 365
OneDrive and SharePoint files
Finds and reportsBuilt to the vendor’s own connection and testedGoogle Drive
Files in your shared drives
Finds and reportsBuilt to the vendor’s own connection and testedAI coding assistants
Claude Code and other agent tooling
On the deviceRuns on the workstation
How far each one is proven is stated on its page, and the limits live in Disclosures.
Confirm the path for your pilot
RedactWall verifies the agreed browser and gateway scope before enrollment. The broader integration list does not expand that scope.
- Coverage is published for each integration
- Proof status is shown explicitly
- Pilot scope is agreed before onboarding