UV
Unshaken Voice Productions
Pittsburgh Growth Engine
All demosDiscuss a pilot
Public-source ecosystem intelligence

Map Pittsburgh's growth engine with real ecosystem data.

This version uses publicly available records from Dealroom and regional first-party sources to map companies, capital, research, commercialization programs, and talent channels. The matching layer is a UVP demonstration that shows how those facts could be routed into actionable introductions.

Evidence boundary: a public record can establish that an organization exists, invests in a sector, operates a program, or reports a metric. It does not establish current buyer interest, investor intent, partnership, endorsement, or participation in this demo. Match scores below are UVP-generated research signals, not Dealroom scores or recommendations.

Live ecosystem topology · public-source data

See Pittsburgh’s commercialization network as a movable 3D system.

Companies, pilot pathways, investors, research programs, talent channels, and the evidence overlaps between them now live inside the Growth Engine itself—not on a separate visualization page. Tower height reflects source richness, cap size reflects signal breadth, and arcs are computed from overlapping public sectors and tags.

Drag to rotate the ecosystem in three dimensions, drag vertically to change the viewing angle, scroll to zoom, isolate data layers, or explode the field to separate dense clusters. Hover or select towers to inspect their public source.

Explore real entities

Choose a Pittsburgh company and inspect possible pathways.

Scores combine sector overlap, public capability signals, stage/program fit, and Pittsburgh-region proximity. The system surfaces why a match appears and links directly to the source record.

Potential pilot and deployment pathways

Publicly documented programs and organizations whose stated remit overlaps the selected company's sector or capabilities.

Loading data…
Ecosystem directory

Source-linked Pittsburgh growth infrastructure.

The cards below are not partner claims. They are public-source records for organizations that can matter to commercialization, capital formation, research translation, workforce, or deployment.

Data governance

Provenance first.

Current implementation is a dated public-source snapshot. A production data service should ingest licensed APIs server-side, retain source lineage, timestamp records, deduplicate entities, and keep third-party API credentials out of the browser. Dealroom data should only be redistributed or embedded under terms that permit the intended use.