Workspace isolation
Dashboard and API paths are scoped to the active workspace and membership.
Security & trust
Built for approved business knowledge, not uncontrolled document sprawl.
Bridge is designed to help teams expose only approved, source-backed knowledge to AI tools. The product emphasizes workspace scoping, citation-first answers, scoped API keys, and clear limits around what is — and is not — certified today.
Current trust posture
Bridge is not marketed as HIPAA-ready, SOC 2-certified, enterprise SSO-ready, or SLA backed unless those controls are implemented and contracted separately. Use it for approved, non-sensitive business knowledge that is safe to connect to customer or internal AI tools.
Controls and practices
Hashed API keys
Bridge stores key hashes and shows raw API keys only once at creation.
Allowed origins
Browser and widget usage can be limited to approved website origins.
Source-backed answers
Answers are designed around retrieved evidence, citations, confidence, and safe refusal behavior.
Raw-source minimization
Parsed source text is minimized after indexing where configured; binary file upload is not part of the launch path.
Audit-friendly workflow
Releases, evals, feedback, and activity records support review before production use.
Recommended customer setup
- Use Bridge only with content you have reviewed and approved for AI use.
- Create separate knowledge bases for different audiences or risk levels.
- Publish releases before connecting production integrations.
- Use separate API keys for server, widget, and testing workflows.
- Review analytics and unanswered questions before expanding usage.
Need a stricter posture?
For regulated, sensitive, or enterprise deployments, treat Bridge as a configurable implementation project. Contractual controls such as DPA, SSO, SLA, data residency, and compliance certifications should be confirmed before use.
Review plans