Skip to main content

Analytics and reporting integrations

Send Seal records to Power BI, Tableau, Grafana or Spotfire, or read query results from Databricks, BigQuery and Redshift into Seal.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

What these systems hold.

Analytics tools and data platforms hold dashboards, prepared datasets and the queries behind them: yield trends, cycle times, deviation counts and comparisons across sites, built from records kept somewhere else.

FDA’s drug GMP regulations require records to be kept so their data can be used to evaluate each product’s quality standards at least once a year (21 CFR 211.180(e)). A trend that feeds that review needs its measure defined and every point traceable to the batch, sample or event behind it.

What Seal reads and writes back.

The two groups move records in opposite directions. To Tableau, Power BI, Grafana and Spotfire, Seal sends selected records through its API, and Seal keeps the records behind each figure. From Databricks, BigQuery and Redshift, Seal reads query results through the provider’s API; nothing is written back unless that is separately approved, and which system holds each dataset is agreed when the connection is scoped.

Seal
  1. Databricks, Google BigQuerySource of truth agreed when scoped

    Reads Selected records your edition exposes

    Writes back If separately approved

  2. Amazon RedshiftSource of truth agreed when scoped

    Reads Selected records your edition exposes

  3. Grafana, Microsoft Power BI, TIBCO Spotfire, TableauSeal keeps the record

    Sends Selected Seal records

7 connections

Blueprints that use these records.

Start with one source.

Tell us what Neil needs to do and where the records live. We’ll scope the connection with your team.

Book a demo