Know who is asking
Identity is established before Bridgly decides which work, evidence or summary a person can see.
Trust and security
Security follows the work from the first idea.
Bridgly keeps identity, access, evidence and audit connected from idea to outcome. Each person sees the work allowed by their role. Leaders get approved summaries, not open access to every project.
Identity and access
Enterprise sign-in and access that fits the organisation.
Bridgly supports enterprise SSO, directory-backed roles and group mapping. Identity is established before the platform decides which project, evidence or summary a person can see.
Keep people in their lane
Tenant, role, team, business-unit and project scope shape every authorised view.
Protect the data before retrieval
Access rules are applied before context reaches an answer, agent or workflow.
Keep a clear record
Decisions, evidence, ownership, access checks and outcomes remain reviewable.
WorkOS is supported as an enterprise identity and SSO route.
Data, models and customer control
Use the model and data route that fits the organisation.
Customers can use their own provider agreements, gateways or local models. Bridgly keeps the same identity, access, policy and audit controls across those routes.
Bring your existing model agreements
Use approved providers and customer-managed credentials where the deployment supports them.
Keep suitable workloads closer
Local and self-hosted models can sit behind the same Bridgly identity, scope, policy and audit contract.
Keep control of organisational knowledge
Ideas, evidence and decision history remain customer content. Data and model routes can be configured around the customer's control needs.
Enterprise reference architecture
A controlled data and application foundation.
Bridgly connects enterprise identity, the application, approved work tools and a customer-scoped Databricks data plane. Identity, row-level access, evidence and audit controls apply across each route. Model, connector and deployment choices depend on the customer's agreed configuration.
Conceptual reference architectureA protected path from the team to the customer data plane
Customer security perimeter
01People and work surfaces
02Bridgly application
Ideas and decision partnerAI assistance built into the flow
Ideas boardDecision rehearsalGoals and milestonesFluid analyticsGoverned skills
03Control and integration
Open connector routesCatalogue connectorsREST APIsSigned webhooksMCPOpenTelemetry
04Databricks data and AI foundation
05Customer separation
Private deployment
Designed for private cloud and VNet deployment.
Bridgly is designed to run within the customer security perimeter. Network topology, egress rules and production packaging are agreed for each enterprise rollout.
Private ingress and service routes
Use private endpoints and approved access paths that fit the customer cloud and network design.
Only approved outbound destinations
Restrict model, connector and service traffic to the routes agreed for the deployment.
Identity, secrets and providers stay scoped
Customer identity, secret handling, provider routes and internal-system access remain deployment specific.
- Identity and scopeWho is asking and which lane applies
- Authorised evidenceOnly permitted context enters the route
- Decision recordRationale, owner and review stay connected
- Outcome and auditThe result remains traceable to its evidence
Governance and evidence
Apply controls before information is used.
Bridgly keeps source permissions, classification, ownership, evidence and decision history connected to the work. Access is checked before restricted context is returned to an answer, agent or workflow.
Access checked before context is returnedRestricted information is not treated as visible and hidden after generation.
Lineage from summary to evidenceAuthorised users can follow important claims back to the work that supports them.
One decision and audit recordRationale, owner, policy, review and outcome remain connected.
Accessible use
Designed to support WCAG 2.2 AA.
Bridgly is being built for keyboard use, visible focus, readable contrast, text resizing, reflow, clear labels, useful target sizes, screen-reader semantics and reduced motion.
Assurance
Clear evidence for security and procurement review.
Security and procurement teams can review the current controls, deployment assumptions, access model and evidence path. Formal certifications and customer-specific production proof are stated only when they exist.
What is supported now
Identity, scope, row-level controls, governed retrieval, evidence and audit.
What is confirmed for the customer
Network topology, provider routes, connector access, operating ownership and production controls.
What needs independent proof
Certifications and formal accessibility conformance are published only when the evidence is complete.
Start with your real boundary
Show us how identity, data and networks work in your organisation.
We will explain how Bridgly fits the people, systems and controls involved.