Skip to content

data-intelligence · tool

Tableside

A warehouse answer in English, with the SQL attached, in the time it takes to type the question

12 h/mo

Saved

35 min

Setup

7

Systems touched

40

Credits per run

$490

Perpetual single-workspace license · Band 1 · Utility

Or included in Growth at $990/mo, along with everything else that tier carries.

Book a demo
Deployment
hosted
Setup
35 min
Hours saved / month
12
Included from
Growth
Credits per run
40

03 — Proof

What is measured, and what is not.

The hours and the setup time are catalog math at a stated volume. Production telemetry is not published yet, and nothing here pretends otherwise.

Catalog math

24 warehouse questions/month × 35 min to write SQL, run, and paste (14h), minus ~2h of remaining grain/join review

Run telemetry

04 — What it does / 5 outputs

Answers ad-hoc questions against your warehouse and returns the SQL and a checkable result.

  • Result table
  • SQL
  • assumed grain

05 — One run

What one run takes in, and what it puts back.

No sandbox on this page yet. This is the real input and output contract from the record, not a demo recording.

In

  • Read-only warehouse credentials
  • optional Looker/Metabase metric map
  • question text
  • row/timeout caps

Out

  • Result table
  • SQL
  • assumed grain
  • run log
  • optional Sheet export

06 — How it works / 35 min setup

Three steps, then it is furniture.

  1. 01

    Connect Snowflake and BigQuery

    Scoped authorisation, revocable from your IdP or the dashboard.

  2. 02

    Point it at the work

    Read-only warehouse credentials, optional Looker/Metabase metric map.

  3. 03

    It runs

    Result table — on a trigger or a schedule, 35 minutes after you start.

07 — Features / 7 listed

What is actually in the box.

  • Read-only service account; every run is logged (question, SQL, rows, who asked)
  • SQL always returned next to the English answer — no hidden query
  • Prefers Looker/Metabase metric definitions when you point it at them
  • Saved-question library with the last-good SQL pinned
  • Blocks questions that would require write, DELETE, or an unbounded SELECT *
  • Row cap and timeout you set; it does not start a full-table scan because someone asked “all customers”
  • Export to Google Sheets; Tableside is not the system of record for the answer

08 — Data

Does it fit your stack and your data?

Inputs this product consumes and outputs it produces
InputOutput
Read-only warehouse credentialsResult table
optional Looker/Metabase metric mapSQL
question textassumed grain
row/timeout capsrun log
optional Sheet export

09 — Integrations / 7 systems

It touches these, and nothing else.

10 — The money

Your hours, your hourly cost.

Two numbers: the hours this product removes at the catalog's stated volume, and the cost of an hour, which only you know.

12

You type this one. We do not know what an hour costs you.

Recovered per month

$600

12 h × $50 an hour, before the credits a run spends.

Where the hours come from: 24 warehouse questions/month × 35 min to write SQL, run, and paste (14h), minus ~2h of remaining grain/join review.

11 — Pricing

Buy it outright, or get it with a plan.

One-time

$490

  • Perpetual single-workspace license to this product’s logic, UI and connectors. Runs still spend credits.
  • Returns $196 as non-expiring credits at your tier’s rate.
  • Twelve months of updates and connector maintenance included.

Per run

40 credits

$0.80 a run at the Starter rate of $0.0200 per credit, less on every tier above it.

Credit class: standard

Every run carries a published hard ceiling. A run that hits it stops and re-quotes instead of billing on.

See how plans and credits work

12 — Packs / 1 pack

What else is in the pack.

  • Part of the Topsheet pack

    Monday’s one-pager for people who will not open Looker

    • Pipeshade

      Topsheet's own key features name the pre-board appendix as "last month vs Pipeshade/Stripe actuals when connected", so the forecast with its visible haircut is a stated part of the packet.

    • Driftnote

      The "what broke" half of the page is a KPI break with the cut that moved and a tracking-suspect flag, which is Driftnote's output verbatim.

    • Cohortcut

      "What moved" is only meaningful in the cut the company runs on, and Cohortcut rebuilds retention, LTV and segment cuts from Stripe with a definition checksum and a diff against last run.

    • Actionline

      The decision list rolls forward week to week and each entry needs an owner, which is Actionline's rule — no task written without a named owner, everything else to the exception list.

    Included in Enterprise · from $7,500/mo

    See the pack

13 — Security

Runs on nox.markets.

You type or upload into our app. Data lands in our region, is processed there, and the results stay in our app until you export them or a connected write-back exists.

Run payloads are kept for your workspace retention window — 30 days by default on Starter and Growth, 90 on Scale and Enterprise, with zero retention available on Enterprise.

Read the security controls

14 — Customers

Someone like you, running this.

15 — Detail

The long version, including what it will not do.

The queue is not “we lack data.” It is twenty Slack messages a month to the one person who can join Stripe invoices to the customers table without double-counting. The requestor waits, rebuilds a worse version in Sheets, or ships a number from memory into a customer email. The analyst’s 35 minutes is real work: find the grain, remember the refund flag, run, paste, explain why last month’s figure does not match Looker.

Tableside is a hosted ask box on a read-only warehouse connection (Snowflake, BigQuery, or Postgres). You type the question; it returns a result table, the SQL, and the grain it assumed. Saved questions become a library so “refund rate by plan, Q2 starts” is not rewritten from scratch. If you have Looker or Metabase metrics, it prefers those definitions over a fresh join.

It is not a semantic layer and it will not invent one. A fluent wrong join is worse than a SQL error — that is why the SQL is always attached and why a human still confirms grain on anything that leaves the building. It will not write to the warehouse. If you already have self-serve Looker with certified Explores and people use them, skip this. Buy it when the certified Explore exists and the questions still land on one inbox.

16 — Questions / 5 answered

Before you buy.

What does it need from me before it can run?

Read-only warehouse credentials; optional Looker/Metabase metric map; question text; row/timeout caps. Nothing else is collected for a run.

How long does setup take?

35 minutes. Runs on nox.markets. You authorise Snowflake, BigQuery, Postgres, Looker, Metabase, Google Sheets, Slack once.

What does it cost to own?

$490 once — band 1, Utility. Runs still spend credits. It is also included in the Growth plan at $990/mo — buying it outright is the way to keep it after a plan ends.

What does it hand back?

Result table; SQL; assumed grain; run log; optional Sheet export.

Where does the hours-saved number come from?

24 warehouse questions/month × 35 min to write SQL, run, and paste (14h), minus ~2h of remaining grain/join review

17 — Related / 4 products

More on the Data & Intelligence shelf.

18 — Collections / 1 shelves

Where it sits on a shelf.

Tableside runs 12 hours of this a month.

Book a demo

Or keep looking: Data & Intelligence · Products for this team · The whole catalog

$490Included in Growth · $990/mo