Bridge
Bridge vs GoodData

GoodData embeds analytics into your product. Bridge handles the ask that doesn't fit a dashboard.

Custom fields, dashboards, exports. Handled in chat by your CSM, on your API. No platform to deploy.

Start free guided pilotSee the comparison

Free for 14 days on one of your customers. No card.

At a glance
GoodDataBridge
Where it lives
Embedded in your product UI
On your API, delivered in chat
How it ships
A platform deployment with a semantic model
Installed on your API in minutes
Who builds the view
Your data and product teams, in advance
Your CSM, in chat
Custom one-off ask
A model and dashboard to build and ship
Handled in chat
Custom fields
Defined in the semantic model first
Calculated live on every record
Time to a new ask
A modeling and deployment cycle
Minutes
6 of 12 differences shownSee all

Why choose Bridge over GoodData.

GoodData embeds a governed analytics platform into your product, so every custom ask runs through your data team. Bridge sits on your API and handles them in chat.

01Workflow

Handled in chat, not modeled and deployed.

GoodData embeds a governed analytics platform into your product, so a new view is a modeling and deployment cycle. Bridge sits on your API. The CSM types the ask in chat, Bridge builds the view, the link goes back in the same conversation. No platform to deploy.

See the full comparison
bridge_chat
live
Show every load 24h+ late, by carrier and lane.
calling /shipments · grouping by carrier · building view
late-loads.bridge.link/acme
shared
Sent back in the same conversation. No ticket opened.
02Custom dashboards

Built in chat, not modeled in advance.

GoodData ships the governed dashboards your data team can model ahead of time, each one embedded and themed. Bridge builds the one your customer asked for once, in chat against your API, scoped to that customer and shared as a white-labeled link they open themselves.

Start a free pilot
late_loads_view
shared
loads late
42
carriers
7
avg delay
31h
late by lane
03Custom fields

Calculated live, not modeled first.

Bridge adds calculated fields across every record without a change to the semantic model behind your dashboards. No engineering ticket, no deployment scheduled. The field is live the moment the formula resolves.

Start a free pilot
contacts
calculated
ContactActivity 90dchampion_strength
Acme Corp142 events92High
Globex88 events64Med
Initech31 events27Low
calculated live · no schema change
04Custom exports

In their format, not a governed report.

Bridge writes a CSV in the shape your customer asked for, with custom and calculated columns included. Saved as a view they can re-run. Their format becomes the default, not a fixed export off a governed dashboard.

Start a free pilot
export.csv
custom format
invoicedays_overduepriority_score
INV-204161High
INV-203834Med
INV-210212Low
custom + calculated columnsdownload
05Speed

Minutes, not a modeling cycle.

In GoodData, a custom ask becomes a data task: model the metric, build the dashboard, deploy the embed. In Bridge, the CSM types the ask, Bridge calls your API and builds the view, and the link goes back in the same conversation.

Start a free pilot
time_to_delivered
measured
Bridge4 min
GoodDataDays. Quarters.

from the moment the CSM relays the ask

Where they actually differ.

The capabilities that decide which tool fits the ask in front of you.

GoodData
Bridge
Built by your CSM, no data team
GoodData: no
Bridge: yes
Installed on your API in minutes, no platform to deploy
GoodData: no
Bridge: yes
Delivered in minutes, not a modeling cycle
GoodData: no
Bridge: yes
Custom dashboards, handled in chat
GoodData: no
Bridge: yes
Custom fields without a semantic model change
GoodData: no
Bridge: yes
Custom exports in the customer's format
GoodData: no
Bridge: yes
Delivered as a chat link, no embed to build
GoodData: no
Bridge: yes
Customer stays in the conversation, no portal
GoodData: no
Bridge: yes
Per-customer scoping from your API auth
GoodData: no
Bridge: yes
Public, self-serve pricing
GoodData: no
Bridge: yes
Embedded analytics inside your product UI
GoodData: yes
Bridge: no
A governed semantic model keeping metrics consistent
GoodData: yes
Bridge: no
Governed customer self-serve at enterprise scale
GoodData: yes
Bridge: no
A reusable analytics layer your data team maintains
GoodData: yes
Bridge: no
Verified June 2026gooddata.ai/pricing

Should you choose Bridge or GoodData?

Bridge sits on your API and handles custom asks in chat. GoodData embeds a governed analytics platform into your product so customers can explore their own data. They cover different jobs.

Best for most teams

Choose Bridge

  • Custom dashboards
    The one your customer asked for once, built in chat and scoped to them.
  • Custom fields
    Calculated across every record, live, with no semantic model change.
  • Custom exports
    A CSV in the customer's format, with calculated columns included.
  • One-off asks
    Anything no governed dashboard covers, handled in minutes by your CSM. No engineering involved.
Start a free pilot

14-day pilot. One customer. No card.

Different job

Choose GoodData only if

  • You want governed, embedded analytics at scale inside your product.
  • Your customers want self-serve exploration with consistent, modeled metrics.
  • You need a semantic model your data team owns across many tenants.
  • You have engineering and data capacity to deploy and maintain the platform.

Still deciding which tool fits the ask?

If you want governed analytics embedded inside your product, that is GoodData. If you want a customer's one-off ask handled in chat without a platform deployment, that is Bridge.

Start a free pilot
  • 14-day pilot on one customer
  • No card to start
  • Keep GoodData for embedded analytics

The questions we get most.

Yes. They cover different jobs, so you can run both. GoodData for the governed analytics your customers explore inside your product. Bridge for the one-off asks they make through your CSM that no dashboard covers.

Yes. They type the ask in plain English. Bridge calls your API, computes whatever needs computing, and builds the view. No semantic model to edit. No dashboard to embed. No engineering pulled in.

No. Embedded, governed analytics at scale inside your product UI is GoodData's job. Bridge sits on your API and handles a customer's one-off ask in chat, shared as a white-labeled link. If you want a semantic model and self-serve analytics your customers explore inside your product, use GoodData. It is built for that.

That is GoodData. Bridge generates a view from a single ask. It does not replace a semantic model your customers explore on their own with consistent metrics. If governed self-serve inside your product is the goal, give them GoodData.

No. GoodData is a platform deployment: a semantic model, an embed, theming, and a governed layer your data team maintains. Bridge installs on your API and your CSM handles asks in chat. No platform, no integration project, no upkeep on a standing model.

GoodData does not publish dollar figures. Both its Professional tier, priced per workspace, and its Enterprise tier are quote-only and sized by sales. Bridge is $199/month for up to 5 connected customers, with unlimited CS seats. Past 5, pricing moves to enterprise and we size it with you. The pilot is free for 14 days, no card. Different models. See the Bridge pricing page for detail.

Only what your API exposes. Queries are authenticated per session. Per-customer activity logs are on by default. We do not train models on your data.

Still on the fence?Book 20 minutes with the founder

Start saying yes to custom asks without a platform deployment.

14 days. One customer. Free. Then $199/month for up to five connected customers, enterprise past that.

Start free guided pilotSee pricing