Home / Platform

Shared data across analytical tools

Databasin lets people analyze shared data through Data Apps, plain-language questions, SQL and notebooks. Open tables hold the records, and business views carry the definitions people use. Our team prepares that foundation so applications and analysts can build on the same work across the organization.

  • WashU Medicine
  • University of Kansas Medical Center
  • Saint Francis Healthcare System
  • Saint Louis University
  • Compana Pet Brands

Consistent measures across the team

A measure has a defined meaning and calculation in the Data Exchange. Colleagues can inspect that definition when they discuss a result. Databasin One and Data Apps use it in the questions and views built on the measure.

The period, filters and permitted records also affect a result. When two figures differ, an analyst can examine those details against the shared definition. We establish the views and calculations so the team can trace the difference to the data or its use.

The foundation for shared analysis

Tools for everyday data work

SQL editor

Inspect query results and continue the investigation against prepared business views.

Python notebooks

Explore prepared tables in notebooks using Python, SQL or PySpark code.

Scheduled transformations

Schedule data preparation and inspect the task logs for each run.

Shared definitions

Reuse a measure whose calculation and business meaning are already established.

Governed access

Manage the identities and data permissions used to query business records.

Federated queries

Join supported live records with synced tables through a Trino query.

Names: Apache IcebergDelta LakeTrinoDatabasin SailPower BITableauPySpark

Applications of the shared lakehouse

Business reviews

A finance view and an analyst's query can use the same prepared measure while people examine it through different tools.

Follow-up questions

A user investigates a change in a business measure and opens the attached SQL to inspect the calculation.

Data science

A notebook gives an analyst a way to explore prepared records within the definitions and access established for that work.

Design, Build, Run

We take responsibility for the work from defining the outcome through implementation and ongoing support.

Design

We define the outcome, current processes and expected return with your stakeholders. A working example shows how Databasin would answer your business questions.

Build

We get your first use case live in 90 days. Communication, rollout, training and success measurement are included in the work.

Run

Choose the help you need after launch. We can run the solution for you, provide monthly support hours or stay on call.

Security for business data

Databasin gives your team controls for who can use business data and records of how they use it.

Trust center →

Access

Your organization manages the identities people use to sign in. Data permissions apply to their work, and investigation agents have read-only access to production sources.

Regulated data

For work involving PHI or HR data, our team helps your security reviewers examine the requirements. Databasin is HIPAA-ready, with a BAA available.

Where data sits

You can use our hosted service, run Databasin in your Azure environment or use it alongside Databricks, Snowflake or Microsoft Fabric.

Audit

An answer comes with its SQL for review. Your team can also examine query logs and lineage to understand the data behind it.

What happens next

We would like to hear where your team wants to make progress with data and AI. We can discuss a project you have in mind or explore where Databasin could help with the work.

What happens next

  1. Book a demo

    Book a conversation about your organization and the work you want to improve. Questions about where to start are welcome.

  2. Explore the opportunity

    We show a working example that answers your business questions, then discuss what it would take to deliver it for your team.

  3. Get the first result

    After agreeing the first use case, we implement it with your team. We train the people using it and measure how it performs.

FAQ

How are upstream changes recorded before analysis uses them?

Schemas and versions are captured in the raw layer. Engineers can inspect a change there and identify the preparation it affects. The extraction record also shows which source structure applied when that run collected the data.

What does an open table format let us do later?

Another compatible tool can read the tables with the required access. This gives the team a way to add analytical engines or applications. The tool must support the format features the workload uses.

Does Databasin Sail support Delta tables too?

Yes. Sail reads and writes both Iceberg and Delta. We choose the format and reading route around the workload and any existing tables the organization intends to keep using.

Can our existing Power BI or Tableau reports use the prepared data?

Yes. A supported BI connection supplies the report with access to the prepared tables. We configure that route so the familiar report can use the definitions and measures established in Databasin.

Can a query combine synced data with a live source?

Yes. Trino can query synced tables together with supported live sources and federated databases. The result combines those sources' data, so their refresh timing and available history must be understood when interpreting it.

Do we have to replace the platform already storing our data?

No. Databasin can work with Databricks, Snowflake or Microsoft Fabric alongside the existing environment. We implement the source connections, preparation and applications that the intended business use needs.

Can analysts revisit records before a business rule was applied?

Yes, with the appropriate access. Bronze retains the raw ingested records. Analysts and engineers can examine those records to trace a calculation or run revised preparation after a business rule changes.

Will every query wait for a cluster to start?

No. Queries can run on compute that is already active. Starting a stopped cluster takes time, so we account for that delay when arranging the compute used by interactive applications and scheduled tasks.

Discuss your data foundation

We can discuss how your teams use data today and which definitions, applications and workflows they want to share. A demo can explore the lakehouse and the implementation work that would support those needs.