DataTugPull more from your data
Open app
☰

For your role · App and backend developers

For developers: production bugs across databases

You own the code, so you get the production bug. DataTug keeps your databases, queries and related records in one project, in the browser or the CLI, so a question about real data does not start with six tabs and a shared login.

Explore the demo project All roles
Watercolor of a developer at a harbour workshop bench tracing a pipe on a small engine opened up on a cloth, a tugboat on the slipway outside.

The bug only happens in production, the data is in three databases, and the quickest way to look is a password I should not be pasting anywhere.

Your day

  • One bug, several databases. The order is in Postgres, the payment in MySQL and the event in a log. Each needs its own client and its own copy of the ID.
  • Joins rebuilt from memory. Which column on the other side points back to this row? You work it out again every time, and so does the next developer.
  • An agent that wants the keys. Your coding agent could find it if it could read the data, and the shortest path is the connection string in its config.
  • Queries that vanish. The query that explained the bug lives in a scratch tab, and the next time it happens you write it again.

One task, before and after: find why one order shows the wrong total

Who: App and backend developers

Today

3 tools1 hand-off1 shared password

  1. You · SQL clientOpen a SQL client per database and copy the order ID between them.
  2. You · SQL clientGuess the joins between orders, lines and payments.
  3. Your coding agent · Agent configPaste the connection string into the agent’s config to let it help.a password changes hands
  4. The next developer · Scratch tabLose the query once the bug is fixed.
Today3 tools · 1 hand-off · 1 shared passwordOpen a SQL client per database and copy the order ID between them.Guess the joins between orders, lines and payments.Paste the connection string into the agent’s config to let it help.Click to see

With DataTug

1 workspace0 hand-offsno shared password

Some steps are planned or in development.

  1. YouQuery several databases from one workspace and join across them.Cross-source TugQL joins in the browserIn development
  2. YouStart from the order and follow its related records.Related records in the web appAvailable
  3. Your coding agentLet the agent read through local access policies today, and through one Perimeter for people and agents, in development.DataTug PerimeterIn development
  4. The next developerSave the query in the project so the next person can rerun it.Query workspace in the web appAvailable
With DataTug1 workspace · 0 hand-offs · no shared passwordQuery several databases from one workspace and join across them.Start from the order and follow its related records.Let the agent read through local access policies today, and through one Perimeter for people and agents, in development.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.

Today’s access policies are enforced by your local DataTug CLI: an agent that can read your machine’s DataTug configuration could get past them. Server-enforced access through one Perimeter is in development. How access policies work

Solutions for you

Also useful: Data UnderstandingData Quality & Monitoring

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