Bright Machines shares air-gapped factory data via Databricks
Start here
Bright Machines now gives customers live, governed dashboards of factory data from air-gapped plants without opening any inbound access to those sites. It captures PostgreSQL changes at the edge with Debezium, writes them as Apache Iceberg, pushes them out over a single auditable outbound path, and reads them in place in Databricks through Unity Catalog federation. The first customer-visible dashboard went live about two months after kickoff, with committed rows queryable in one to two minutes and dashboards refreshing every ten minutes. The proof of concept took about six weeks with two engineers. Operators keep the on-prem assembly dashboard because they need real time; the cloud-specific parts are the edge sync target, the cross-account replication and the catalog hop.
Generated from reports · updated 12 h ago
Report timeline
Follow the reports to see the event from different sides.
- Databricks BlogBright Machines uses Debezium and Iceberg to give customers live dashboards from air-gapped factories
Bright Machines now gives customers live, governed dashboards of factory data from air-gapped plants without opening any inbound access. It captures PostgreSQL changes at the edge with Debezium, writes them as Apache Iceberg, pushes them out over one auditable outbound path, and reads them in place in Databricks via Unity Catalog federation. The first customer-visible dashboard went live about two months after kickoff, with committed rows queryable in one to two minutes and dashboards refreshing every ten minutes.
Heat for this event
Not enough continuous observations yet to draw a trend.