Bridge
Bridge vs Hex

Hex is where your data team builds. Bridge handles the ask your customer made.

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

Start free guided pilotSee the comparison

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

At a glance
HexBridge
Who it's for
Your data team and analysts
Your customer, through your CSM
What it makes
Notebooks, analyses, data apps
The one-off view a customer asked for
Who builds it
An analyst, in SQL and Python
Your CSM, in chat
Skills needed
SQL and Python, or plain-language Threads
Plain English
Time to a new ask
A notebook to write and review
Minutes
Delivery
A published app your team shares
A white-labeled link, in the conversation
6 of 12 differences shownSee all

Why choose Bridge over Hex.

Hex is where your data team explores and builds. Bridge sits on your API and handles the asks your customers make, in chat.

01Workflow

Handled in chat, not built in a notebook.

Hex is where an analyst writes a notebook to answer a question. Bridge sits on your API. The CSM types the customer's ask in chat, Bridge builds the view, the link goes back in the same conversation. No notebook, no data team.

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 in a notebook.

A new customer view in Hex is a notebook an analyst writes and reviews. 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
03Speed

Minutes, not a notebook to write and review.

In Hex, a customer ask becomes work for the data team: a notebook to write, run, and review against your warehouse. 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
HexDays. Quarters.

from the moment the CSM relays the ask

04Custom fields

Calculated live, not queried.

Bridge adds calculated fields across every record without a query or a Python cell to write. No notebook, no review cycle. 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
05Custom exports

In their format, not a notebook export.

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 yours.

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

Where they actually differ.

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

Hex
Bridge
Built by your CSM, no data team
Hex: no
Bridge: yes
Plain-English ask delivered to your customer by your CSM
Hex: no
Bridge: yes
Installed on your API in minutes, no notebook to build
Hex: no
Bridge: yes
Delivered in minutes, not after a notebook review
Hex: no
Bridge: yes
Custom dashboards, handled in chat
Hex: no
Bridge: yes
Custom fields without writing a query
Hex: no
Bridge: yes
Custom exports in the customer's format
Hex: no
Bridge: yes
Shared as a white-labeled link to your customer
Hex: no
Bridge: yes
Customer stays in the conversation, no app to open
Hex: no
Bridge: yes
Per-customer scoping from your API
Hex: no
Bridge: yes
Exploratory analysis in SQL and Python notebooks
Hex: yes
Bridge: no
AI-assisted data-science workflows for analysts
Hex: yes
Bridge: no
Polished, published data apps for your team
Hex: yes
Bridge: no
Direct warehouse connection and modeling
Hex: yes
Bridge: no
Verified June 2026hex.tech/pricing

Should you choose Bridge or Hex?

Bridge sits on your API and handles customer asks in chat. Hex is where your data team explores, models, and ships analyses. 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 query to write.
  • Custom exports
    A CSV in the customer's format, with calculated columns included.
  • One-off asks
    Anything that does not need a data team, handled in minutes by your CSM.
Start a free pilot

14-day pilot. One customer. No card.

Different job

Choose Hex only if

  • Your data team needs to explore and build analyses in SQL and Python.
  • The work is open-ended: modeling, joins, data-science workflows.
  • You want AI-assisted notebooks and polished, published data apps.
  • Your starting point is a connected warehouse, not a customer ask.

Still deciding which tool fits the ask?

If your data team needs to explore and build an analysis, that is Hex. If you want a customer's one-off ask handled in chat, that is Bridge.

Start a free pilot
  • 14-day pilot on one customer
  • No card to start
  • Keep Hex for data-team analysis

The questions we get most.

Yes. They cover different jobs, so you can run both. Hex for the analyses your data team explores and builds. Bridge for the one-off asks your customers make through your CSM.

Yes. They type the ask in plain English. Bridge calls your API, computes whatever needs computing, and builds the view. No notebook to write. No query, no Python. No analyst pulled in.

Hex's AI, from notebook assist to its plain-language Threads, helps your own team explore your warehouse. The audience is internal and the data is your warehouse. Bridge sits on your API and handles a customer's one-off ask in chat, scoped to that customer and shared as a white-labeled link they open. Different audience, different data, different job.

No. Open-ended exploration, modeling, and data-science workflows in SQL and Python are Hex's job. Bridge answers a single, scoped ask and returns one view. If your analyst needs to explore for an afternoon, use Hex. It is a strong, well-supported tool.

No. Hex connects to your warehouse so analysts can query it directly. Bridge sits on your API and reads only what that API exposes, scoped per customer. If your work starts from warehouse tables and SQL, that is Hex.

Hex is $36 per editor per month on Professional and $75 per editor per month on Team, with a free Community tier and enterprise pricing above. 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 customer asks without a notebook.

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

Start free guided pilotSee pricing