Loading...
Engineering signal comparison · gaming · independent
Side-by-side view of Beamable and Pragma on publicly observable engineering-signal axes. Both orgs are tracked in the gaming sector. This page is independent — neither company is affiliated with VC Deal Flow Signal, and no private data is published here.
A quantitative view of Beamable's public engineering activity — what we track and why investors watch it.
A quantitative view of Pragma's public engineering activity — what we track and why investors watch it.
| Axis | Beamable | Pragma |
|---|---|---|
| Sector | gaming | gaming |
| Stage | series a | series b |
| GitHub org | beamable | pragmaplatform |
| Homepage | https://beamable.com | https://pragma.gg |
| Public momentum | steady | steady |
| Public repos | 60+ public repos | 15+ public repos |
| Language bias | C# / ShaderLab | Rust |
Every axis above is derivable from each company's publicly self-published facts (homepage, GitHub org, careers page) or aggregated public GitHub events. We do not publish private contact data, leaked employee info, or anything that requires authenticated access. For deeper per-company signals, see /signal/beamable and /signal/pragma.
Beamable (series a) shows steady momentum across 60+ public repos on a C# / ShaderLab stack. Pragma (series b) shows steady momentum across 15+ public repos on a Rust stack. The contributor-influx and commit-velocity panels are the comparison surfaces most often used by investors and operators when sourcing in this sector.
No. This is an independent side-by-side using only publicly observable GitHub-event aggregates and each company's self-published facts (homepage, GitHub org, stage). Neither company has endorsed, paid for, or reviewed this page. Corrections welcome via /corrections.
Public GitHub events only — commits, pull requests, issues, releases, contributors. Aggregated weekly across both beamable and pragmaplatform. The methodology is published at /methodology and the underlying paper is at SSRN 6606558. Raw aggregates ship via the public MCP server at /api/v1.
Three workflows. (1) Acquisition shortlists: when both orgs are in the same sector and stage, the comparison surfaces the engineering-organization shape that informs integration cost. (2) Vendor consolidation: tech VPs running gaming consolidation projects use side-by-side eng signals as one input. (3) Competitive scans: emerging-manager funds use these pages to benchmark their own portfolio companies against the closest public reference.
Track Beamable, Pragma, and adjacent gaming orgs in one weekly digest.
See First Look