DataTugPull more from your data
Open app
☰

For developers, analysts and support leads

Explore data across sources and share the answer

One project holds your sources, your queries and your dashboards. A question asked once becomes something the team can rerun, not a screenshot in a chat.

Explore the demo project All five solutions

Starts here: DevelopersData analystsQA and testers

Watercolor of a crew member at a spyglass on a quay while copies of the same chart are passed hand to hand along it on cards.
Watercolor of five different telescopes and instruments on a jetty, each pointed at a different island, with notes in bottles drifting away.

The problem

Each database has its own client. Combining two of them means exporting CSVs and matching rows in a spreadsheet. A useful query ends up pasted in a chat with the customer ID edited by hand, and nobody can tell which version produced last week’s number.

Dashboards built that way cannot be traced back to the query behind them, so the team stops trusting them.

Before and after

Who: Developers, analysts and support leads

Today

4 tools2 hand-offsno shared password

  1. Analyst · A client per databaseOpen a different client for each database.
  2. Analyst · SpreadsheetExport two CSVs and reconcile them by hand.
  3. A colleague · ChatPaste the query into a chat; edit the values for the next customer.
  4. Whoever asks · BI toolRebuild the dashboard when someone asks where a number came from.
Today4 tools · 2 hand-offs · no shared passwordOpen a different client for each database.Export two CSVs and reconcile them by hand.Paste the query into a chat; edit the values for the next customer.Click to see

With DataTug

1 workspace0 hand-offsno shared password

Some steps are planned or in development.

  1. AnalystKeep every source in one project and save queries with named parameters.Query workspace in the web appAvailable
  2. Developer, in the CLIJoin across sources with TugQL from the CLI.Cross-source TugQL joins in the CLIAvailable
  3. Analyst, in the browserJoin across sources in the browser too.Cross-source TugQL joins in the browserIn development
  4. ReaderOpen the record behind a value with a card, and pin saved queries to a dashboard.DashboardsAvailable
  5. The teamDashboards on a shared project rerun their saved queries.DashboardsAvailable
With DataTug1 workspace · 0 hand-offs · no shared passwordKeep every source in one project and save queries with named parameters.Join across sources with TugQL from the CLI.Join across sources in the browser too.Click to see

Each step names the part of DataTug it relies on and that part’s status today. “Planned” and “In development” steps describe where the product is going, not what you can use now.

Illustration · sample data, not a capture

One question across two databases

Northwind · SQLite · OrdersPayments · PostgreSQL · payments
from Orders o
join payments p on p.order_ref = o.OrderID
where o.CustomerID = 'BOTTM'
select o.OrderID, p.status, o.ShippedDate
The result: Bottom-Dollar Markets' orders with their payment and shipping state
OrderIDpaymentshipped
11045capturednot yet
10918captured1 March
  • Join across sources from the CLI, with TugQL. Cross-source TugQL joins in the CLIAvailable
  • The same in the browser. Cross-source TugQL joins in the browserIn development

Where it meets the other solutions

Try it on sample data

The public demo project opens in the browser with sample Northwind and Chinook data. No sign-up.

Explore the demo project