Connect your data Plus & Ultimate · add-on

Coming soon Live connections from the website come with the full release. The desktop app already reads SQL Server, PostgreSQL, MySQL, Oracle and ODBC databases on your network, at no charge. The full release launches once enough people ask for it. Express your interest

Your spreadsheets and your databases, in the same report.

Connect SQL Server, PostgreSQL, MySQL or Oracle and refresh a dataset from it as often as every 15 minutes. Reports read the refreshed copy, so opening or sharing one never touches your server — unless you make a dataset live, and then it reads the database the moment the report opens.

The Data sources add-on is $30 a month per workspace, on Plus and Ultimate.

  • Four database engines, side by side with your files
  • Cloud databases sign in without a stored password
  • A gateway for servers inside your network
  • Every refresh logged, failures explained in plain words, and edits written back

Coming soon: Adding a SQL Server data source, testing it, making a dataset and setting a 15-minute refresh

Demo — connect a database and schedule its refresh

Three ways in

Wherever the database lives, there’s a way to reach it.

Directly

A server the cloud can reach

Point it at the server with a read-only account. The setup shows the exact GRANT script for your database, and a test reports what it found before anything is saved.

Connect a database

From the cloud

No stored password at all

Azure SQL and Azure Database for PostgreSQL or MySQL, Amazon RDS and Aurora, and Google Cloud SQL can trust your workspace’s own identity for that one data source. There is no long-lived secret anywhere.

Cloud sign-in

Through a gateway

Servers inside your network

A small service on a Windows, Linux or macOS machine you choose. It connects outward only, needs no inbound firewall rule, and its credentials never leave the machine.

Install a gateway

Linked data

Link datasets on the columns they share.

Customers and orders, projects and tasks, budget and actuals: link two datasets on a shared column, from a database or a file, and the report works across both.

  • A grid, Gantt chart or matrix opens each row to its linked rows, up to 4 levels deep
  • Click a customer, and the whole page filters to their orders
  • One visual can read fields from several linked datasets: a customer’s region beside their orders’ total
  • Look up a linked value in a calculated field
  • Link once for the whole workspace on Plus and Ultimate, and row access follows the link
Demo — link two files on a shared column; each project opens to its tasks

Refresh

A refresh that tells you when it breaks.

Choose how often — when asked, every 15 minutes to 24 hours, daily or weekly — and whether each run replaces the rows or adds a dated snapshot. Every run is listed with who or which schedule started it, what it loaded and how long it took.

  • A failed run says why: the sign-in was refused, or the server couldn’t be reached
  • An activity log of every change, test and refused access, exportable as CSV
  • The same schedules on Plus and Ultimate, with no premium tier for more refreshes

Coming soon: A data source’s run history, showing start times, rows loaded, durations and a failed run explained in plain words

Demo — every refresh logged, failures explained

More than a table

Read it the way your database already serves it.

Stored procedures

With their parameters

A dataset can come from a procedure as easily as a table. Its parameters become the dataset’s inputs, set once or filled in when the report opens.

Query texts

SQL you write, reviewed before it runs

Whoever manages a data source can write the query a dataset reads. It is scanned for anything that could change data, and an admin reviews it before the first run.

Live datasets

Read when the report opens

For the numbers that can’t wait for a schedule: a live dataset reads the data source each time the report opens, can refresh itself while the page is up, and can take the reader’s own identity as an input.

Write-back

Fix it in the report, and it’s fixed in the database.

Give a dataset its key fields and a write action — an update, insert or delete through a table, a stored procedure or a query you write — and an edit in the grid is written back where the row lives.

A dry run first

See exactly which rows a write would touch before anything is changed.

A history of every write

Who changed what, when, and what the database said back.

Approved on the gateway

Through a gateway, writes are approved on the machine inside your network, and a data source can be sealed so nothing writes to it at all.

How write-back works

Spreadsheets too

Spreadsheets work just as well.

Not everything lives in a database. Drop another file onto an open report and it becomes another dataset, ready to link to the first. Save the report, and next month’s file drops straight in.

Demo — drop in a second file and it joins the report

Kept safe

Built for the people who have to say yes.

A vault per workspace

Each workspace gets its own vault, identity and key service, so credentials are never shared with another workspace.

Your own key, if you want it

Encrypt stored credentials under a key in your Azure Key Vault, AWS KMS or Google Cloud KMS. Disable it, and refreshes stop from the next run on.

An authenticator for everyone

Before the first data source, every member must use an authenticator app, and every change to a data source asks for a code.

Read-only by design

A dedicated account with SELECT on only the tables you choose. Reports read the stored copy; only a live dataset or a write action you set up reaches the database.

Private Link and Windows sign-in

Reach an Azure database over Private Link with no public endpoint, or let a gateway sign in to SQL Server as the Windows account it runs under. Each data source also says whether public reports may read it.

Coming soon: Pairing an on-premises gateway, with its pairing code and the prompt to approve the machine

Demo — pair a gateway inside your network

Data sources add-on

$30 a month per workspace, on Plus and Ultimate.

The workspace owner adds it on Plan & billing, the same way as extra users. Every person in the workspace can use the data sources they’re given.

Questions about connecting

Which databases can I connect?

SQL Server, PostgreSQL, MySQL / MariaDB and Oracle — on your own servers, or in Azure, AWS or Google Cloud.

Will it slow our database down?

Only refreshes reach it, on the schedule you choose, with a read-only account. Reports and shared links read the stored copy, so a busy dashboard puts no load on your server.

Is a report live, or a copy?

A copy by default, refreshed as often as every 15 minutes. That is what keeps your server out of every page view, and what lets a public link work without anyone reaching your network. A dataset you mark as live reads the database when the report opens instead, for the few numbers that can’t wait.

Can I write edits back to the database?

Yes. Give the dataset its key fields and a write action, and edits made in the grid are written to the table, procedure or query you chose, after a dry run and with a history of every write.

Can it reach a server behind our firewall?

Yes, through a gateway installed on a machine inside your network. It makes one outbound connection, so there is no inbound rule to open.

Where are the credentials kept?

In the workspace’s own vault, or on the gateway machine for a gateway data source. Cloud sign-in needs none at all.

Who can add or change a data source?

The workspace owner and admins, with a code from their authenticator app for every change. Everyone else uses the data sources they are given.

Still exporting the same query to a spreadsheet every Monday? Connect it once instead.

Try it free with a file today, and add the Data sources add-on on Plus or Ultimate when you’re ready.

The Dasher: a CSV in a hurry to become a dashboard.
Try it free before you sign up