Databricks Says OpenSharing Doubled Procore's Construction Analytics Catalog

Procore rebuilds its analytics product on Databricks' OpenSharing

Construction management software company Procore has rebuilt its Procore Analytics business intelligence product using Databricks' OpenSharing data-sharing technology, according to a Databricks blog post. Databricks says the change lets Procore customers pull data on an hourly basis, replacing a system that was limited to a single daily refresh.

Procore serves tens of thousands of customers across the United States, Europe, the Middle East, Asia and Australia, Databricks says, including real estate owners, general contractors and specialty contractors. Procore Analytics gives those customers programmatic access to Procore's connected dataset so they can pull it into tools they already use, such as Power BI, Tableau, Snowflake, BigQuery, their own Databricks workspace or on-premises SQL Server.

The previous system

The earlier version, which Databricks refers to as Procore Analytics 1.0, ran on a SQL Server backend, with data pulled from Procore's public APIs into an Azure database that customers could query. Databricks says refreshes were capped at once a day, or up to three times a day for customers who paid extra, and that extracting data for tens of thousands of customers through public APIs created cost and reliability problems, including timeouts tied to running deep recursive API calls.

What changed

Databricks says Procore built the new version, Procore Analytics 2.0, on a medallion architecture inside Databricks: a bronze layer holding raw, untouched events, a silver layer applying cleaning and validation, and a gold layer where data is aggregated and modeled for analytics. Gold-layer tables, produced across multiple regions, are consolidated into one primary analytics region, from which OpenSharing distributes data to customers.

According to Databricks, OpenSharing now distributes hundreds of curated tables and maintains partitioned, per-customer access across hundreds of thousands of distinct data shares. Customers without a Databricks account can generate an OpenSharing token inside the Procore application and connect through the open protocol, while customers already running Databricks receive shares natively, workspace to workspace. Databricks says a scheduled job automatically reconciles each user's Procore permissions with their OpenSharing entitlements, enforcing access per user and per project without manual provisioning. Tables have Change Data Feed enabled, letting customers sync only what has changed since their last pull.

Databricks also says Procore consolidated two previously separate pipelines, one for analytics and one for in-app reporting, into a single pipeline feeding both, and adopted a fixed release cadence of four breaking-change releases a year with six weeks of advance notice, plus twelve non-breaking releases a year with three weeks of notice.

Reported results

Databricks says Procore Analytics 1.0 took several years to build its baseline catalog of available tables and fields, while Procore Analytics 2.0 expanded that catalog to hundreds of tables in less than half the time, which Databricks describes as doubling the data available for customers to extract. Databricks also says customers are no longer limited to daily pulls, with many now scheduling refreshes multiple times a day to match their own workflows, and that new product features can have their data made extractable to customers almost as soon as they ship.

Source: Databricks blog, "How Procore is powering construction analytics with OpenSharing," published October 29, 2026.