The platform
An annual plan for the ideas and decision record, access controls, audit, core services and the areas of the organisation using Bridgly.
Sized around the organisation and rollout, not a tally of every idea.Pricing
Clear enough to explain.
Flexible enough to fit the organisation.
Bridgly is not priced by seat alone. Pricing covers the platform, active contributors, the model services you choose and any enterprise deployment requirements.
We publish how pricing works, not untested list prices. Pilot, Organisation and Enterprise packages are scoped around the real work and agreed before rollout.
Three pricing parts
A clear model with the right detail underneath.
The people who contribute
Collaborator bands cover people who shape, rehearse and own work. Viewers, auditors and board members can read through free, unlimited Lens access.
Agents are capacity. They are not sold as seats.The AI work you choose
Use your own provider agreements, run local models, or use Bridgly-routed services. Higher-volume work is pooled and controlled, not presented as a confusing token bill.
The route can vary by team, workflow or sensitivity.Packages
Start small, then expand without starting again.
The package changes as more teams, systems and controls come into scope. The decision record and the learning built during a pilot carry forward.
Start with one useful problem
Pilot
A fixed, bounded engagement for one team or decision flow. It can include a historical backfill, a clear success measure and a practical route into wider use.
- Selected connectors for the pilot scopeA bounded scope keeps the first connected systems aligned to the pilot outcome.
- One improvement loop with measured outcomesDecision memory and evidence attachments support one measured learning loop.
- Briefing and handover packReceipts, ledger writes, and decision-record queries preserve the pilot story for handover.
- Light onboarding and success check-inThe Pilot team band supports a focused rollout with a success checkpoint.
Bring teams onto one shared record
Organisation
An annual platform plan with collaborator bands, SSO, shared reporting and agreed usage. Customer-managed model agreements are the usual starting point.
- Team and workflow viewsCollaborator bands and scoped operating areas extend the pilot into multi-team visibility.
- Usage attribution and budget visibilityBridgly-routed compute attribution is available from Organisation.
- Decision and capability signalsDecision memory and evidence attachments connect decisions, proof, and team learning.
- Governed reporting cadenceEvidence-ready reports support internal sponsors and customer proof.
- SSO (standard)SAML/OIDC login is included from Organisation as a standard identity control.
- Access review readinessStandard identity controls and evidence reporting support recurring access review.
Fit Bridgly to a complex organisation
Enterprise
A tailored package for private or VNet deployment, federation, advanced identity, custom connectors, managed storage and a dedicated support cadence.
- SCIM auto-provisioningGovernance-grade identity provisioning for complex organisations.
- Advanced access reviewAdvanced access-review controls for deeper governance routines.
- Business-unit and line-of-business visibility controlsBusiness-unit and line-of-business boundaries stay visible and enforceable.
- Custom connectors and implementation supportEnterprise implementation can cover private posture, federation, and custom source integration.
- Security and compliance review supportDisclosure controls, policy enforcement, and private-cloud posture support enterprise review.
- Provider-routing visibilityCustomer-managed, local, and Bridgly-routed compute lanes stay attributable.
- Dedicated rollout and success cadenceGovernance policy and private posture requirements shape a dedicated rollout plan.
Model choice
Bring your own, use ours, or run local.
Different workloads can take different routes. Bridgly keeps the usage, budget and outcome visible without forcing the whole organisation through one model provider.
Your provider agreements
Use your existing OpenAI, Anthropic, Bedrock or other approved provider agreements. Bridgly keeps usage and outcomes attributable while the provider bills you directly.
Bridgly-routed services
Use a pooled convenience route when you want one managed path. This can cover voice and higher-volume model services, with budgets and usage controls agreed up front.
Local or customer-hosted models
Run suitable workloads on infrastructure you control. Bridgly does not add a compute charge for your local model runtime.
The annual platform plan includes the core services Bridgly needs to operate, including fair-use internal AI. Higher-volume voice, model and workflow services are handled through the agreed usage route.
Included in the platform plan
Your decision record is part of the product.
Decisions, evidence links, receipts, ledger records and ordinary queries of the decision record are part of the platform plan. Managed storage for large retained source material may be priced separately.
Common questions
The detail buyers need before a conversation.
Why not publish one price per seat?
Because the real cost depends on rollout scope, active contributors, connectors, model routing, usage and enterprise controls. A single seat price would look simple but hide the parts that matter.
Do agents need seats?
No. Agents are capacity, not people. Commercial limits follow the organisation, contributors and any managed model usage.
Do we pay to read our own decision record?
No. Recording decisions, attaching evidence, writing receipts and reading the decision record are included in the platform plan.
Can we use our own OpenAI or Anthropic agreement?
Yes. Customer-managed provider routing is a first-class option. Bridgly can still attribute usage, spend and outcomes without reselling that provider capacity.
Can Bridgly run behind our network boundary?
Private cloud, VNet integration, customer-owned data platforms, federation and custom network controls are Enterprise options. The exact design depends on your identity, data and egress requirements.
Where are the exact numbers?
Pilot, Organisation and Enterprise packages are scoped with the buyer while the commercial bands are validated. The structure is public, but untested list prices are not.
Discuss your requirements
Bring one real use case.
We will explain what drives the price.
We can map the rollout, contributor groups, provider routes, deployment needs and the evidence you want the pilot to produce.